Triggers
Nodes for starting workflows from external events.
Trigger nodes initiate workflow execution in response to external events, HTTP requests, scheduled times, or message queue events.
Available Nodes
| Node | Description |
|---|---|
| REST | HTTP endpoint trigger for REST APIs |
| GraphQL | GraphQL endpoint trigger |
| Schedule | Cron-based scheduled execution |
| Kafka | Apache Kafka message consumer |
| RabbitMQ | RabbitMQ message queue consumer |
HTTP Triggers
REST Trigger
Exposes an HTTP endpoint that starts workflow execution when called.
Configuration:
- HTTP method (GET, POST, PUT, DELETE, PATCH)
- Path pattern with optional parameters
- Request body parsing (JSON, form data)
- Authentication requirements
GraphQL Trigger
Exposes a GraphQL endpoint for query and mutation operations.
Configuration:
- Schema definition
- Resolver mapping to workflow inputs
- Query/mutation type selection
Scheduled Triggers
Schedule Trigger
Execute workflows on a recurring schedule using cron expressions.
Configuration:
- Cron expression (e.g.,
0 9 * * 1-5for weekdays at 9 AM) - Timezone setting
- Optional payload data
Message Queue Triggers
Kafka Trigger
Consume messages from Apache Kafka topics.
Configuration:
- Broker connection settings
- Topic name
- Consumer group ID
- Message deserialization format
RabbitMQ Trigger
Consume messages from RabbitMQ queues.
Configuration:
- Connection URL
- Queue name
- Exchange and routing key
- Acknowledgment mode
Integration Triggers
Some integration nodes also serve as triggers:
- Telegram: Bot webhook for incoming messages
- Gmail: Push notifications for new emails
- Bitrix24: Webhook events
- amoCRM: Webhook events
- Google Calendar: Calendar event notifications
- Linear: Issue update webhooks