Docs / Workflows / Jobs
Jobs
A job runs one action in a workflow. The job editor sets the event that starts it, the Filters it checks, the action it runs and the event it publishes.
A job listens for one event type, checks each event against its Filters and runs one action, such as an LLM Call or a Slack message. When the action finishes, the job can publish an output event that starts the next job. A workflow is a set of jobs linked this way.
The job editor
Selecting a job on the canvas opens the job editor in a side panel. The same editor opens as a full page, Edit Job, from links to the job in other parts of the app. Adding a job on the canvas first opens New job, a short form for the job type, name and main fields. Open full editor continues in the complete editor.
The header shows the action’s icon and the job name. Select the name to rename the job. For an integration action, the integration and its action appear under the name. More actions, the down arrow beside the name, holds Copy job, Access and Delete job. Delete job is in the side panel only. Save appears once the job has unsaved changes. In the side panel, Show Results opens the job’s recorded results after it has run.
- Overview
- A summary of the job: Name, Description, Action Type and the action’s main fields, such as the prompt and model of an LLM Call. The prompt of an LLM Call or Agent can be changed from here through Model & prompt settings.
- Advanced
- Every setting, in four collapsible sections: General, Trigger, Action and Output event. A Schedule job has no Trigger section. When a save fails validation, the editor opens Advanced at the field to fix.
Saving from the canvas writes to a draft of the workflow. If you were viewing the live version, the editor switches to a draft, and the live workflow runs unchanged until Go live.
Name, description and notifications
The General section holds the job’s Name, Description and Notify on failure. Name is required and identifies the job on the canvas and in run records. Description is optional.
Notify on failure decides whether a failure of this job emails the person who manages the job’s account, normally the person who created the job. Auto follows the workflow’s setting. Enabled and Disabled override it for this job. Runs explains the email and the workflow setting.
- Copy job
- Opens Copy / Paste Job Configuration. Copy shows the Job UUID and the job’s last saved configuration as JSON, so save first to include recent edits. Paste replaces the editor’s values with a pasted configuration after checking it, matches its integrations to yours and removes knowledge documents your account does not have. Save the job to keep the result. Copy job does not create a second job.
- Delete job
- Removes the job from the workflow’s draft after a confirmation. When later jobs depend on its output event, Repair & Delete reconnects the jobs before and after it. Delete without repair leaves them disconnected.
Trigger
Trigger sets the event type that starts the job. Event lists the event types available to you as e:provider/name and also accepts a typed identifier. Show properties opens the latest event of that type with its properties, the values that Filters and references read.
For an integration’s events, Source connection chooses the connection the events come from. Any Slack integration, for example, accepts events from every Slack connection. Source connection appears when you have more than one connection to that service or one is already chosen.
A job that earlier jobs start warns before you change its event type, because saving the change disconnects it from them. A Schedule job has no trigger and starts from its own schedule.
Filters
Filters decide whether an event that reached the job runs its action. The Filters button in the Trigger section opens them once an event type is chosen. A job without Filters runs for every event of its type.
Each filter compares one Field of the event with an Expected value. Field lists the event’s properties and accepts a typed path. The comparisons offered depend on the field’s type.
- Text
- Equals, Does Not Equal, Contains, Does Not Contain, Starts With, Does Not Start With, Ends With and Does Not End With.
- Numbers, IDs and dates
- Equals, Does Not Equal, Greater Than and Less Than. A date value uses the form YYYY-MM-DDTHH:MM:SSZ.
- True or false
- Equals and Does Not Equal, with true or false.
Add opens Add filter, which adds a filter, and Add nested group, which adds a group of filters. Between the items of one group, choose AND or OR. The choice applies to the whole group. AND needs every item to match and OR needs one. A nested group shows ALL filters must match (AND) or ANY filter can match (OR) and counts as one item of the group around it. Groups nest up to two levels below the top level.
When an event does not pass, the action does not run and the job publishes no output event, so the jobs after it do not start from that event. The canvas marks the job Filters not met. This is a separate outcome from a failed action, and the run records it.
Event properties and references
Event properties are the named values an event carries, such as an order ID or a question. A field in the job reads one through a reference such as {{ properties.question }}, which is replaced with the event’s value when the job runs. Type @ in a field to insert a property. In a prompt, @ also tags knowledge documents.
The action’s results are available as references such as {{ action.summary }}. The output event uses them to pass results to later jobs.
Action
Action Type chooses what the job does. The list has Built-in actions, such as LLM Call, Agent, Webhook and Code Execution, and Integrations, the actions of your connected services. Changing the type resets the action’s settings to the defaults of the new type.
The fields under Action Type belong to the chosen action, and each action’s page explains them. An integration action needs one of your integrations to publish or run. LLM Call and Agent keep their model, prompt, tools and skills in Model & prompt settings.
Timeout limits how long the action runs, from 10 to 3600 seconds, with 60 as the default. For LLM Call and Agent it is in Model & prompt settings. Schedule, Human Approval, Delay and Wait for Event manage their own timing.
Knowledge documents
LLM Call, Agent and Decision jobs can attach knowledge documents. They appear under Knowledge documents in the Action section and in Model & prompt settings. Add Knowledge searches your documents, and each attached document can be removed from the list.
When the job runs, LLM Call and Agent give the documents’ content to the model. Decision adds it to the state its questions judge. A document that was deleted, or that you cannot open, shows as Unavailable document. Saving the job gives its account access to attached documents, as Access control describes.
Output event
The output event is the event the job publishes after its action finishes. A later job whose trigger is this event type starts from it, and the canvas draws that connection. The switch at the top of the section turns the output event on or off. Turning it off disconnects the later jobs when you save.
Event Identifier names the event type as e:provider/name, for example e:support/reply-drafted. It cannot equal the job’s own trigger event, which would start the job again. Changing it disconnects the jobs that listen for the old identifier when you save. When jobs form a loop through their events, the identifier that closes it is marked Cycle source.
- New properties from this action
- Values produced by the action, written as references such as {{ action.summary }}. The + button lists the action’s known outputs or adds a custom property.
- Forwarding properties
- Values copied unchanged from the input event, such as an order ID that later jobs still need. Add all input properties forwards every one.
Each property has a Name, a Type and its Content. Type is String, Integer, Float, Boolean, List or Object. Later jobs receive only the properties listed here, so a value they need must be added to this event.
Access
Each job runs as its own job account, separate from the people who edit it. Share dialogs list it under the name Job: followed by the job’s name. Knowledge documents, databases and integration tools check that account’s access when the job runs.
Access in More actions opens Manage access, the access held by the job account. Its tabs are Knowledge documents, Databases, Integrations and Events. Add or remove documents and choose View or Edit for each. Add or remove integration tools the same way. Databases lists the databases the job’s settings use, at the level they need. Events sets the events the job can read, either Any or Selected sources. Give access saves the list and gives the access shown. When part of it needs someone with more access, the dialog says so.
When a save leaves an Agent able to read text from other people and also send or delete data, the dialog first asks about Prompt injection risk. Allow lets the Agent use those tools together. Until someone allows it, the Agent runs without its send and delete tools.