Integration
Connect OutageDeck to Cloudflare Trace
When something happens in OutageDeck, your agent does the next thing in Cloudflare Trace. 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 Cloudflare Trace 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 Cloudflare Trace
Triggers and actions 1 trigger · 9 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
Get geolocation infoLook up the geolocation Cloudflare reports for this automation's own outbound requests — city, region, country, postal code, latitude and longitude — plus the IP address, network operator (ASN) and the Cloudflare data center serving it, from Cloudflare's speed-test metadata endpoint. Takes no input.
- Get trace info
Fetch the requester's IP address, timestamp, user agent, country code, TLS/HTTP version, and other network metadata from Cloudflare's trace endpoint.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.