Events
Event nodes trigger pattern execution. Every pattern starts with at least one event node.
Event nodes are the entry points for every pattern. They define what causes your pattern to run — a webhook request, a cron schedule, a message from another pattern, or an incoming email. Every pattern must contain at least one event node.
All event nodes are impure and have a pink header. They produce an output execution pin that starts the downstream flow.
On Start
Manual trigger. Execution starts here when you select the Run button in the editor.
| Pin | Direction | Type | Description |
|---|---|---|---|
| Exec | Output | Exec | Fires when the pattern starts |
Impure. Use On Start for patterns you run manually or trigger via the API.
On Webhook
Fires when an HTTP request arrives at the pattern's webhook URL.
| Pin | Direction | Type | Description |
|---|---|---|---|
| Exec | Output | Exec | Fires when a request is received |
| Headers | Output | Object | HTTP headers from the incoming request |
| Body | Output | Object | Parsed request body |
| Method | Output | String | HTTP method (GET, POST, PUT, etc.) |
| URL | Output | String | Full URL of the request |
Properties:
- Webhook Alias — a friendly name for this webhook endpoint.
- Response Mode — controls how the caller receives a response: Immediate (returns 202 right away), Last Node (waits for pattern completion), or Response Node (waits for a Respond to Webhook node).
Impure. Use On Webhook to receive events from external services like GitHub, Stripe, or Slack.
On Schedule
Fires on a cron schedule or interval.
| Pin | Direction | Type | Description |
|---|---|---|---|
| Exec | Output | Exec | Fires on each scheduled tick |
| Timestamp | Output | DateTime | The time the schedule fired |
Properties:
- Schedule — a cron expression (e.g.,
*/5 * * * *for every 5 minutes).
Impure. Use On Schedule for periodic tasks like health checks, data syncs, or report generation.
On Error
Fires when an unhandled error occurs anywhere in the pattern.
| Pin | Direction | Type | Description |
|---|---|---|---|
| Exec | Output | Exec | Fires when an error is caught |
| Error | Output | Object | Error details including message and code |
Impure. Use On Error as a global error handler to log failures, send alerts, or perform cleanup.
On Pattern Call
Entry point when this pattern is invoked by another pattern using the Call Pattern node.
| Pin | Direction | Type | Description |
|---|---|---|---|
| Exec | Output | Exec | Fires when the pattern is called |
| Input | Output | Object | Data passed by the calling pattern |
| Context | Output | Object | Execution context from the caller |
Impure. Use On Pattern Call to build reusable sub-patterns that other patterns invoke.
On Queue Message
Fires when a message arrives from a named queue.
| Pin | Direction | Type | Description |
|---|---|---|---|
| Exec | Output | Exec | Fires when a message is received |
| Message | Output | Object | The message payload |
Properties:
- Queue Name — the name of the queue to listen on.
Impure. Use On Queue Message for asynchronous, decoupled workflows where one pattern enqueues work for another.
On Log Event
Fires when a log event arrives from an external data source (monitoring platform, log aggregator, etc.).
| Pin | Direction | Type | Description |
|---|---|---|---|
| Exec | Output | Exec | Fires when a log event is received |
| Event | Output | Object | The full event payload |
| Source | Output | String | Name of the data source |
| Index | Output | String | Index or collection name |
| Timestamp | Output | String | Event timestamp |
Properties:
- Source Filter — filter events by source name.
Impure. Use On Log Event for detection patterns that react to application logs, alerts, or audit events.
On Receive Email
Fires when an email arrives at the pattern's unique platform-hosted address.
| Pin | Direction | Type | Description |
|---|---|---|---|
| Exec | Output | Exec | Fires when an email is received |
| From | Output | String | Sender address |
| To | Output | String | Recipient address |
| Subject | Output | String | Email subject line |
| Body | Output | String | Plain text body |
| HTML Body | Output | String | HTML body content |
| Headers | Output | Object | Email headers |
| Attachments | Output | Array | List of attachment metadata (filename, type, size) |
| Date | Output | String | Date the email was sent |
| Message ID | Output | String | Unique message identifier |
Impure. Use On Receive Email for workflows triggered by inbound email — phishing analysis, ticket creation, or alert forwarding.
Related categories
- Flow Control — route execution after an event fires
- HTTP — make outbound HTTP requests or respond to webhooks
- Variables — store and retrieve data during execution