Integration
Connect OutageDeck and Pipefile
When something happens in OutageDeck or Pipefile, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want OutageDeck and Pipefile to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What OutageDeck and Pipefile can do together
From OutageDeck to Pipefile
When New incident in OutageDeck
then Add File Request From Template in Pipefile
From Pipefile to OutageDeck
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with OutageDeck and Pipefile
Triggers and actions 2 triggers · 17 actions
- New incident
Fires 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.
- File Request Created
Triggers when a file request is created.
- Add File Request From Template
Create a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.
- Create Contact
Add to contacts
- Delete Contact
Delete a contact by id. Returns 204 No Content on success.
- Get Contact
Retrieve one contact by id.
- Get File Request
Retrieve detailed information about one file request by id, including contents, items, files, and tracking events.
- List Contacts
Retrieve a paginated list of contacts, filterable by name/email/phone partial match.
- List File Request Templates
Retrieve the list of file request templates available for creating new file requests, with optional name search.
- Search File Requests
Finds all file requests matching this search query (contact name, email, tags, etc).
- Send Request
Create and send a new request
- Update Contact
Update name/email/phone of an existing contact by id.
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
What our customers say
More from OutageDeck
OutageDeck to PolarPolar is a modern billing platform for developers & designers.
OutageDeck to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
OutageDeck to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
OutageDeck to StripeStripe is a payment processing platform for online businesses.
OutageDeck to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
OutageDeck to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Pipefile
HubSpot to PipefileHubSpot is your all-in-one stop for all of your marketing software needs.
Instagram to PipefileInstagram is a social media platform for sharing photos, videos, and stories.
EARLY to PipefileEARLY is a Time Tracking App: Effortless, Smart, and Secure.
Google Sheets to PipefileGoogle Sheets
Gmail to PipefileGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PipefileGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
OutageDeck and Pipefile, answered
What can start an automation from OutageDeck?
Any of OutageDeck's 1 trigger in the catalog, including New incident. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pipefile when something happens in OutageDeck?
Any of Pipefile's 10 actions, including Create Contact, Send Request, Update Contact and Add File Request From Template. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pipefile to OutageDeck?
Yes. When something happens in Pipefile, your agent can act in OutageDeck too. This page covers both directions: Pipefile's triggers and OutageDeck's actions are listed here as well.
Do I have to build a connector for OutageDeck or Pipefile?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.