Integration
Connect CRUSH to PagerDuty Events API
When something happens in CRUSH, your agent does the next thing in PagerDuty Events API. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want CRUSH and PagerDuty Events API to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with CRUSH and PagerDuty Events API
Triggers and actions 1 trigger · 4 actions
Trigger
Receive NoteTriggers when a new note is captured in CRUSH. Returns the note's transcript and the date it was created.
- Create Note
Creates a new note in CRUSH from the transcript text you provide. Returns the id of the note that was created.
Action
Change Alert StateAcknowledge or resolve an existing PagerDuty alert via the Events API v2, using its dedup key.
- Send Change Event
Record a non-alerting change event (deploy, config change) in PagerDuty via the Events API v2.
- Trigger Alert
Trigger a new PagerDuty alert via the Events API v2.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.