Trigger runs via Webhook

RWX now supports triggering automation runs from third-party webhooks, enabling teams to respond to PagerDuty or Datadog alerts by analyzing incidents, rolling back deployments, or executing custom workflows. Webhook triggers are defined as infrastructure as code in a run definition’s `on` section, with incoming headers and payload data made available to tasks through initialization parameters. The workflow can verify webhook authenticity using provider-specific signature-verification packages, such as PagerDuty’s verification package, before proceeding with automation. After publishing a webhook definition, users can find its endpoint URL and token in the RWX Runs page and configure external providers to send POST requests with the token in the `x-rwx-webhook-token` header. This expands RWX’s existing cron- and manually triggered automation capabilities with event-driven workflows.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.