Skip to main content

​
What a workflow is

A workflow is an automation that starts with a trigger and completes a sequence of steps. In Workflow Machine, a workflow is the main unit of work you build, test, publish, and monitor. It is the container that brings together:
  • the event that starts the automation
  • the steps that process data or take action
  • the connections that let steps talk to external apps
  • the runs that show what happened over time

​
The basic workflow model

Most workflows follow the same structure:
  1. A trigger starts the workflow.
  2. One or more steps process the input.
  3. The workflow creates an output, update, notification, or downstream action.
That structure can be simple or complex, but the core model stays the same.

​
A workflow can have multiple triggers

Some workflows use more than one trigger. These triggers are independent from each other. Each trigger can start the workflow on its own and send data into the same sequence of workflow steps without affecting the other triggers. This is useful when you want the same workflow logic to run from multiple sources. For example, you might want the same follow-up process to start from a webhook, a schedule, or an app event without rebuilding the whole workflow each time.

​
What makes up a workflow

The most important parts of a workflow are:
  • Trigger: the event that starts the workflow
  • Steps: the actions and logic that happen after the trigger
  • Connections: the authenticated app accounts the steps can use
  • Runs: the execution records created when the workflow actually runs
  • Versions: saved changes over time, especially around publishing
If you understand those five concepts, you understand most of the product.

​
Workflows are designed to be tested

A workflow is not just a diagram. It is something you can test before making it live. That matters because most automation issues come from:
  • trigger setup
  • missing or invalid connections
  • incorrect field mapping
  • assumptions about the shape of incoming data
Workflow Machine is structured to help you catch those issues before they affect real work.

​
Workflows are designed to be reused and improved

You do not need to build the perfect workflow immediately. A common pattern is:
  1. Start with one trigger and one outcome.
  2. Confirm a successful run.
  3. Add more logic, branching, and integrations later.
That is usually a better path than trying to design an advanced workflow before you have seen any real runs.

​
A good way to think about workflows

If you are new to the product, think of a workflow as:
  • one process
  • with one starting event
  • and one repeatable way of handling that event
Once you think in those terms, it becomes much easier to decide what belongs in a workflow and what should be a separate automation.