Skip to main content

​
The trigger defines how the workflow starts

The trigger is the event that starts the workflow and provides the first input. That makes it one of the most important design choices in the whole automation. A workflow with the wrong trigger often becomes harder to understand, harder to test, and harder to trust.

​
Start with the real event

Ask:
  • what exact event should start this process
  • should the workflow begin because something happened or because time passed
  • what input data should be available at the start
Those answers usually point you toward the right trigger quickly.

​
Common trigger patterns

These are the most common starting points:
  • Webhook when another system should send data into Workflow Machine
  • Schedule when the workflow should run at a recurring time
  • RSS when the workflow should react to feed updates
  • App event trigger when a connected integration already provides the event you need
Choose the trigger that most naturally matches the process instead of forcing the workflow into an awkward shape.

​
A workflow can have more than one trigger

Some workflows use multiple triggers. These triggers are independent from each other. Each one can start the workflow on its own and send data into the same workflow logic without affecting the others. This is useful when you want the same sequence of steps to run from multiple sources.

​
Configure the trigger with testing in mind

A good trigger is easy to validate before publishing. That usually means:
  • the event is easy to reproduce
  • the incoming data is understandable
  • the downstream steps can inspect what the trigger produced
If trigger behavior is unclear, everything that follows becomes harder to debug.

​
Common trigger mistakes

Watch out for these early problems:
  • using a schedule when a real event trigger is a better fit
  • choosing a webhook without understanding the payload structure
  • using a trigger that fires more often than the workflow really needs
  • assuming the trigger data will always have the same shape
  • adding too many triggers before the first working path is stable
Many workflow issues look like step problems at first, but the real cause often starts at the trigger.

​
What to do after adding the trigger

Once the trigger is set up:
  1. inspect what data it provides
  2. confirm that the data matches your expectations
  3. add only the steps that depend on that input
  4. run a test as early as possible
The sooner you validate the trigger, the easier the rest of the workflow becomes.