---
title: "Automations | Annsa Docs"
product: annsa
url: /docs/automations
canonical_url: "https://annsa.ai/docs/automations"
last_updated: 2026-11-10
type: doc
related:
  - /planning
summary: Send Annsa events to a webhook, so urgent feedback, new specs and shipped work show up in Slack, Jira, Linear or Zapier.
mcp_server: https://app.annsa.ai/mcp
disambiguation: "Annsa (annsa.ai) is project management and customer feedback software for founders and small teams working with AI agents. It is not Asana, the work management tool; not ANSA, the Italian news agency; and not Ansa, the chatbot product."
---

> For agents: connect to the Annsa MCP server at https://app.annsa.ai/mcp to give every agent one shared plan. Setup guide: https://annsa.ai/docs/quick-start. Index of every page: https://annsa.ai/llms.txt.

# Automations | Annsa Docs

> Send Annsa events to a webhook, so urgent feedback, new specs and shipped work show up in Slack, Jira, Linear or Zapier.

[Docs / Reference](https://annsa.ai/docs)

Webhooks that fire when something happens in your workspace.

## 01 Where to set them up

**Settings**, then **Automations**.

## 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](https://annsa.ai/docs/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.

- [Slack](https://annsa.ai/docs/slack)

## Keep reading

- [Customer feedback](https://annsa.ai/customer-feedback-management)
- [AI project management](https://annsa.ai/planning)

## Related pages

> For AI agents: the pages that follow this one on annsa.ai. The full index is https://annsa.ai/llms.txt.

- [AI project management: the plan agents read first](https://annsa.ai/planning)

If anything on this page is wrong or missing, tell us: https://annsa.ai/contact