Integration
Connect OutageDeck to Benchmark Email
When something happens in OutageDeck, your agent does the next thing in Benchmark Email. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want OutageDeck and Benchmark Email 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 OutageDeck and Benchmark Email
Triggers and actions 1 trigger ยท 13 actions
Trigger
New incidentFires when a new incident is reported for a tracked provider or service.
- Get incident
Get an incident's detail including its full update timeline, by incident slug.
- Get platform status
Get the platform-wide status overview: directory stats, every tracked provider's current status, and the most recent incidents.
- Get provider
Get details for a single tracked provider by its slug.
- Get service
Get details for a single service by its slug.
- List incidents
List incidents, filterable by provider, severity, lifecycle state, and page/limit.
- List providers
List tracked service providers, filterable by free-text search, status, category, and sort order.
- List services
List services, filterable by provider, current status, and free-text search.
Action
Add CampaignCreate a new email campaign. POST /api/email/campaign
- Create List
Create a new list to organize your contacts.
- Delete Contact
Delete a contact by id. DELETE /api/contact/{contactId}
- Find Contact
Search for a contact by email address.
- Remove Contact From List
Remove a contact from a list.
- Update Campaign
Update an existing email campaign by id. PATCH /api/email/campaign/{campaignId}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.