Replace
{workspace_id}, {trigger_id}, and {environment} with values from your trigger config. Assign the correct Agent Build in DEV before testing these examples.Request Details
- Method:
POST - Authorization: Bearer Token (workspace-level)
- Content-Type:
application/json
Sample Payload
Replace:{workspace_id}with your workspace ID{trigger_id}with your trigger ID{environment}with DEV / UAT / PRODworkspace_api_keywith your workspace token
Error Responses
Common Use Cases
- Automated incident response from monitoring systems
- Scheduled data processing and reporting
- Webhook-triggered workflows from external platforms
- Background batch processing with real-time progress tracking
- Long-running data transformation and enrichment tasks
- Periodic system health checks and maintenance routines
Notes & Best Practices
- Validate bearer tokens: Always verify authentication in DEV environment before deploying to PROD.
- Use user_variables for context: Pass structured data through
user_variablesinstead of embedding everything in the message field. - Poll status intelligently: When using background tasks, implement appropriate polling intervals (e.g., every 5-10 seconds) to check status without overwhelming the API.
- Monitor execution time: Be aware of the 2700-second maximum for background tasks. Design flows to complete within this limit.
- Test thoroughly: Always test in DEV environment before promoting to UAT and PROD.
- Keep triggers descriptive: Use clear, meaningful names for triggers to facilitate internal reference and debugging.
- Handle webhooks appropriately: Validate payload shape and auth before promoting webhook callers to PROD.

