1. This video puts the parts of a workflow together, from the first event to every path it takes.
Workflows

What a workflow is

How events, jobs and paths fit together, from the first event to every branch.

Email received
Read the email and find the order number.
Draft a reply that follows the Returns policy.
Route the request: refund or delivery.
Tell #support about the refund for this order.
Ask the warehouse to check the delivery.
EventRefund requested
  1. A workflow is a set of jobs on one canvas, connected through events.
  2. An event starts it. Maya's email arrives as Email received, the event type the first job waits for.
  3. The job checks its Filters and runs its action. Here, an LLM call finds the order number.
  4. Then it publishes an output event, Request read, and the jobs listening for it start next.

Jobs connected by events

An event starts it

The job checks, then acts

Its output event starts the next jobs

Email received
Read the email and find the order number.
EventRequest read
Maya Chen
Cracked lamp shade
1Waits for
Email received
2Checks its Filters
The email passes
3Runs its action
LLM Callfinds Order 4821
4Publishes an output event
Request read"order": "4821"
The jobs listening for it start next
  1. Several jobs can listen for the same event. Two jobs here wait for Request read.
  2. When it arrives, both start and run side by side. One event has started two parallel paths.
  3. One path drafts a reply to Maya. The other decides where her request goes.

Several jobs can listen

One event, two parallel paths

Each path does its own work

Path 1
Drafts a reply to Maya
Path 2
Decides where her request goes
Email received
Read the email and find the order number.
Draft a reply that follows the Returns policy.
Route the request: refund or delivery.
EventRequest read
Both listen forRequest read
  1. To choose a path, this workflow uses a Decision. It answers one question, refund or delivery.
  2. The Decision publishes its answer on an event. Each job after it checks that answer with its own Filters.
  3. Maya's lamp shade arrived cracked, so the answer is refund. The delivery job shows Filters not met.
  4. When Jonas asks where his order is, the delivery path runs instead.

A Decision chooses the path

Each job checks its own Filters

Maya's request takes the refund path

Jonas's question takes the delivery path

Email received
Read the email and find the order number.
Draft a reply that follows the Returns policy.
Route the request: refund or delivery.
Tell #support about the refund for this order.
Ask the warehouse to check the delivery.
Maya Chen
Cracked lamp shade
Jonas Berg
Where is my order
Filters
category is refundPassesFilters not met
Filters
category is deliveryPassesFilters not met
Decision
Answers refund or delivery
Publishes Request routed"category": "refund""category": "delivery"
  1. A job only sees the event that started it. The refund job never sees Maya's email, only the Decision's event.
  2. So a value that a later job needs has to travel on the output events.
  3. Each job here passes on the order number, 4821, so the refund message can name the order.

A job sees only the event that started it

Values travel on output events

Pass on what later jobs need

Email received
Read the email and find the order number.
Draft a reply that follows the Returns policy.
Route the request: refund or delivery.
Tell #support about the refund for this order.
Ask the warehouse to check the delivery.
The refund job sees
Request routedfrom the Decision
Email receivedMaya's email
Output events carry values
Later jobs receive only the properties listed on the event
Request read"order": "4821"
Request routed"order": "4821"
Message to #support
Refund requested for order 4821.
  1. An output event can also start another workflow. The refund path ends by publishing Refund requested.
  2. A second workflow, Refunds, listens for that event, and starts when it arrives.
  3. In a test run, that only happens when Publish Events is on in Permissions.

An output event can start another workflow

Refunds listens for it

In a test, only with Publish Events

Customer requests
Email received
Read the email and find the order number.
Draft a reply that follows the Returns policy.
Route the request: refund or delivery.
Tell #support about the refund for this order.
Ask the warehouse to check the delivery.
EventRefund requested
Refunds
Refund requested
Sam approves the refund for the order.
Publish Events Each step publishes an event that other jobs and workflows can listen for.
In a test run, Permissions decide
  1. You edit a workflow as a draft, and a draft does not react to real events.
  2. Go live publishes the draft. From then on, each matching event starts the live version.
  3. Every pass through it is a run, and Logs shows what each job did.
  4. Now you can read a workflow as events and jobs, and see where it splits, branches and hands off.
  5. The Workflows page in the docs goes deeper.

You edit a draft

Go live for real events

Each pass is a run, read in Logs

Read any workflow

Email received
Read the email and find the order number.
Draft a reply that follows the Returns policy.
Route the request: refund or delivery.
Tell #support about the refund for this order.
Ask the warehouse to check the delivery.
EventRefund requested
Customer requestsDraftGo liveDiscard PublishedLive
Run workflow Logs
LogsLive Feed
StartedStatusSummaryDurationCost
10 Nov 2026, 09:26:40Triggered runSucceeded All steps completed4 steps completed 5.912s€0.0018
10 Nov 2026, 09:12:04Triggered runSucceeded All steps completedOutput event emitted 6.204s€0.0021
Draft
Real events do not start it
Live
Each matching event starts it
Maya Chen
Cracked lamp shade
Events and jobsAn event starts each job, and its output event starts the next
SplitsSeveral jobs listen for one event and run side by side
BranchesA Decision answers, and Filters choose the path
Hand-offsAn output event can start another workflow
Go deeper in the docsWorkflows