What is a trigger?

A trigger is the event that starts a pattern's execution. Every pattern needs exactly one trigger node, placed at the beginning of the execution flow.

Trigger types

On Webhook

Starts the pattern when an HTTP request hits the pattern's webhook URL.

Each pattern with a webhook trigger gets a unique, stable URL
URLs survive undeploy and redeploy — you can safely register them with external services
The request body, headers, and query parameters are available as output pins
Supports GET, POST, PUT, PATCH, and DELETE methods

Use for: GitHub events, Slack commands, Stripe notifications, or any HTTP-based integration.

Tap mode: When building a webhook-triggered pattern, you can enable tap mode to capture a real incoming payload in the editor. This lets you inspect the exact data structure your pattern will receive, making it easier to wire up downstream nodes correctly.

On Schedule

Runs the pattern on a recurring schedule.

Configure with standard cron expressions (e.g., */5 * * * * for every 5 minutes)
Supports complex schedules: 0 9 * * MON-FRI (weekdays at 9 AM)
Built-in catch-up: if the execution engine restarts, missed ticks within the last hour fire automatically

Use for: Periodic health checks, data sync, report generation, cleanup jobs.

On Pattern Call

Makes a pattern callable by other patterns via the Call Pattern node.

Define typed input and output pins — callers must match the interface
Works like a function call: the caller blocks until the called pattern completes
Results flow back through the output pins

Use for: Shared logic, reusable building blocks, composing complex workflows from smaller pieces.

On Start

Runs the pattern immediately when you select Run in the editor. This is the simplest trigger — it takes no configuration and has no external event source.

Use for: Manual testing, one-off scripts, and patterns you trigger by hand from the dashboard.

Choosing a trigger

Trigger	Best for	Starts when
On Webhook	External integrations, event-driven workflows	HTTP request received
On Schedule	Periodic tasks, polling, maintenance	Cron schedule fires
On Pattern Call	Reusable sub-workflows, shared logic	Another pattern calls it
On Start	Manual testing, one-off tasks	You select Run or Execute

Most patterns use On Webhook for event-driven automation or On Schedule for periodic tasks. Use On Pattern Call when you want to build reusable logic that multiple patterns share.

Patterns — the workflows that triggers start
Deployments — triggers only fire on deployed patterns
Executions — the runs that triggers create

Triggers