PagerDuty
PagerDuty incident orchestration
PagerDuty is the on-call alerting and incident-response platform that pages the right engineer when production breaks. Tiny Command exposes five actions, no triggers (PagerDuty has webhook subscriptions configured in Services → Integrations → Generic Webhook, or via webhook-v3 subscriptions API; point them at a Tiny Command webhook trigger for "react to a paged incident" workflows): Create Incident (open a new incident on a specific service, with title, urgency, and optional auto-assigned escalation policy), List Incidents (with filters for service, urgency, status, time range), Acknowledge Incident (the responder picked up the page), Resolve Incident (the issue is fixed; PagerDuty stops paging), List Services. The connection uses a PagerDuty API key (account-wide REST API key from Integrations → API Access Keys) or a personal user token. The Events API v2 (used internally by Create Incident) auto-dedupes incidents on dedup_key — multiple alerts for the same problem collapse into one incident, which is the standard fan-in pattern for noisy monitoring sources.
Do anything PagerDuty can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Acknowledge PagerDuty Incident | Marks an incident as acknowledged — stops escalation but keeps it open. For "Slack reaction roller → ack the incident" workflows that integrate chat-based acknowledgement. |
| Create PagerDuty Incident | Opens an incident with title, service, urgency, dedup_key for fan-in. The standard hook for "external monitor detected → page the on-call engineer" workflows. |
| List PagerDuty Incidents | Paginated incidents with filters by service, status, urgency. For "current active incidents" dashboards and post-incident reporting workflows. |
| List PagerDuty Services | Returns the service catalog. Useful for resolving service IDs at workflow setup and for inventorying alert-routing structure. |
| Resolve PagerDuty Incident | Closes an incident. For "monitoring source signals recovery → auto-resolve" or for self-healing systems that emit recovery events. |
Pre-built PagerDuty workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect PagerDuty once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every PagerDuty field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the PagerDuty integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect PagerDuty to Tiny Command?
What PagerDuty triggers does Tiny Command support?
What PagerDuty actions can I run from a workflow?
Is the PagerDuty integration real-time?
Do I need to write code to use PagerDuty with Tiny Command?
How much does the PagerDuty integration cost?
More developer tools apps people connect.
Same category as PagerDuty, ordered by how often teams pair them. Hover the carousel to pause.
Do more with PagerDuty.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
