Integration
Connect OutageDeck to Harness.io
When something happens in OutageDeck, your agent does the next thing in Harness.io. 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 Harness.io 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 Harness.io
Triggers and actions 1 trigger ยท 18 actions
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.
Action
Add ConnectorCreate a new connector (e.g. GitHub, Kubernetes, Docker registry). POST /ng/api/connectors
Action
Add EnvironmentCreate a new deployment environment in a project. POST /ng/api/environmentsV2
Action
Add SecretCreate a new secret (text/file/SSH key) in a scope. POST /ng/api/v2/secrets
Action
Create ProjectCreates a new project in Harness.
Action
Execute PipelineTrigger a pipeline execution. POST /pipeline/api/pipeline/execute/{pipelineIdentifier}
Action
Get PipelineFetch a single pipeline definition by identifier. GET /pipeline/api/pipelines/{pipelineIdentifier}
Action
Get Pipeline ExecutionFetch a pipeline execution's status and details by execution id. GET /pipeline/api/pipelines/execution/{planExecutionId}
Action
Get ProjectFetch a single project by identifier. GET /ng/api/projects/{identifier}
Action
List Pipeline ExecutionsList pipeline executions for a project. POST /pipeline/api/pipelines/execution/summary
Action
List PipelinesList pipelines for a project. POST /pipeline/api/pipelines/list
Action
List ProjectsList projects in the account/org. GET /ng/api/projects
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.