Trigger
Category: Trigger
Node id: trigger
Handles event-based triggers: manual, webhook, schedule, condition, and event matching
What it does
- Manual trigger activation with user attribution
- Webhook trigger with optional signature validation
- Schedule-based trigger with timezone-aware evaluation
- Condition-based trigger with AND/OR logic operators
- Event matching trigger by type and source
- Comparison operators: eq, ne, gt, lt, gte, lte, contains, matches
- Automatic next-run calculation for schedule triggers
Use cases
- Start a pipeline manually from the UI or API
- React to incoming webhook events from external services
- Run pipelines on a recurring schedule (every minute/hour/day/week)
- Trigger downstream processing only when specific conditions are met
- Match and route incoming events by type and source
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
payload | json | No | Event payload data. In production, injected by the trigger system. For testing, provide via fixture or override. |
metadata | json | No | Additional metadata for the event |
signature | text | No | Webhook signature for validation (webhook type) |
event_type | text | No | Event type string for event-based triggers (e.g. 'patient.created') |
event_source | text | No | Event source identifier for event-based triggers |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Full trigger result with event, reason, and metadata |
triggered | boolean | No | Whether the trigger condition was met |
success | boolean | No | Whether the trigger processing completed |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Trigger Type | type | enum | No | manual | manual, webhook, schedule, condition, event | Type of trigger mechanism |
| Source | source | string | No | Source identifier for the trigger | ||
| Triggered By | triggered_by | string | No | manual | Identifier for who triggered (manual type) | |
| Webhook URL | webhook_url | string | No | URL for webhook trigger | ||
| Schedule | schedule | string | No | Schedule expression (e.g. 'every hour') | ||
| Conditions | conditions | array | No | Array of conditions for condition trigger | ||
| Event Type | event_type | string | No | Expected event type to match (event type) |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| HTTP Method | method | string | No | POST | HTTP method for webhook | |
| Validate Signature | validate_signature | boolean | No | false | Whether to validate webhook signatures | |
| Timezone | timezone | string | No | UTC | Timezone for schedule evaluation | |
| Logic | logic | enum | No | and | and, or | How to combine conditions (condition type) |
| Event Source | event_source | string | No | Expected event source to match (event type) |
Errors
| Code | Description |
|---|---|
UNSUPPORTED_TRIGGER_TYPE | Trigger type is not one of: manual, webhook, schedule, condition, event |
MISSING_SCHEDULE | Schedule expression is required for schedule trigger but was empty |
MISSING_CONDITIONS | Conditions array is required for condition trigger but was nil |
MISSING_EVENT_TYPE | Event type is required for event trigger but was empty |
MISSING_SIGNATURE | Webhook signature validation enabled but no signature provided |
Runtime notes
- Wire the 'triggered' boolean to a branch/condition node to gate downstream execution
- Schedule triggers return a 'next_run' timestamp in result; condition triggers include evaluated 'conditions' array
- Condition trigger evaluates payload fields against conditions using AND/OR logic — fields come from inputs map
- Event IDs are auto-generated and unique per invocation (evt_{timestamp}_{counter})
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Etwas unklar? Senden Sie Feedback zur Dokumentation per E-Mail..