Events
Events are the data packets that flow through OAIZ. Every automation starts with an event, and understanding their structure is key to building effective workflows.
Click to enlarge
What is an Event?
An event is a structured data packet that represents something that happened — an email arrived, a form was submitted, a task was completed. Events contain:
- Event Type — An identifier like
e:gmail/email-receivedthat categorizes the event - Properties — The actual data payload (email body, sender info, etc.)
- Metadata — System info like UUID, timestamp, and source integration
Where Events Come From
Events in OAIZ can originate from:
- Integrations — Connected services like Gmail, Slack, or GitHub automatically emit events when things happen
- Jobs — When a job completes, it can emit an output event that triggers downstream jobs in a chain
- API — Your systems can send events directly via the OAIZ API
Event Structure
When you configure a job to listen for an event type, you'll work with its properties — the data fields available in that event. Here's an example of a Gmail email-received event:
{
"body": "Hi! I want to sign up to your service...",
"date": "2025-01-15T14:39:51Z",
"from": {
"address": "customer@example.com",
"display_name": "Jane Smith"
},
"history_id": "4627",
"id": "19a78826962bac81",
"labels": ["UNREAD", "INBOX"],
"subject": "Sign up request",
"thread_id": "19a78826962bac81",
"to": [{ "address": "support@yourcompany.com" }]
}Show full event metadata
{
"uuid": "019a7882-6962-bac8-1000-000000000001",
"organisationUuid": "019a7812-f9ff-7a59-94fd-18d23475ee09",
"eventTypeIdentifier": "e:gmail/email-received",
"timestamp": "2025-01-15T14:39:51Z",
"properties": {
"body": "Hi! I want to sign up to your service...",
"date": "2025-01-15T14:39:51Z",
"from": {
"address": "customer@example.com",
"display_name": "Jane Smith"
},
"history_id": "4627",
"id": "19a78826962bac81",
"labels": ["UNREAD", "INBOX"],
"subject": "Sign up request",
"thread_id": "19a78826962bac81",
"to": [{ "address": "support@yourcompany.com" }]
},
"userUuid": null,
"namespaceId": null,
"userIdentifier": null,
"userAggregationId": null,
"uniqueKey": "a1b2c3d4e5f6...",
"integrationUuid": "019b08bf-5f2a-7bfb-ae75-59ab7ce5a18d"
}The properties object is what your jobs work with. You reference these fields using the {{ properties.fieldName }} syntax in your job configuration. For nested fields, use dot notation like {{ properties.from.address }}.
Viewing Event Details
Click any event in the list to view its full details, including all properties and metadata:
Click to enlarge
The Event Details view shows:
- Event Info — UUID, Event Type identifier, and timestamp
- User Info — Associated user UUID and identifier (if applicable)
- Event Properties — The full JSON payload with all data fields
Events View Overview
The Events view lists all events flowing through your workspace. Use it to monitor activity, debug automations, or understand what data is available.
Action Area
| Action | Description |
|---|---|
| Apply to chat context | Add selected events to the Chat context for reference when building automations |
Filtering Events
Use filters to find specific events:
- Search — Full-text search in event data
- Event Type — Filter by event type identifier
- Date Range — Filter by time period
- Integration — Filter by source integration
Events in Your Automations
How Jobs Use Events
Events are the foundation of OAIZ automations. Each job listens for a specific event type and uses its properties as input data.
- Input Event — The event type that triggers your job (e.g.,
e:gmail/email-received) - Properties — Reference event data in your action using
@autocomplete - Output Event — Optionally emit a new event with custom properties for downstream jobs
Using Events in Chat
Select events and click Apply to chat context to reference them when talking to the AI assistant. This helps when debugging or building automations based on specific events.