- A trigger is the event that starts a workflow. This video shows where triggers come from, and how you set one on a job.
Workflows
Triggers: what starts a workflow
Where triggers come from, and how a job picks the one it needs.
Email received
Issue createdYour own system
Sort the request: damaged item, delivery question, return or refund.
- An event records that something happened, like Maya Chen's email about order 4821.
- Its type names the provider and what happened. Here, Gmail and email received.
- Its properties hold the content. The sender, the subject, and the text.
An event records what happened
The type says what happened
The properties hold the content
Maya Chen
maya.chen@example.com
Cracked lamp shade
Hi, my order 4821 arrived today and the lamp shade is cracked. Could you send a new one?
Event type
e:
gmailprovider
/
email-receivedname
Properties
{
"from": { "address": "maya.chen@example.com" },
"subject": "Cracked lamp shade",
"body": "Hi, my order 4821 arrived today and the lamp shade is cracked."
}
- Most triggers are events your integrations publish, with no code from you.
- A message in the support inbox is one. An issue created in Linear is another.
- Your own systems post events to the OAIZ API, like the web shop's return requests.
- A custom integration gives them their own provider, such as custom-fjord-shop.
Most triggers come from integrations
Your systems send events to the API
Support inbox
Gmail · a message arrives
Warehouse team
Linear · an issue is created
Fjord Living web shop
Posts to the OAIZ API with an API key
Its own provider and API keys
EventsNewest on top
e:gmail/email-received
Cracked lamp shade · Maya Chen
e:linear/issue-create
Replace the lamp shade for order 4821
e:custom/return-requested
Order 4821 · Lamp shade
e:custom-fjord-shop/return-requested
Order 4821 · Lamp shade
- A finished job can also publish an output event, with its result.
- The sorting job publishes Request sorted. That is the next job's trigger.
- The last job's event, Reply sent, can start a different workflow.
- A Schedule job has no trigger. It starts runs at the times you set.
- This one starts a weekly summary for Sam every Monday at nine.
Jobs publish output events
It is the next job's trigger
Another workflow can start from it
A Schedule job has no trigger
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
PublishesRequest sorted
Next job's triggerRequest sorted
Another workflow
Its triggerReply sent
Start the weekly summary for Sam.
Find last week's customer requests.
Summarise the week's requests.
Send the summary to Sam.
No trigger, a schedule
Runs at the times you set
Every Monday at 09:00 · Europe/Stockholm
- Every job has a Trigger. It picks the one event type that starts the job.
- Show properties opens the latest event of that type, so you see what the job can read.
- Filters narrow the trigger. This job runs only when the message mentions an order.
- Other emails stop there, and the canvas shows Filters not met.
Every job has a Trigger
See what the event carries
Filters narrow the trigger
Other events stop at Filters not met
Email received
Cracked lamp shade
Do you ship to Norway?
Sort the request: damaged item, delivery question, return or refund.
Route by category.
Cracked lamp shade"…my order 4821 arrived…"
Do you ship to Norway?No order in the text
Filters
bodyContainsorder
Sort the requestOverviewAdvanced
General
Trigger
Filters
Event*
e:gmail/email-received
Show propertiesHide properties
from: { address: "maya.chen@example.com" }
subject: "Cracked lamp shade"
body: "Hi, my order 4821 arrived…"
Action
Output event
- Activity lists every stored event, under Events.
- Each row shows the integration, the event type, and when it arrived.
- Open one to see its properties, and the runs it triggered.
- Add Custom Event publishes one by hand, with a provider, a name and properties.
- Every live workflow with that trigger starts, which helps when you test.
Every event is in Activity
Open one to see its properties
Publish one with Add Custom Event
Live workflows with that trigger start
Activity
Overview
Runs
Events
Search events
Select event type
Live Feed
Add Custom Event
Integration
Event type
Created at
Attachments
Support inbox
e:gmail/email-received
26 Oct 2026, 10:22
Warehouse team
e:linear/issue-create
26 Oct 2026, 10:05
Team chat
e:slack/message-channel
26 Oct 2026, 09:48
Support inbox
e:gmail/email-received
26 Oct 2026, 09:31
EventsEvent - e:gmail/email-received
Type:e:gmail/email-received
Created:26 Oct 2026, 10:22
Event properties
{
"from": { "address": "maya.chen@example.com" },
"subject": "Cracked lamp shade",
"body": "Hi, my order 4821 arrived today…"
}
Triggered runs
Customer requests
26 Oct 2026, 10:22Add Custom Event
Publish a custom event.
Event type
Provider
custom
Name
return-requested
Event identifier: e:custom/return-requested
Properties
order
String
4821
Cancel
Publish Event
- Start from the moment the work begins, like a customer writing in.
- Find that event in Activity, and check it carries what the job needs.
- Pick its type under Trigger, and add Filters for the right cases.
- Use a Schedule job for set times, and the API for your own systems.
- You now know where triggers come from. The Events page in the docs has the details.
Choosing the right trigger
Start from what happenedA customer writes in, an issue is created
Check its propertiesIn Activity, under Events
Pick one type, then add FiltersIn the job's Trigger section
Set times, or your own systemsA Schedule job, or events sent to the API
Go deeper in the docs
Events
Event types, properties, and where events come from.
oaiz.io/docs/events