1. 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 created
Your own system
Monday 09:00
Sort the request: damaged item, delivery question, return or refund.
  1. An event records that something happened, like Maya Chen's email about order 4821.
  2. Its type names the provider and what happened. Here, Gmail and email received.
  3. 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

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."
}
  1. Most triggers are events your integrations publish, with no code from you.
  2. A message in the support inbox is one. An issue created in Linear is another.
  3. Your own systems post events to the OAIZ API, like the web shop's return requests.
  4. 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
Custom integration
EventsNewest on top
e:gmail/email-received
Cracked lamp shade · Maya Chen
10:22
e:linear/issue-create
Replace the lamp shade for order 4821
10:24
e:custom/return-requested
Order 4821 · Lamp shade
10:30
e:custom-fjord-shop/return-requested
Order 4821 · Lamp shade
10:31
  1. A finished job can also publish an output event, with its result.
  2. The sorting job publishes Request sorted. That is the next job's trigger.
  3. The last job's event, Reply sent, can start a different workflow.
  4. A Schedule job has no trigger. It starts runs at the times you set.
  5. 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
  1. Every job has a Trigger. It picks the one event type that starts the job.
  2. Show properties opens the latest event of that type, so you see what the job can read.
  3. Filters narrow the trigger. This job runs only when the message mentions an order.
  4. 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
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
  1. Activity lists every stored event, under Events.
  2. Each row shows the integration, the event type, and when it arrived.
  3. Open one to see its properties, and the runs it triggered.
  4. Add Custom Event publishes one by hand, with a provider, a name and properties.
  5. 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
Oaiz e:custom/return-requested 26 Oct 2026, 10:31
Support inbox e:gmail/email-received 26 Oct 2026, 10:22
Oaiz e:support/request-sorted 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:22
Succeeded
Add Custom Event
Publish a custom event.
Event type
Provider
custom
Name
return-requested
Event identifier: e:custom/return-requested
Properties
order
String
4821
Add Property
Cancel Publish Event
  1. Start from the moment the work begins, like a customer writing in.
  2. Find that event in Activity, and check it carries what the job needs.
  3. Pick its type under Trigger, and add Filters for the right cases.
  4. Use a Schedule job for set times, and the API for your own systems.
  5. 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