# monday.com One Trigger Multiple Actions: Action Chaining Canonical: https://www.taskrhino.ca/en-us/monday-com-automations/one-trigger-multiple-actions/ > Chain multiple actions from one monday.com trigger: custom automations run them in parallel, the workflow builder runs them in order. Plus workarounds. Published: 2026-02-26 Updated: 2026-10-29 Author: Rakesh Patel Categories: BoardBridge **Key takeaways** - monday.com automations can run several actions from one trigger, but in custom board automations they run at the same time and take values only from the trigger. - The workflow builder runs blocks in sequence and can pass values from earlier steps. - In custom automations a failed action doesn’t stop the others, so a status can say “Sent” when the email never went out. - Community reports say a change made by one automation doesn’t trigger another; monday.com doesn’t document this, so test it. - Run history shows each automation run and its outcome, so check it after the first runs to catch a failed action. You need a button click to trigger a sequence of actions—send an email, update three status columns, and create an item on another board. monday.com’s button column can trigger automation recipes with multiple actions. That part is fine. But here’s the problem: **actions don’t share data with each other**, and **cross-board actions don’t integrate well with email actions in the same recipe**. The result? You end up with fragile multi-automation setups that fire at unpredictable times, or you give up and build workarounds that make maintenance a nightmare. This article explains how action chaining works in monday.com, where it breaks down, and how the workflow builder handles sequential multi-action workflows. ## The Problem: Limited Button Automation Actions Definition **Action chaining:** running several actions from one trigger in a set order, where later actions can use results from earlier ones. monday.com’s automation builder DOES let you add multiple actions to a single recipe. When you create an automation, you can click the “+” button to add more actions below the first one. But here’s where it gets restrictive: ### Button Column Limitations Community threads from 2020-2022 (such as [Introducing the Button Column](https://community.monday.com/t/introducing-the-button-column/10279)) describe the button as triggering one automation recipe, with multi-step work needing separate automations or workarounds. While technically you can add multiple actions within that ONE recipe, **the button column itself can only connect to one automation**. So if you need five different button-triggered workflows on the same board, you need five separate button columns. ### Cross-Board Action Limitations From a forum thread titled [“Custom Automations and Action Button / Command Button Column”](https://community.monday.com/t/custom-automations-and-action-button-command-button-column/2530): > “Make it compatible with Subitem automation recipes (example create subitem instead of item)” and “The create item functions doesn’t allow to select or concatenate and put original field content on new item.” — **hlopezvc**, August 11, 2020 monday.com staff (Becca) confirmed the button column was released but did not address the advanced functionality requests. ### What Actions Can’t Combine Well - **Email + cross-board item creation:** In custom board automations, email actions don’t have access to the newly created item’s ID from a prior “create item on another board” action (the workflow builder can pass it) - **Multiple status updates + notification:** Community reports say status changes made by an automation don’t trigger other automations (monday.com doesn’t document this) - **Button click + conditional email:** No conditional branching within a single recipe (see [monday.com Conditional Automation If/Else](https://www.taskrhino.ca/en-us/monday-com-automations/if-then-conditional/) for more on this limitation) ## What monday.com Supports ### Native Multi-Action Capabilities monday.com automations CAN chain multiple actions in a single recipe. For example: **Recipe: When status changes to “Approved”** - Action 1: Notify person - Action 2: Move item to “Approved” group - Action 3: Create item on “Archive” board This works fine for **linear, non-dependent actions** — actions that don’t need data from each other. ### What Doesn’t Work - **Using results from earlier actions in later ones:** In custom board automations values come only from the trigger, so you can’t reference the item ID created in Action 1 within the email body of Action 2. The workflow builder does pass dynamic values from earlier steps ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/18382067611410-Comparing-the-workflow-builder-and-automations)) - **Conditional continuation:** If Action 1 fails, later actions still run unless they depend on it, so a failed email won’t stop a status update ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/360012254440-Build-your-own-custom-automation)) - **Cross-automation chaining:** Community reports say an automation-triggered column change doesn’t trigger other automations; monday.com doesn’t document this, so test it TaskRhino tip In custom board automations, write a value to a column first if a later action needs it, then reference that column. From a forum thread titled [“Automation by column change does not work if the change was by automation”](https://community.monday.com/t/automation-by-column-change-does-not-work-if-the-change-was-by-automation/69289): > “When an item is created in the board NEW an automation is activated to connect the item…On the board CURRENT there is an automation that suppose to be activated by column change…It does not get activated by the change that happens with the automation.” — **elromlu**, October 26, 2023 monday.com Implementation Consultant **GiannisKoukounas** replied that this isn’t supported. monday.com’s documentation doesn’t state the rule either way. **Plan Your Multi-Action Automations** Get help deciding what belongs in one automation, a workflow or separate automations. [Book a Free Call](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ## Real-World Example: Event Confirmation Workflow Here’s an example workflow for a team managing live event logistics. ### The Scenario When the event coordinator clicks the **“Send Show Form”** button on an event item, the system needs to: 1. **Send a personalized email** to the client with a unique form link 2. **Update the “Show Form Status”** column to “Sent” 3. **Update the “Last Contact Date”** column to today’s date 4. **CC the logistics team** on the email ### The monday.com Approach You’d set up a button column with a connected automation: **Trigger:** Button clicked **Actions:** 1. Send an email (but NO CC support — see [monday.com Button Automation Send Email with CC](https://www.taskrhino.ca/en-us/monday-com-automations/button-click-email/)) 2. Change “Show Form Status” to “Sent” 3. Change “Last Contact Date” to “Today” **Problems:** - **No CC** — monday.com button-triggered emails don’t support CC recipients - **Personalized form URLs take setup** — WorkForms URL pre-fill (Pro and Enterprise) can build per-item links, and email actions can insert a Form view URL column value ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/26808283008146-WorkForms-pre-fill-and-form-tags-settings)) - **No failure handling** — if the email fails to send (invalid recipient address), the status columns still update, making it look like the email went out when it didn’t ### The Workflow Builder Approach In the workflow builder, blocks run in sequence and later blocks can use values from earlier steps, so the work can be ordered: 1. **Send the email** to the address in the “Client Email” column, with the item’s form link from a Form view URL column (or a pre-filled WorkForms link) 2. **Update “Show Form Status”** to “Sent” 3. **Update “Last Contact Date”** to today **CC:** the standard Gmail/Outlook action has no CC; monday service’s Send new email block has CC/BCC (Pro plan and above), and BoardBridge emails, sent from a button, support CC and BCC. **Failures:** monday.com doesn’t document a stop-on-failure option, so check Run history after the first runs. Wondering whether BoardBridge’s button emails fit this workflow? [Ask us](https://www.taskrhino.ca/en-us/contact-us/). ## How Action Chaining Works in monday.com ### Sequential Execution In the workflow builder, blocks run in order, one after another. In custom board automations, the actions in one automation run at the same time. **Why this matters:** Some actions produce data that later actions need. For example: - Action 1: Create an item on the Production board → returns the new item’s ID - Action 2: Update a “Production Item Link” column on the original board with that ID In custom board automations, you’d need TWO separate automations (actions in one automation run at the same time); the workflow builder can do it in sequence. ### Passing Values Between Steps The workflow builder can pass dynamic values from earlier steps. In custom board automations, values come only from the trigger, so write a value to a column first (for example, a Form view URL column) and reference that column in the email. ### When an Action Fails In a custom automation, a failed action doesn’t stop the others unless they depend on it, so a failed email won’t stop a status update. Run history shows how each automation ran and where it got stuck, and a failed integration action also shows a bell notification and a failure message in the automation activity log. **Example:** - Action 1: Send email → **Fails** (recipient address is invalid) - Action 2: Update status to “Sent” → **Still runs** - Run history shows the failed email, so you can fix the address and set the status back **Need help structuring your monday.com boards?** 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) ## When to Use Multiple Actions vs. Multiple Automations ### Use One Automation with Multiple Actions When: - Actions are **logically part of the same workflow** (e.g., “send confirmation email” and “update confirmation status”) - Actions need to **execute in a specific sequence** or **use results from earlier ones**: build it in the workflow builder, since custom automation actions run at the same time ### Use Separate Automations When: - Actions are **triggered by different events** (e.g., one on button click, one on status change) - Actions are **independent** and can run in parallel - You need **different conditional logic** for each action (e.g., “send email A if dropdown = X, send email B if dropdown = Y”) ## Common Action Sequences Here are five common multi-action workflows: ### 1\. Button Click → Send Form Link + Update Status **Actions:** 1. Send email to the recipient (from column) with the item’s form link (from a Form view URL column) 2. Update “Form Sent Status” to “Sent” 3. Update “Last Contact Date” to today **Use case:** Client onboarding, vendor data collection, event RSVPs ### 2\. Status Change → Create Item on Another Board + Link It Back **Actions:** 1. Create item on the Production board (with column values from the source item) 2. Update a “Production Board Link” column on the source item with the new item’s ID (in the workflow builder, which passes values from earlier steps) **Use case:** Cross-board project handoffs (Sales → Delivery, Booking → Logistics) ### 3\. Button Click → Travel Email + Status Update **Condition:** and only if “Trip Type” is “Outbound” (a second automation with “Trip Type” is “Return” sends the return email) **Actions:** 1. Send Outbound Travel Email 2. Update “Travel Email Status” to “Sent” **Use case:** Event travel coordination, multi-stage project workflows ### 4\. Form Submission → New Item + Follow-Up Email **Actions:** 1. A WorkForms submission creates the item 2. “When an item is created” sends a “Thank You” email 3. The same automation sets the “Form Submitted Date” column **Use case:** Multi-page forms, conditional follow-ups based on form data ### 5\. Button Click → One Email with Three Form Links **Actions:** 1. Send one email to the client (from “Client Email” column) with the Show Form, Teebox Form and Production Form links (from three Form view URL columns) 2. Update “All Forms Sent Status” to “Sent” **Use case:** Consolidated client communication (one email instead of three separate messages) **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) ## What This Means for Your Workflows Action chaining turns button clicks and status changes into complete workflows. Instead of managing five separate automations that fire at unpredictable times, you build one workflow whose blocks run in order, then check Run history to see what happened. Since there is no [test sandbox mode for monday.com automations](https://www.taskrhino.ca/en-us/monday-com-automations/dry-run/), run a new chain on test items first. For teams coordinating multi-step processes (client onboarding, event logistics, approval workflows, vendor management), this is the difference between automations that feel brittle and automations that just work. If your processes require more than simple “notify person” automations, our [monday.com customization](https://www.taskrhino.ca/en-us/monday-com-customization/) team can build the workflow with you. See more gaps in our [monday.com automations](https://www.taskrhino.ca/en-us/monday-com-automations/) guides. [Book a consultation](https://www.taskrhino.ca/en-us/contact-us/) to see how action chaining works for your workflow. ## Frequently Asked Questions **Can monday.com automations include multiple actions?** ### Yes. One automation can include multiple actions (send email, change status, create item). In custom board automations the actions run at the same time and take values only from the trigger, so later actions can’t use data from earlier ones; the workflow builder runs blocks in sequence and can pass values from earlier steps. **Can I reference data from Action 1 in Action 2’s email body?** ### Not in custom board automations: actions don’t share data, so write the URL to a column first, then reference that column in the email. The workflow builder can pass values from earlier steps. **Can I add conditional logic within a multi-action automation?** ### Yes: a custom automation can take “and only if” conditions, which must pass before its actions run (see [pre-conditions](https://www.taskrhino.ca/en-us/monday-com-automations/block-precondition/)). For branching logic (if X then do A, else do B), set up two automations with opposite conditions, or use the workflow builder’s If/Else and multi-branch conditions. **Do monday.com automations trigger other automations?** ### Community reports say no: if Automation 1 changes a status and Automation 2 is set to trigger on that status change, Automation 2 may not fire when the change was made by Automation 1. monday.com’s documentation doesn’t state this rule, so test chained automations before relying on them. **What if required data is missing when the button is clicked?** ### The button runs its custom automation regardless of column state unless you add “and only if” conditions, so add conditions for the columns the actions need. If a run doesn’t do what you expect, check Run history. **Can I use action chaining with status change triggers?** ### Yes. Action chaining isn’t limited to button clicks; a status change can trigger a chained automation too. **Do chained actions consume more monday.com automation quota?** ### Yes. Triggering a template usually uses one action, but some use more, and in the workflow builder the more blocks you create, the more actions you use (one per email sent, one per person notified). Plans include 250 actions a month on Standard, 25,000 on Pro and 250,000 on Enterprise. **Can I see what happened after each action in the chain?** ### Yes. Run history shows how each automation ran and the actions or outcomes it produced, so you can see where a run got stuck. **What’s the difference between sequential and parallel action execution?** ### **Sequential (what monday.com’s workflow builder does):** Action 1 → Action 2 → Action 3. Actions can share data and depend on each other. **Parallel (what monday.com’s custom board automations do):** Action 1, 2, 3 happen at the same time. Fine for independent actions, but no data sharing between actions.