PagerDuty Incident Digest

Daily digest of open PagerDuty incidents, delivered to your InTouch subscribers. Keeps on-call leads and engineering managers aware of what is currently firing without anyone having to log into PagerDuty.

Use case

Every morning, see the open PagerDuty incidents (triggered + acknowledged) in a single readable message — counts, urgencies, affected services — pushed to whatever channels your subscribers use (email, Slack, Discord, Telegram).

What it does each run

1. fetch-incidents (pagerduty tool) — calls the PagerDuty REST API list_incidents operation, filtered to the triggered and acknowledged statuses (limit 50). The connector publishes exactly two outputs: {{fetch-incidents.result}} (the raw JSON API response) and {{fetch-incidents.status}} (the HTTP status code).
2. summarize (ai tool) — feeds {{fetch-incidents.result}} to the AI provider and produces a concise, human-readable markdown digest (total count, one bullet per incident with title / urgency / status / service / created time, high-urgency first). Publishes answer.
3. notify-digest (message tool) — wraps {{summarize.answer}} into a notification and sends it to the intouch user's subscribers. The HTTP status from step 1 is appended for diagnostics.

alertOnError: true means the intouch user is also notified if the workflow itself fails (e.g. an expired or revoked API token).

Required credentials

PagerDuty API key

The apiKey property on the fetch-incidents task is set to the placeholder <set via credential>. You supply the real key — do not hardcode it in the YAML. Two options:

• Credential (recommended) — create a credential of the pagerduty type and reference it; InTouch injects the key as the task's apiKey at runtime, keeping it in the encrypted vault and out of the workflow definition.
• Runtime environment variable — store the key in a runtime env and reference it (e.g. apiKey: "{{env.PAGERDUTY_API_KEY}}").

Generate the token in the PagerDuty web app under Integrations → API Access Keys (account-level) or My Profile → User Settings → Create API User Token (user-level). It is sent as Authorization: Token token=.... This is a static REST API token — no interactive OAuth flow is required.

AI provider

The summarize step uses the ai tool with model: claude-sonnet-4-6. You need a configured AI provider credential (Anthropic, OpenAI, Gemini, or a local Ollama model). Swap the model value to match the provider you have set up.

Schedule

Attach a daily schedule (e.g. 08:00 local) so the digest lands at the start of the working day.

Customizing

• Quieter digest — narrow the statuses filter to triggered only.
• Include resolved — add resolved to the statuses value to also recap what was cleaned up.
• Bigger page — raise limit (1–100) for busy accounts.