- This video takes one job apart, from the event that starts it to the event it passes on.
Jobs
What is a job
One step of a workflow. An event starts it, it runs one action, and it passes the result on.
Email received
Sort the request: damaged item, delivery question, return or refund.
Write a reply that follows the Returns policy.
Save the reply as a draft.
- Here is the Customer requests workflow. Each job on the canvas is one step.
- This job writes the reply to Maya Chen about her cracked lamp shade, on order 4821.
- Each job waits for an event, runs one action, and can publish an event of its own.
Each job is one step
This job writes the reply
Every job works the same way
Email received
Sort the request: damaged item, delivery question, return or refund.
Write a reply that follows the Returns policy.
Save the reply as a draft.

Maya Chen
Cracked lamp shade · Order 4821
1Waits for an event
The event type it listens for starts it
2Runs one action
Here, an LLM call writes the reply
3Can publish an event
Its output event starts the next job
- A job's Trigger names the one event type that starts it.
- The first job listens for Email received. This one listens for Request sorted, from the job before it.
- Filters narrow the trigger. A job without Filters runs for every event of its type.
- This job checks that the category is damaged item. Maya's request passes, so the job runs.
- When Jonas asks where his order is, his request stops at the Filters. The canvas shows Filters not met.
An event starts a job
Any event type can be a Trigger
Filters narrow the trigger
Maya's request passes
Jonas's request stops at Filters not met
Email received
Sort the request: damaged item, delivery question, return or refund.
Write a reply that follows the Returns policy.

Maya Chen
Cracked lamp shade

Jonas Berg
Where is my order
First job's Trigger
Email received
This job's Trigger
Request sorted
Filters
None, so every Request sorted event runs the job
categoryEqualsdamaged itemPassesFilters not met
Write a replyOverviewAdvanced
General
Trigger
Filters
Event*
e:support/request-sorted
Show properties
Action
Output event
- Once an event passes, the job runs one action. Action Type chooses which.
- Built-in actions include an LLM call, an Agent and Code Execution. Integrations add the actions of your connected tools.
- This job is an LLM call. A model writes the reply from the prompt and Maya's message, which the event carries.
A job runs one action
Built-in actions and integrations
This job is an LLM call
Sort the request: damaged item, delivery question, return or refund.
Write a reply that follows the Returns policy.
Save the reply as a draft.
Request sorted carries
"message": "My order 4821 arrived cracked…"
Write a replyOverviewAdvanced
General
Trigger
Action
Action Type*
LLM CallPrompt
Write a reply to this customer message: {{ properties.message }}
Output event
- When the action finishes, the job can publish an output event.
- This job publishes Reply drafted. It carries the reply the model wrote.
- Later jobs receive only what this event carries, so it also passes on the order number, 4821.
- The draft job listens for Reply drafted, so it starts next.
It can publish an output event
The event carries the result
Pass on what later jobs need
The next job starts
Write a reply that follows the Returns policy.
Save the reply as a draft.
Reply drafted
"reply": "Hi Maya, I'm sorry…"
"order": "4821"
Write a replyOverviewAdvanced
General
Trigger
Action
Output event
Event Identifier*
e:support/reply-drafted
New properties from this action
replyString{{ action.reply }}
Forwarding properties
orderString{{ properties.order }}
- LLM calls, Agents and Decisions can also attach knowledge documents.
- This job has Returns policy attached, so the model gets your policy when it writes.
- Each job runs as its own job account. Documents, databases and integration tools check that account's access.
- Saving the job gives that account View access to Returns policy. Share dialogs list it as Job: Write a reply.
A job can read knowledge
The model gets your policy
Each job has its own account
Saving gives it access
Write a replySaveOverviewAdvanced
General
Trigger
Action
Action Type*
LLM CallKnowledge documents
Returns policy
Output event
Can attach knowledge documents
LLM CallAgentDecision
Returns policy
Knowledge document
Given to the model each time the job runsJob: Write a reply
Job account, separate from the people who edit the job
Knowledge documentsReturns policy · View
Databases
Integration tools
In the Share dialog of Returns policy
- Select a job on the canvas, and the job editor shows each part under Trigger, Action and Output event.
- Now you can read any job. The event that starts it, its Filters, its action, and the event it passes on.
- The Jobs page in the docs has every setting.
Every part is in the job editor
Read any job
Email received
Sort the request: damaged item, delivery question, return or refund.
Write a reply that follows the Returns policy.
Write a replyOverviewAdvanced
General
Trigger
Action
Output event
TriggerThe one event type that starts the job
FiltersWhich of those events run the action
ActionThe one thing the job does, such as an LLM call
Output eventWhat it passes on to the next jobs
Go deeper in the docsJobs
Slack