Automations & Webhooks
Automations react to events in your project without anyone watching. When a defined event happens — for example, a production prompt is updated — an automation fires an action: a webhook, a Slack message, a PagerDuty incident, or a ServiceNow ticket.
Open them from Automations in the left nav.
How an automation is built
| Part | What it is |
|---|---|
| Trigger | An event source (e.g. prompts) and event action (create / update). |
| Filters | Optional conditions that narrow when the automation fires. |
| Action | What happens — Webhook, Slack, PagerDuty, or ServiceNow. |
Action types
| Action | Does |
|---|---|
| Webhook | POSTs the event payload to a URL you control, signed with a secret. |
| Slack | Sends a message to a connected Slack channel. |
| PagerDuty | Raises an incident. |
| ServiceNow | Creates a ticket. |
Slack, PagerDuty, and ServiceNow actions require the matching integration to be connected first.
Creating an automation
Define the trigger
Choose the event source and action (e.g. prompt updated) and add any filters to scope it.
Choose an action
Pick Webhook, Slack, PagerDuty, or ServiceNow, and configure its target (URL, channel, service, etc.).
Secure webhooks
Webhook automations are signed with an auto-generated secret so your endpoint can verify authenticity. You can regenerate the secret at any time.
Activate
Save and activate. Each execution is tracked (success/failure).
Automations that fail repeatedly are auto-disabled after consecutive failures, so a broken endpoint doesn't retry forever. Fix the target and re-enable. Check the execution history if an automation stops firing.
Next steps
- Integrations — connect Slack, PagerDuty, and ServiceNow.
- Prompt Management — the most common automation trigger source.