# monday.com Conditional Email Template Selection Canonical: https://www.taskrhino.ca/en-us/monday-com-automations/conditional-email-template-selection/ > monday.com automations can’t pick an email template from column values. How workflow branches do it, the separate-automation workaround and its costs. Published: 2026-02-26 Updated: 2026-10-29 Author: Rakesh Patel Categories: BoardBridge **Key takeaways** - A monday.com board automation can filter when it fires, but it can’t choose a different email template based on column values. - The workflow builder can: If/Else and multi-branch conditions give each branch its own Send email step. - Each condition step in a workflow counts toward your monthly automation actions. - The classic workaround is one automation per scenario, which multiplies maintenance as scenarios grow. - BoardBridge emails can add conditional recipients and merge column values; ask us whether one email can pick its template from your data. You need one automation rule that sends different email templates depending on column values. When Status changes to “Advanced” and Trip Type = “Outbound”, send the Outbound Travel Email. When Status changes to “Advanced” and Trip Type = “Return”, send the Return Travel Email. [monday.com’s automation builder](https://www.taskrhino.ca/en-us/monday-com-automations/) doesn’t support if/else branching in board automations. You can set up ONE trigger (status change) and a fixed set of actions, but you cannot say “if Column X = Y, send Template A, otherwise send Template B.” The workflow builder can: its If/Else and multi-branch conditions give each branch its own Send email step ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/11065311570066-Get-started-with-the-workflow-builder)). The result? Teams create separate automations for every scenario — one automation for outbound trips, one for return trips, one for canceled trips — multiplying maintenance overhead and increasing the chance that one automation breaks while others work. This article explains where monday.com’s board automations stop and the workflow builder starts, and what BoardBridge adds. Emails sent from a button are covered further down. ## The Problem: No If/Else in Board Automation Actions monday.com board automations follow a simple structure: **Trigger** → **Condition (optional)** → **Action(s)** The **Condition** step lets you filter WHEN the automation fires (e.g., “only if Person = Manager”), but it doesn’t let you [**branch the action**](https://www.taskrhino.ca/en-us/monday-com-automations/if-then-conditional/). Once the trigger and condition pass, the actions are fixed. Definition **Conditional template selection:** one automation that picks which email to send from the item’s data, such as an Outbound or Return email depending on Trip Type. In a board automation, several conditions combine with AND, so you can narrow when one automation fires, but every automation still sends the one email it was built with. Choosing between emails needs either a separate automation per email or the workflow builder’s branches ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/11065311570066-Get-started-with-the-workflow-builder)). ## The Same Gap on a Button Click monday.com’s button column connects to **one automation recipe**. That automation can include [multiple actions](https://www.taskrhino.ca/en-us/monday-com-automations/one-trigger-multiple-actions/) (send email, change status, create item, etc.), but **all actions are fixed**. Board automations have no else branch that says “if Column X = Y, do Action A, otherwise do Action B.” The workflow builder does have If/Else and multi-branch conditions, but monday.com’s docs don’t confirm a Button column click as a workflow trigger ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/11065311570066-Get-started-with-the-workflow-builder)). Definition **Else branch:** the “otherwise” path of a condition — if Trip Type is Outbound send one email, otherwise send another. The workflow builder is also limited by plan: 3 active workflows on Standard, 20 on Pro and 250 on Enterprise ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/11381357489810)). ### What This Means for Button Emails If you need to send different email templates based on item data, you have two bad options: **Option 1: Multiple buttons** - “Send Outbound Travel Email” button (connected to Outbound Email automation) - “Send Return Travel Email” button (connected to Return Email automation) **Problems:** - Visual clutter — two button columns instead of one - User error — team members click the wrong button - Maintenance overhead — every new scenario requires a new button and automation **Option 2: One button with generic email** - “Send Travel Email” button sends a generic template that covers both outbound and return trips **Problems:** - Email contains irrelevant information (return trip details when it’s an outbound trip) - Looks unprofessional and confuses recipients Neither is acceptable for client-facing workflows. ## What Users Need vs. What monday.com Offers ### What Users Need | Scenario | Desired Logic | | --- | --- | | Travel coordination | When Status = “Advanced”, check Trip Type → if “Outbound”, send Outbound Email; if “Return”, send Return Email | | Approval workflow | When Status = “Approved”, check Amount → if ≥$10k, send Large Approval Email; if <$10k, send Standard Email | | Team handoff | When Status = “Complete”, check Team → if “Internal”, send Internal Handoff Email; if “External”, send Vendor Email | | Multi-language | When Status = “Confirmed”, check Language → send template in client’s preferred language | ### What monday.com Offers | Feature | Support | | --- | --- | | Trigger on status change | ✅ Supported | | Condition to filter when automation fires | ✅ Supported (several conditions combine with AND) | | Conditional email template selection | ⚠️ Not in board automations; workflow If/Else or multi-branch conditions can | | Multiple automations per scenario | ⚠️ Workaround exists but fragile and hard to maintain | **Finally: CC/BCC in monday.com Emails** BoardBridge adds CC/BCC, named CC groups and conditional recipients to monday.com emails. [Book a Free Demo](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ## Example: Multi-Stage Approval Workflow Take a company managing project approvals across multiple departments. ### The Scenario The company uses an Approvals board with: - **Status column:** “Submitted”, “In Review”, “Approved”, “Rejected” - **Amount column:** Dollar value of the request - **Department dropdown:** “Marketing”, “Sales”, “Operations”, “Finance” When the status changes to **“Approved”**, the system needs to send different email templates based on: 1. **Amount:** Large approvals (≥$10,000) require detailed documentation. Small approvals (<$10,000) get a simple confirmation. 2. **Department:** Different departments have different next steps (Marketing needs creative assets, Finance needs invoice details, etc.) This creates **8 possible email scenarios**: **The 8 email scenarios:** - Marketing + Large Approval - Marketing + Standard Approval - Sales + Large Approval - Sales + Standard Approval - Operations + Large Approval - Operations + Standard Approval - Finance + Large Approval - Finance + Standard Approval ### The monday.com Approach (8 Separate Automations) Here’s what teams have to do: **Automation 1:** - **Trigger:** When Status changes to “Approved” - **Condition:** Person is in “Marketing” AND Amount ≥ $10,000 - **Action:** Send “Marketing Large Approval Email” **Automation 2:** - **Trigger:** When Status changes to “Approved” - **Condition:** Person is in “Marketing” AND Amount < $10,000 - **Action:** Send “Marketing Standard Approval Email” …repeat for Sales, Operations, Finance (8 total automations). **Problems:** - **8 automations to maintain** — if you update the email template or change the $10,000 threshold, you have to edit 8 automations - **No branching** — each combination needs its own automation; to branch on Amount and Department in one place you need the workflow builder, whose conditions check any item value - **Easy to break** — deactivate one automation by accident, and one scenario stops working while others continue (hard to debug) - **Hard to audit** — no single place to see the full approval workflow logic ## The monday.com Workaround (Separate Automations) If you’re not using BoardBridge, here’s the most reliable [monday.com-native approach](https://www.taskrhino.ca/en-us/monday-com-automations/if-then-conditional/): ### Setup Create separate automations for each combination of Department and Amount tier. **Automation structure:** - **Trigger:** When Status changes to “Approved” - **Condition:** (optional) Person is in \[Department\] - **Action:** Send email using \[Department + Amount Tier\] template **Example:** | Automation # | Condition | Email Template | | --- | --- | --- | | 1 | Person in Marketing, Amount ≥ $10k | Marketing Large Approval | | 2 | Person in Marketing, Amount < $10k | Marketing Standard Approval | | 3 | Person in Sales, Amount ≥ $10k | Sales Large Approval | | 4 | Person in Sales, Amount < $10k | Sales Standard Approval | | 5 | Person in Operations, Amount ≥ $10k | Operations Large Approval | | 6 | Person in Operations, Amount < $10k | Operations Standard Approval | | 7 | Person in Finance, Amount ≥ $10k | Finance Large Approval | | 8 | Person in Finance, Amount < $10k | Finance Standard Approval | **Problems:** - **Intermediate columns** — teams often add an **“Amount Tier”** or “Department Status” status column so a simple condition can test it; the workflow builder’s conditions can check item values like Amount and Department directly ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/11065311570066-Get-started-with-the-workflow-builder)) - **Person as a proxy for Department** — doesn’t work if multiple people from the same department are involved - **Maintenance nightmare** — changing the $10,000 threshold requires editing all 8 automations This workaround is technically possible but painful to build and harder to maintain. In the workflow builder, one workflow with a multi-branch condition on Department and Amount can replace the eight automations, though each condition step counts toward your monthly automation actions ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/360017556179-Automation-and-Integration-actions-and-limits)). TaskRhino tip If you stay with separate automations, give each one a name that states its condition and template, such as “Approved – Marketing – Large”. It makes the set easier to audit and update. ## The Button Workaround (Multiple Buttons) If you’re not using BoardBridge, here’s the cleanest monday.com-native approach: ### Setting up the buttons **Step 1: Create button columns** - “Send Outbound Email” (connected to Automation 1) - “Send Return Email” (connected to Automation 2) **Step 2: Configure automations** **Automation 1:** - **Trigger:** “Send Outbound Email” button clicked - **Action:** Send email using “Outbound Travel Email” template - **Recipient:** Team Member Email column **Automation 2:** - **Trigger:** “Send Return Email” button clicked - **Action:** Send email using “Return Travel Email” template - **Recipient:** Team Member Email column **Step 3: Hide the wrong button based on Trip Type** **Workaround:** Use conditional formatting to visually hide buttons that shouldn’t be clicked. **Problem:** Conditional formatting **only changes appearance** — it doesn’t actually prevent the button from being clicked. A user can still accidentally click a visually dimmed button. TaskRhino tip If you keep separate buttons, add a condition to each automation, such as “only if the Trip Type status is Outbound”. A wrong click then sends nothing. ### Alternative: Separate Boards Some teams create **separate boards** for outbound and return trips to avoid the multiple-button problem. **Problems:** - **Data fragmentation** — travel data split across two boards - **Harder reporting** — can’t easily see all travel items in one view - **Double the board maintenance** — column changes, view setups, and automation updates must be done twice ## How BoardBridge Handles Conditional Email Templates BoardBridge — Form & Workflow Automation for monday.com — sends button-triggered emails from monday.com items. Several of its email features help with the same problem: **What BoardBridge emails support:** - **Rich HTML** with the item’s column values merged in, so one email can carry the details that differ between items ([rich HTML emails](https://www.taskrhino.ca/en-us/monday-com-automations/rich-html-emails/)) - **Conditional recipients** — add people to the CC line when a column meets a condition, such as Department equals “Marketing” ([conditional CC](https://www.taskrhino.ca/en-us/monday-com-automations/conditional-cc-recipients/)) - **Named CC groups** — such as “Approvals Team” - **Button-triggered sending** from the item ([button-click emails](https://www.taskrhino.ca/en-us/monday-com-automations/button-click-email/)) - **Not monday.com automation actions** — BoardBridge emails don’t use automation actions, but its monday.com API calls count toward the daily API limit (below) BoardBridge uses the monday.com API, so its calls count toward monday.com’s daily API limit (200 on Free, 1,000 on Basic and Standard; 10,000 on Pro; 25,000 on Enterprise) ([monday.com developer docs](https://developer.monday.com/api-reference/docs/rate-limits)). Whether one BoardBridge email can choose its template from column values depends on your setup: [ask us](https://www.taskrhino.ca/en-us/contact-us/) with your scenarios. **Need help with monday.com email automations?** Book a free 30-minute call with a certified monday.com partner. [Book a Free Call](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ## Common Conditional Email Scenarios Here are five workflows where one workflow with branches replaces a separate automation per email: ### 1\. Multi-Language Client Communication **Trigger:** Status changes to “Confirmed” **Conditional logic:** - If Language = “English” → English Confirmation template - If Language = “Spanish” → Spanish Confirmation template - If Language = “French” → French Confirmation template **Why it matters:** Client communications must match their preferred language. One automation handles all. ### 2\. Tiered Support Responses **Trigger:** Status changes to “Resolved” **Conditional logic:** - If Priority = “Critical” → VIP Resolution template (includes escalation manager contact) - If Priority = “High” → Standard Resolution template - If Priority = “Low” → Self-Service Resolution template (includes knowledge base links) **Why it matters:** Different priority levels require different follow-up content. One automation adapts. ### 3\. Internal vs. External Handoff **Trigger:** Status changes to “Complete” **Conditional logic:** - If Team = “Internal” → Internal Handoff template (casual tone, includes Slack channels and internal process links) - If Team = “External Vendor” → External Handoff template (formal tone, self-contained instructions) **Why it matters:** Internal and external audiences need completely different language and content. One automation handles both. ### 4\. Geographic Region Routing **Trigger:** Status changes to “Shipped” **Conditional logic:** - If Region = “North America” → NA Shipping Confirmation (includes FedEx tracking, 2-5 day delivery) - If Region = “Europe” → EU Shipping Confirmation (includes DHL tracking, customs info, 5-10 day delivery) - If Region = “Asia-Pacific” → APAC Shipping Confirmation (includes different carrier, 7-14 day delivery) **Why it matters:** Shipping logistics vary by region. One automation covers all. ### 5\. Subscription Tier Notifications **Trigger:** Status changes to “Renewed” **Conditional logic:** - If Plan = “Basic” → Basic Renewal template (includes upgrade incentives) - If Plan = “Pro” → Pro Renewal template (includes advanced feature tips) - If Plan = “Enterprise” → Enterprise Renewal template (includes dedicated account manager contact) **Why it matters:** Different subscription tiers receive different renewal communications. One automation scales across tiers. **Need Help With Your monday.com Setup?** TaskRhino has implemented monday.com for 110+ teams. Get a free consultation. [Schedule Free Consultation](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ### 6\. Event Type Confirmations **Button:** “Send Confirmation Email” **Conditional logic:** - If Event Type = “Wedding” → Wedding Confirmation template - If Event Type = “Corporate” → Corporate Confirmation template - If Event Type = “Concert” → Concert Confirmation template **Why it matters:** Wedding confirmations include ceremony details, corporate events include branding requirements, concerts include setlist and soundcheck info. Three completely different emails. ### 7\. Invoice Amount Tiers **Button:** “Send Invoice” **Conditional logic:** - If Amount < $5,000 → Standard Invoice template - If Amount ≥ $5,000 → Large Invoice template (includes payment plan options) **Why it matters:** High-value invoices require different payment terms and approval workflows. ### 8\. Approval Status Notifications **Button:** “Send Status Update” **Conditional logic:** - If Status = “Approved” → Approval Notification template - If Status = “Rejected” → Rejection Notification template (includes next steps and appeal process) - If Status = “Pending” → Reminder template **Why it matters:** Three distinct outcomes, three different tones and content blocks. ## When Native Emails Are Enough monday.com’s native button-triggered emails work perfectly fine when: - You only need **one email template per button** - You don’t need **CC or BCC recipients** (see [CC and BCC in monday.com email automations](https://www.taskrhino.ca/en-us/monday-com-automations/email-cc-bcc/)) - You’re okay with **limited email formatting** (plain text in classic recipes; HTML needs the New Automation Builder or workflow email blocks) - Your workflow doesn’t have **branching scenarios** (if this, send A; if that, send B) For these simple cases, stick with native [monday.com automations](https://www.taskrhino.ca/en-us/monday-com-automations/) — they’re fast to set up and require no additional tools. ## Frequently Asked Questions **Can monday.com automations send different emails based on column values?** ### Not in a single board automation: you can filter WHEN it fires (via conditions), but you cannot branch WHAT it does based on data, so you’d need separate automations for each scenario. The workflow builder can: If/Else and multi-branch conditions send a different email per branch, and each condition step counts toward your monthly automation actions. **How many emails can one workflow choose between?** ### monday.com doesn’t document a branch limit. Each condition step counts toward your monthly automation actions, so many branches on a busy board use actions faster. **Can I combine conditional templates with CC rules?** ### Yes, with BoardBridge. CC recipients can be: – Static (same CC list for every email) – Conditional (different CC recipients based on Department, Region, or other column values) For example: – Marketing approvals CC the Marketing Director – Finance approvals CC the CFO – Sales approvals CC the VP of Sales **Do BoardBridge emails consume monday.com automation actions?** ### No. BoardBridge emails don’t use your monday.com automation action quota. BoardBridge does use the monday.com API, so its calls count toward the daily API limit (200 on Free, 1,000 on Basic and Standard; 10,000 on Pro; 25,000 on Enterprise). **Can one button column pick a different email template for each item?** ### Not from one button automation. A button runs one custom automation with a fixed set of actions and no else branch, so you’d need separate buttons (and separate automations) for each email template. The workflow builder has If/Else branches that can send a different email per branch, but monday.com doesn’t document a button click as a workflow trigger.