Integration
Connect PagerDuty to FilePost
When New Incidents fires in PagerDuty, your agent runs Update file in FilePost. Describe the whole flow 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 PagerDuty and FilePost to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 PagerDuty can start in FilePost
When New Incidents in PagerDuty
then Update file in FilePost
When List Maintenance Windows in PagerDuty
then Upload File in FilePost
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 PagerDuty and FilePost
Triggers and actions 2 triggers · 36 actions
Trigger
List Maintenance WindowsGets a list of maintenance windows.
Trigger
New IncidentsPolls for new incidents in PagerDuty.
Action
Add RespondersRequest additional responders (a user or escalation policy) to help with an incident.
Action
Add Team MemberAdd a user to a team with a given role.
Action
Create IncidentCreates an incident in PagerDuty.
Action
Create Note on IncidentCreates a note on a given incident.
Action
Delete or End a Maintenance WindowDeletes a maintenance window that hasn't started yet, or ends one that is ongoing.
Action
Get Escalation PolicyRetrieve a single escalation policy by its ID.
Action
Get IncidentRetrieve a single PagerDuty incident by id.
Action
Get ScheduleRetrieve a single on-call schedule by its ID.
Action
Get ServiceRetrieve a single PagerDuty service by id.
Action
Get TeamRetrieve a single team by its ID.
Action
Get User InformationGets a user's information based on provided ID.
Action
List Escalation PoliciesList PagerDuty escalation policies.
Action
List Incident NotesList all notes attached to an incident.
Action
List IncidentsList PagerDuty incidents with filters (statuses, service_ids, urgencies, date range).
Action
List On-CallsList current on-call entries — who is on call now, by escalation policy/schedule/user/time window.
Action
List Schedule OverridesList overrides on a schedule within a required since/until time window.
Action
List SchedulesList PagerDuty on-call schedules.
Action
List ServicesList PagerDuty services.
Action
List TeamsList all teams in the account.
Action
List UsersList PagerDuty users.
Action
Manage IncidentsBulk acknowledge or resolve multiple incidents in a single call.
Action
Snooze IncidentSnooze a triggered/acknowledged incident for a number of seconds so it won't re-alert until the snooze expires.
Action
Two-way sync add a maintenance windowCreates a maintenance window for use with two-way sync triggers. Does not update. Use only with two-way sync triggers.
Action
Two-way sync add or update an incidentCreates or updates an incident for use with two-way sync triggers. Use only with two-way sync triggers.
Action
Update IncidentUpdates an incident in PagerDuty. Set status to acknowledged or resolved to manage the incident.
Action
Update Maintenance WindowUpdates a maintenance window.
Action
Create Intake LinkCreates a FilePost intake link — a public upload page you can send to someone so they can drop files to you, with your own limits on file type, size, count and how long it stays open.
Action
Delete FilePermanently deletes a file from FilePost. The stored file and its public link are removed and cannot be recovered.
Action
Delete intake linkCloses a FilePost intake link so it stops accepting uploads. Files already uploaded through it are untouched, and the slot frees up against your plan's limit on active links.
Action
Get fileReturns the details FilePost holds about one stored file — its name, size, type, download link and when it expires.
Action
Get intake linkReturns one intake link from your FilePost account, looked up by its intake link ID. FilePost has no single-link endpoint, so the link is selected out of your full list of intake links.
Action
List FilesReturns the files stored in your FilePost account, newest first, together with the total number of files.
Action
List intake linksReturns the intake links on your FilePost account, with each link's label, public upload page, limits and expiry.
Action
Update fileChanges whether a stored file's name appears in its public link, and returns the file with its new link.
Action
Upload FileUploads a file to FilePost and returns its shareable link.
Action
Upload File From URLStores a file from a public web link in FilePost and returns its shareable link.
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 PagerDuty
PagerDuty to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
PagerDuty to StripeStripe is a payment processing platform for online businesses.
PagerDuty to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
PagerDuty to PipedrivePipedrive is a sales CRM and pipeline management tool.
PagerDuty to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
PagerDuty to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into FilePost
HubSpot to FilePostHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to FilePostSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to FilePostSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to FilePostGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to FilePostGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to FilePostGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
PagerDuty and FilePost, answered
What can start an automation from PagerDuty?
Any of PagerDuty's 2 triggers in the catalog, including New Incidents and List Maintenance Windows. Describe the moment in plain language and your agent picks the right one.
What can your agent do in FilePost when something happens in PagerDuty?
Any of FilePost's 10 actions, including Create Intake Link, Update file, Upload File and Upload File From URL. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from FilePost to PagerDuty?
FilePost has no triggers in the catalog today, so automations start in PagerDuty. If you need the other direction, ask: your agent reads FilePost's API documentation and adds it.
Do I have to build a connector for PagerDuty or FilePost?
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.
Can my AI client use PagerDuty and FilePost without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.