- Every job in a workflow runs one action. This video shows the actions a job can run, and how to choose between them.
Actions
What actions a job can run
The work a job can do, and how to pick the right one.
- An action is the work a job does. It reads the event that started the job, and returns a result.
- Each job card names its action along the bottom.
- In Customer requests, an LLM call sorts Maya's email, and a Decision routes it.
Every job runs one action
The card names its action
Each action is one kind of work
Email received
Sort the request: damaged item, delivery question, return or refund.
Route by category.
Log damaged items for the warehouse team.
Draft a reply that follows the Returns policy.
Tell #support about refund requests.
Sam approves the reply before it is sent.
Send the approved reply to the customer.
EventReply sent
EventIssue logged
EventTeam told
Reads the eventEmail received
Returns a result
Request sorted
- An LLM call sends one prompt to a model, with what the job gives it.
- From Maya's email, it returns the order number, 4821, and the problem, a cracked shade.
- An Agent works in rounds. Each round, the model answers, or calls the tools you selected.
- Its Storage Query tool finds Maya's earlier refund, on order 4612.
- Choose an LLM call when the event and attached knowledge hold everything the model needs.
- Choose an Agent when the job has to fetch more data, or take action in a connected service.
An LLM call makes one request
An Agent works in rounds
Which one to choose
LLM Call
One request
Email received
Maya Chen · Cracked lamp shade
Maya Chen · Cracked lamp shadeMy order 4821 arrived today and the lamp shade is cracked.
Returns its result
action.orderNumber 4821
action.problem "Cracked lamp shade"
Agent
1Calls Storage Query
Refund requests
Maya Chen · order 4612 · September
2Reads the result and answers
Tools you selectedStorage Query
LLM CallThe event and knowledge hold everything
AgentIt must fetch more data, or act in a connected service
- Decision answers typed questions, such as which kind of request a message is. It returns answers and probabilities, never written text.
- Image generation creates pictures from a prompt, and attaches the files to an event.
- Code execution runs Python, to add up an order total or build a CSV file.
Answers, images and code
Decision
Answers typed questions that later jobs use in their Filters.
ChoiceWhich kind of request is Maya's email
Damaged itemProbability 0.91
Answers and probabilities, never written text.
Image Generation
PromptA Fjord Living table lamp on a white background
Attached to the event
Code Execution
Runs Python to calculate values, transform data or create files.
main.py
Order 4821 total€129.00
order-4821.csv
- Schedule starts runs at set times, like a request summary every Monday at nine.
- Delay holds a job's output for a set time, so a follow-up reaches Maya three days later.
- Wait for event holds the run until a matching event arrives, or a deadline passes.
- Human approval holds a proposed output for a person. Sam checks the reply before it is sent.
When work happens, and who signs off
Schedule
Starts runs at set times
Every Monday 09:00
Summarise last week's requests
Delay
Holds the output for a set time
Waiting for delay · 3 days
Follow-up to Maya
Wait for Event
Waits for a matching event, or a deadline
Return received · order 4821
or
Deadline · 1 week
Human Approval
Holds a proposed output for a person
Waiting for approval
Sam approves the reply
- Create knowledge and Update knowledge write documents, like a weekly summary of requests.
- Query database reads rows, and Write to database changes them, here adding a row for order 4821.
- Webhook sends an HTTP request to another system, like order 4821's status to the warehouse.
- An integration action runs one action in a connected account, such as a message to your team chat.
- Agent and Code execution jobs can call the same integration actions too.
Keep records
Reach other systems
Knowledge and databases
Create Knowledge, Update Knowledge
Write knowledge documents
Request summary · week 45
Knowledge and databases
Query database, Write to database
Read rows, or change them
Damage reports
Row added · order 4821
HTTP
Webhook
Sends an HTTP request and uses its response
POST · order 4821 · Replacement sent
200
Integration actions
Integration action
Runs one action in a connected account
Slack · Send Message
#support
Slack · Send Message
#support
Also available toAgentCode Execution
- Each job's action tells you what kind of work it does.
- You can now tell when a job needs an LLM call, and when it needs an Agent.
- The Actions section of the docs has a page for every action.
Reading a job's action
Name the action behind each jobThe card shows it along the bottom
Choose an LLM call or an AgentAn Agent when the job needs tools
Go deeper in the docsActions has a page for every action
ActionsDocs
Models and code
Time and approval
Knowledge and databases
HTTP
Integration actions