Settings, then Automations.
01 Where to set them up
02 What can trigger one
| Event | When it fires |
|---|---|
| Feedback received | A new item is imported from any source |
| Priority created | A new priority is created |
| Priority updated | A priority's rank or score changes significantly |
| Spec generated | A new spec is created for a priority (spec.created) |
| Feature shipped | A spec is marked Shipped |
03 Where it sends
Each automation POSTs to a webhook URL you choose. Typical uses: send urgent feedback to Slack, open a Jira ticket when a spec is created, notify Linear when something ships, or start a Zapier or Make workflow.
04 What arrives
A POST with a JSON body. The data block varies by event, but every payload carries the event name, a timestamp and the workspace id. The sample shows one illustrative data field. The sample shows one illustrative data field.
{
"event": "spec.created",
"timestamp": "2026-03-24T09:00:00Z",
"workspace_id": "ws_abc123",
"data": { "priority_number": 42 }
}
05 Keep it quiet
A webhook on Feedback received fires once for each imported item, so use automations for events you would act on. The activity log shows when they fire, so you can debug from there.
06 Agents don't need one
Your agent reads the board with annsa.priorities when it starts work, so it doesn't need a webhook to find out what changed. Automations send events to tools outside Annsa.