---
title: "PagerDuty integration: customer context for on-call | Annsa"
product: annsa
url: /integrations/pagerduty
canonical_url: "https://annsa.ai/integrations/pagerduty"
type: integration
related:
  - /docs/automations
  - /integrations/slack
summary: Trigger a PagerDuty incident from a spec with the customer quotes in the payload, so whoever is on call sees who is affected and what they said about it.
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.

# PagerDuty integration: customer context for on-call | Annsa

> Trigger a PagerDuty incident from a spec with the customer quotes in the payload, so whoever is on call sees who is affected and what they said about it.

PagerDuty

## Your on-call team sees what customers said.

Fire a PagerDuty incident from a spec, and the customer quotes ride along in the payload.

[Try Annsa](https://app.annsa.ai/signup)

Category

[Code and operations](https://annsa.ai/integrations#code)

Set up

3 steps

Guide

[See Ship →](https://annsa.ai/direct/handoff)

**One spec, one page, full context.** A wave of “checkout broken” feedback becomes a spec, and the incident it fires carries those quotes.

## On-call, with context.

- **Quotes in the page.** On-call sees what customers said, not just “something is broken.”
- **The right severity.** Annsa maps urgency to critical, warning or info.
- **Wired on purpose.** PagerDuty is never switched on for you. You add the hook when you're ready.

## Key, hook, test.

A standard Events API v2 integration key.

1. **Add the integration key.** Paste an Events API v2 key. Annsa encrypts it and reads it only when an incident fires.
2. **Add the hook.** Settings → Hooks, then add PagerDuty. Fire it by hand from a spec, or when a spec is written.
3. **Check it worked.** Test the connection. Annsa sends a dry-run event to confirm the key.

## Questions people ask.

**Does Annsa page anyone on its own?**

No. An incident fires only from a hook you add, or when you fire it from a spec.

**Why a separate hook for PagerDuty?**

PagerDuty gets incidents that need someone now. Other automations go to Slack or a webhook.

## Goes well with

- [**Slack** Turn what customers say in Slack into what to build next.](https://annsa.ai/integrations/slack)
- [**GitHub** Your agents know your code. You know what shipped.](https://annsa.ai/integrations/github)

[All integrations →](https://annsa.ai/integrations)

## The source of direction for agent teams.

Begin with one agent and the work that matters next.

- [Try Annsa](https://app.annsa.ai/signup)
- [See pricing](https://annsa.ai/pricing)

## Related pages

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

- [Automations](https://annsa.ai/docs/automations)
- [Slack customer feedback integration](https://annsa.ai/integrations/slack)

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