Understanding Workflow Triggers: Why Did This Automation Run?

Triggers and filters decide who enters a workflow. When an automation runs for the wrong people or sends the wrong email, the usual cause is a missing or too-loose trigger filter. This article explains how entry works and where to look when a workflow ran when you did not expect it.

How a workflow decides who enters

A workflow runs only after it is Published. A Draft never processes triggers or takes real actions, so configuration changes while you build stay invisible to members until you publish.

A workflow can have multiple triggers, and any trigger that meets its conditions can start the workflow for a contact. Trigger filters then narrow who enters: they restrict the trigger to specific forms, payments, tags, or other conditions.

Some filters accept multiple values, and those values combine with OR behavior. If you select three forms on a Form Submitted trigger, the workflow starts when a contact submits any one of the three. See Workflow triggers for the full trigger catalog.

Form triggers without filters

Without additional configuration, a Form Submitted trigger may respond to every form submission in your account, not just the form you had in mind.

A documented example: a volunteer welcome workflow whose Form Submitted trigger was not filtered sent the volunteer email to someone who submitted a conference registration form instead. The same mistake can also apply incorrect tags, send staff notifications, update membership records, or start follow-up sequences for the wrong people.

The fix is to select the specific form in the Form Submitted trigger dropdown. If the workflow should respond to several forms, select them all in the dropdown; multiple selected forms combine with OR behavior. Using Form Submission Triggers walks through the setup.

Payment triggers without filters

Payment Received is the centralized trigger for incoming payments. Without filters it runs for both successful and failed payment attempts, and it can cover one-time purchases, subscription charges, and invoices.

It fires for both initial and later subscription payments. A workflow built for one-time purchases therefore also runs on background subscription charges unless you filter Transaction type (Customer present/first transaction versus Customer not present/subscription transaction) or Payment status (Success versus Failed).

These filters narrow the trigger:

For setup details and examples, see Payment Received workflow trigger.

Duplicate entry points

Two triggers that can both fire for the same contact enroll that contact twice, which causes duplicate emails or tasks.

The common case: a workflow starts on Form Submitted and Tag Added, and submitting the form also adds the tag. Both triggers fire, and the contact enters the workflow twice.

Before adding multiple triggers, ask whether the same person could satisfy more than one trigger at the same time. If so, use only one trigger, split the work across separate workflows, or add conditions that prevent duplicate processing. Multiple triggers in a workflow covers when several triggers make sense.

When an automation ran unexpectedly

Check the trigger filter first. A missing or too-loose filter is the most common reason a workflow started for a contact you did not intend.

To see how a specific contact got in, open their Enrollment History. It covers the last 30 days and shows which path the contact took through the workflow. Workflow History and Logs explains how to read it.

Related articles

• Workflow triggers — the full trigger catalog and how each one fires.

• Using Form Submission Triggers — how to filter a Form Submitted trigger to one form.

• Payment Received workflow trigger — payment filters and setup steps.

• Common automation mistakes — the mistakes behind most unexpected automation runs.

• Workflow History and Logs — check what a workflow actually did for a contact.