Integration
Connect OutageDeck to Pipedream
When something happens in OutageDeck, your agent does the next thing in Pipedream. 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 Pipedream 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 Pipedream
Triggers and actions 3 triggers ยท 41 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.
Trigger
New accountFires when a new app account appears in the project.
- New project
Fires when a new project is created in the workspace.
- Create account
Connect an app account on behalf of an end user.
- Create connect token
Create a short-lived token that lets an end user connect an account.
- Create project
Create a new project in your Pipedream workspace.
- Delete account
Disconnect and remove a single connected account.
- Delete deployed trigger
Remove a deployed trigger so it stops emitting events.
- Delete project
Permanently remove a project from your workspace.
- Delete user
Remove an end user and all of their connected accounts.
- Deploy trigger
Deploy a trigger for an end user so it starts emitting events.
- Get account
Retrieve the details of a single connected account.
- Get action
Retrieve the definition of a single action.
- Get app
Retrieve the details of a single app in Pipedream's catalog.
- Get component
Retrieve the definition of a single component.
- Get deployed trigger
Retrieve the details of a single deployed trigger.
- Get project
Retrieve the details of a single project.
- Get trigger
Retrieve the definition of a single trigger.
- List accounts
List the app accounts your end users have connected in a project.
- List accounts for user
List the accounts a specific end user has connected.
- List actions
Browse the actions available to run for a project's apps.
- List apps
Browse the apps available in Pipedream's integration catalog.
- List components
Browse the components available in a project.
- List deployed triggers
List the triggers currently deployed in a project.
- List projects
List the projects in your Pipedream workspace.
- List trigger events
Retrieve the recent events emitted by a deployed trigger.
- List triggers
Browse the triggers available to deploy for a project's apps.
- List users
List the end users who have connected accounts in a project.
- Proxy GET request
Send an authenticated GET request to a connected app's API on behalf of an end user.
- Proxy PATCH request
Send an authenticated PATCH request to a connected app's API on behalf of an end user.
- Proxy POST request
Send an authenticated POST request to a connected app's API on behalf of an end user.
- Proxy PUT request
Send an authenticated PUT request to a connected app's API on behalf of an end user.
- Run action
Run an app action on behalf of an end user and return its result.
- Set trigger webhook
Send a deployed trigger's events to one webhook address, replacing any addresses it currently sends to.
- Update deployed trigger
Change the configuration of a deployed trigger.
- Update project
Change the name or settings of an existing project.
- Validate connect token
Check whether a Connect token is still valid.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews