Skip to main content
Triggers define how workflows are initiated. Workflows can be triggered by incoming WhatsApp messages, project events, or external API calls.

Trigger types

WhatsApp message trigger
  • Starts workflow when message received on specific WhatsApp number
  • Intercepts messages before they reach agents
  • Provides message content and user context to workflow
WhatsApp event trigger
  • Starts workflow when WhatsApp events occur (message and conversation lifecycle)
  • Runs in observer mode (read-only, no outbound messages unless overridden)
  • Access event data, conversation state, and message details
API trigger
  • Starts workflow via HTTP POST request
  • Programmatic workflow execution from external systems
  • Pass custom variables and context data
Project event trigger
  • Starts workflow when a custom project event is emitted
  • Optionally filters by one event property
  • Runs in observer mode (read-only, no outbound messages unless overridden)
For configuration, available context, and caveats, see Use project events in workflows.

WhatsApp message trigger

When active, starts the workflow when messages are received on the configured WhatsApp number. Configuration
  • Select WhatsApp configuration (phone number)
  • Only one workflow can have an active WhatsApp trigger per number
Available context

WhatsApp event trigger

Starts workflows when WhatsApp message and conversation events occur. Workflows run in observer mode: they can read event data but cannot send messages unless a step explicitly overrides the destination phone number. Configuration
  • Select event type (message or conversation event)
  • Optionally scope to specific WhatsApp number
  • Only one workflow per event type per number
Available events Message events:
  • whatsapp.message.received - New message from customer
  • whatsapp.message.sent - Message sent to WhatsApp
  • whatsapp.message.failed - Message delivery failed
Conversation events:
  • whatsapp.conversation.created - New conversation initiated
  • whatsapp.conversation.ended - Conversation closed
Observer mode Event-triggered workflows run in observer mode:
  • Cannot send outbound messages by default
  • Send steps (text, template, interactive) are skipped
  • To send messages: configure “To phone number” in send step
Available context
Testing event triggers Test event triggers from the Flow Test modal:
  • Select trigger type: “WhatsApp Event”
  • Choose conversation ID
  • Select event type
  • Test execution runs in observer mode
  • Use phone number override in send steps to test outbound messages

API trigger

Execute workflows programmatically via HTTP API. Perfect for integrating workflows with external systems, webhooks, or custom applications. Endpoint
Request parameters
phone_number_id validation
  • Must belong to your project (direct or via customer)
  • Returns 422 error if invalid or doesn’t belong to project
  • When omitted, uses project’s default WhatsApp config
  • Preferred over deprecated whatsapp_config_id
Response
Burst rate limit
  • This endpoint has an additional burst limiter scoped by API key and workflow_id
  • legacy / free: 5 requests per second
  • pro: 15 requests per second
  • enterprise / platform: 30 requests per second
  • Successful responses include X-Burst-RateLimit-Limit and X-Burst-RateLimit-Remaining
  • If exceeded, the API returns 429 Too Many Requests with Retry-After: 1
  • General platform API rate limits still apply
Example API call

Workflow context

Triggered workflows receive context data based on the trigger type: WhatsApp message trigger context
WhatsApp event trigger context
API trigger context

Managing triggers

Triggers are managed via the web interface:
  1. Go to Workflow settings
  2. Add a WhatsApp, project event, or API trigger
  3. Configure trigger settings
  4. Activate/deactivate as needed
See Use project events in workflows for project event triggers. See Project events for emitting and querying events through the API.