There are several concepts to keep in mind when understanding how workflows. This section introduces each concept, and each concept is explained in greater detail in our documentation.
- Workflows: A workflow defines a series of actions which run every time events are received, or on a schedule.
- Triggers: A trigger defines how a workflow runs. There are two types of triggers: "scheduled triggers" or "event triggers"
- Scheduled triggers: These run workflows on a schedule, eg. every 15 minutes.
- Event triggers: These run workflows each time a specific event is received, eg. triggering a workflow when the "signup.new" event is received.
- Actions: Actions are serverless functions that run within a workflow. You can write your own actions in any language, or use our built ins. See the action documentation for more information.
- Edges: Define the order in which actions should run. For example, to have a workflow first run action A; then B; then C an edge will link the trigger to A; A to B; and B to C.
- Async edges: An async edge waits for another event to continue. This allows you to coordinate events within your system.
- Baggage: Baggage defines the data that is built up within your workflow. At the beginning, baggage contains the initial event data. As each action runs, the action's output is added to the baggage and can be used in future actions within the same workflow.