Integration
Connect Swiftype to OutageDeck
When something happens in Swiftype, your agent does the next thing in OutageDeck. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Swiftype and OutageDeck 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 Swiftype and OutageDeck
Triggers and actions 2 triggers ยท 21 actions
Trigger
New DocumentTriggers when a new Document is created.
Action
Add domainAdd a crawler domain to an Engine. POST /api/v1/engines/{engine_id}/domains.json with url.
Action
Add engineCreate a new Engine (index). POST /api/v1/engines.json with name.
Action
Create DocumentCreates a new Document.
Action
Delete documentDelete a document by document_id from a document type. DELETE /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{document_id}.json
Action
Delete domainRemove a crawler domain from an Engine. DELETE /api/v1/engines/{engine_id}/domains/{domain_id}.json
Action
Delete engineDelete an Engine by id. DELETE /api/v1/engines/{engine_id}.json
Action
Get documentRetrieve a single document by external_id from a document type. GET /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{external_id}.json
Action
Get engineRetrieve a single Engine by id or name. GET /api/v1/engines/{engine_id}.json
Action
List documentsList documents within a document type/engine. GET /api/v1/engines/{engine_id}/document_types/{document_type}/documents.json
Action
List domainsList crawler domains configured on an Engine. GET /api/v1/engines/{engine_id}/domains.json
Action
List enginesList all Engines for the account. GET /api/v1/engines.json
Action
Recrawl domainTrigger a recrawl of a domain's crawled content. PUT /api/v1/engines/{engine_id}/domains/{domain_id}/recrawl.json
Action
Search documentsPerform full-text search over documents within an Engine. GET/POST https://search-api.swiftype.com/api/v1/public/engines/search.json with engine_key + q. Returns matching records grouped by document type.
Action
Update documentUpdate fields on an existing document. PUT /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{document_id}/update_fields.json
Trigger
New incidentFires when a new incident is reported for a tracked provider or service.
Action
Get incidentGet an incident's detail including its full update timeline, by incident slug.
Action
Get platform statusGet the platform-wide status overview: directory stats, every tracked provider's current status, and the most recent incidents.
Action
Get providerGet details for a single tracked provider by its slug.
Action
Get serviceGet details for a single service by its slug.
Action
List incidentsList incidents, filterable by provider, severity, lifecycle state, and page/limit.
Action
List providersList tracked service providers, filterable by free-text search, status, category, and sort order.
Action
List servicesList services, filterable by provider, current status, and free-text search.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.