tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

Multiple Triggers in One Workflow: FlowMattic Multi-Trigger Guide

FlowMattic multi-trigger workflows: a form submission and a webhook both start the same workflow, with the webhook's fields mapped onto the form's names before an AI Agent and CRM step.

Multiple triggers in one workflow means a single chain of steps can start from several events: a form submission, a webhook from a partner, a schedule or a WordPress event. FlowMattic’s multi-trigger workflows let you add as many triggers as a process needs and map each one onto the first trigger’s field names, so the steps after them never need to know which event started the run.

It is for anyone who has built the same workflow twice because data arrives from two places. One workflow per process keeps the list short and means a fix to a step is a fix for every source.

What is a multi-trigger workflow?

Every workflow in the visual builder starts with one trigger. Beside it on the canvas sits a dashed Add New Trigger box labelled “Start this workflow another way”. Click it, pick an app and event, and the new trigger joins the first one. The builder numbers them 1.1, 1.2, 1.3 and so on, and every trigger’s connector merges into the same first step.

The first trigger has a special role. Its captured fields become the names your action steps use. Every additional trigger keeps its own settings, its own captured response and its own map that translates its fields onto those names.

How multiple triggers in one workflow work

  1. Build with the first trigger. Set it up, capture a response and map its fields into your steps as usual. Keys such as email and first_name become the contract.
  2. Add another trigger. Click Add New Trigger and choose the event, for example Webhooks by FlowMattic. An additional webhook trigger gets its own URL, separate from the first.
  3. Capture its response. Send a sample so FlowMattic knows this trigger’s field names.
  4. Map it. On the new trigger’s Capture tab, the Multi-trigger workflow section lists one row per key from the first trigger, such as “Map email”. In each row, insert a key from this trigger’s response, type a value, or combine both.
  5. Use Auto-map matching keys. One click fills every row whose key exists in both responses. Rows you have already filled are left alone.
  6. Test it. The Run Workflow Test dialog lists captured responses from every trigger, labelled by trigger, and runs the one you choose through that trigger’s mapping.
FlowMattic builder showing the second trigger's Capture tab (Form Builder) with the Multi-trigger workflow mapping rows, each first-trigger key mapped to a {trigger.key} token.
Trigger 1.2's Capture tab maps its fields onto the first trigger's keys, with Auto-map matching keys at the top.

What happens when the second trigger fires

FlowMattic rewrites the incoming data onto the first trigger’s keys before any step runs. A row that holds exactly one token, such as {trigger.customer_email}, passes the value through unchanged, so a list stays a list. A row that mixes text and tokens, such as {trigger.fname} {trigger.lname}, builds a string, and any token with no value becomes empty. The steps then run exactly as they would for the first trigger.

Task History shows where each run came from: the trigger step’s title gains “(via 1.2 …)” with the event name of the trigger that fired.

Conditions and duplicates, per trigger

Each trigger keeps its own Conditions tab. When trigger 1.2 fires, its conditions and its Skip Duplicate Events settings apply, not those of trigger 1.1. A partner webhook can therefore be filtered to one event type while the form trigger accepts everything.

Key options

OptionWhat it does
Add New TriggerAdds trigger 1.2, 1.3 and onwards beside the first trigger.
Map rowsOne row per key of the first trigger’s captured response. Each row’s value becomes that key when this trigger fires.
{trigger.key}Inserts a key from this trigger’s own response. The insert button lists them once a response is captured.
Static textAny plain value, for when this trigger has no matching field.
Auto-map matching keysFills empty rows whose key name exists in both responses.
Conditions tabPer-trigger filters and Skip Duplicate Events, read from the trigger that fired.
DeleteRemoving a trigger renumbers the rest, so 1.3 becomes 1.2.

Use cases

Leads from the website and a partner, scored once

The website form is trigger 1.1 and a partner’s webhook is 1.2, with customer_email mapped to email. Every lead passes through the same AI scoring and lands in the CRM with the same tags.

Form Builder · Webhook → AI Agent → Router → FluentCRM · Slack

Store orders and direct payments, one fulfilment chain

WooCommerce orders are the first trigger. Payments taken outside the shop arrive on a webhook mapped onto the order’s field names, and both reach the same invoice and thank-you steps.

WooCommerce Order Paid · Webhook → Generate PDF from Template → Send Template Email

A report on a timer and on demand

A Schedule trigger runs the weekly report every Monday. A webhook trigger runs the same steps whenever a manager asks for an update mid-week.

Schedule · Webhook → WP Tables: get rows → AI Agent → Send Email

One audit log for every site change

An agency watches Plugin Updated, Theme Switched and WordPress Core Updated in one workflow. The log table and the Slack message are configured once.

Plugin Updated · Theme Switched · WordPress Core Updated → WP Tables → Slack

Support requests from two front doors

A SaaS team takes requests from a contact form and from its in-app help widget’s webhook. An AI Agent classifies both, and the same Router sends them to the right queue.

Form Builder · Webhook → AI Agent → Router → Slack · Email

Published or updated, the same announcement

New Post and Update Post (filtered to published posts) share one workflow that tells the team what changed and logs it in the content calendar.

New Post · Update Post → Telegram → Google Sheets

Tips and gotchas

Most surprises with multiple triggers in one workflow come from which trigger goes first and what the map carries:

  • Capture the first trigger first. Its keys become the map rows. Until it has a response, the map shows “First trigger has no captured response yet.”
  • Make the first trigger’s sample complete. When an additional trigger fires, the run carries only the mapped keys. A field that exists only on trigger 1.2 is not available to the steps unless it is mapped onto one of the first trigger’s keys.
  • Choose which trigger goes first. Webhooks, Schedule, WordPress events and FlowMattic’s own events, such as Form Builder submissions, WP Tables and Bookings, start a run as additional triggers. Polling triggers (RSS Feed, IMAP Email Parser, API Polling) and some integrations, WooCommerce among them, start a run only as the first trigger, so put those in position 1.1.
  • Static values fill gaps. If a partner never sends a country, type the default straight into the row.
  • Each webhook trigger has its own URL. Give each sender the URL of its own trigger, so the right map is applied.

Related features

See examples and the canvas in action on the multi-trigger workflows page.

FAQ

Can a workflow have more than one trigger?

Yes. Click Add New Trigger beside the first trigger on the canvas to add trigger 1.2, 1.3 and onwards. All of them run the same chain of steps.

What if the triggers use different field names?

Map them once. On each additional trigger’s Capture tab, every key of the first trigger is a row, and you insert the matching key from the new trigger, such as {trigger.customer_email} for email. Auto-map matching keys fills the rows whose names already agree.

How do I know which trigger started a run?

Task History labels the trigger step with “(via 1.2 …)” and the event name of the trigger that fired. Runs started by the first trigger look the same as in a single-trigger workflow.

Do conditions apply to every trigger?

No, each trigger has its own. The Conditions tab and Skip Duplicate Events settings of the trigger that fired are the ones applied to that run.

Can Generate with AI build multi-trigger workflows?

Yes. Workflow generation understands multi-trigger workflows and writes each additional trigger with its map onto the first trigger’s fields. Review the map on each trigger’s Capture tab before you switch the workflow on.

One process, one workflow, however many ways in. Try FlowMattic and add a second trigger on a live demo site.

More from the blog