Integration
Connect PagerDuty to Brand.dev
When New Incidents fires in PagerDuty, your agent runs Find rows in a collection in Brand.dev. 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 Brand.dev 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 Brand.dev
When New Incidents in PagerDuty
then Find rows in a collection in Brand.dev
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 Brand.dev
Triggers and actions 2 triggers · 45 actions
- List Maintenance Windows
Gets a list of maintenance windows.
- New Incidents
Polls for new incidents in PagerDuty.
- Add Responders
Request additional responders (a user or escalation policy) to help with an incident.
- Add Team Member
Add a user to a team with a given role.
- Create Incident
Creates an incident in PagerDuty.
- Create Note on Incident
Creates a note on a given incident.
- Delete or End a Maintenance Window
Deletes a maintenance window that hasn't started yet, or ends one that is ongoing.
- Get Escalation Policy
Retrieve a single escalation policy by its ID.
- Get Incident
Retrieve a single PagerDuty incident by id.
- Get Schedule
Retrieve a single on-call schedule by its ID.
- Get Service
Retrieve a single PagerDuty service by id.
- Get Team
Retrieve a single team by its ID.
- Get User Information
Gets a user's information based on provided ID.
- List Escalation Policies
List PagerDuty escalation policies.
- List Incident Notes
List all notes attached to an incident.
- List Incidents
List PagerDuty incidents with filters (statuses, service_ids, urgencies, date range).
- List On-Calls
List current on-call entries — who is on call now, by escalation policy/schedule/user/time window.
- List Schedule Overrides
List overrides on a schedule within a required since/until time window.
- List Schedules
List PagerDuty on-call schedules.
- List Services
List PagerDuty services.
- List Teams
List all teams in the account.
- List Users
List PagerDuty users.
- Manage Incidents
Bulk acknowledge or resolve multiple incidents in a single call.
- Snooze Incident
Snooze a triggered/acknowledged incident for a number of seconds so it won't re-alert until the snooze expires.
- Two-way sync add a maintenance window
Creates a maintenance window for use with two-way sync triggers. Does not update. Use only with two-way sync triggers.
- Two-way sync add or update an incident
Creates or updates an incident for use with two-way sync triggers. Use only with two-way sync triggers.
- Update Incident
Updates an incident in PagerDuty. Set status to acknowledged or resolved to manage the incident.
- Update Maintenance Window
Updates a maintenance window.
- Add a monitor
Create a website change monitor.
- Delete a collection
Delete a WebDBs data collection.
- Delete a monitor
Delete a website change monitor.
- Extract Products From a Brand's Website
Beta feature: Extract product information from a brand's website. Brand.dev will analyze the website and return a list of products with details such as name, description, image, pricing, features, and more.
- Find rows in a collection
Query rows stored in a WebDBs data collection.
- Get a batch
Retrieve a batch's status by ID.
- Get a monitor
Retrieve a website change monitor by ID.
- Get batch results
Retrieve the results of a completed batch.
- List batches
List submitted batches.
- List collections
List WebDBs data collections.
- List monitors
List website change monitors.
- Query Website Data Using AI
Use AI to extract specific data points from a brand's website. The AI will crawl the website and extract the requested information based on the provided data points.
- Retrieve Brand Data by Company Name
Retrieve brand information using a company name. This endpoint searches for the company by name and returns its brand data.
- Retrieve person
Retrieve a person's profile data.
- Retrieve Simplified Brand Data by Domain
Returns a simplified version of brand data containing only essential information: domain, title, colors, logos, and backdrops. This endpoint is optimized for faster responses and reduced data transfer.
- Run a monitor
Trigger a website change monitor to run immediately.
- Search company news
Search for recent news articles about a company or brand.
- Update a collection
Update a WebDBs data collection's configuration.
- Update a monitor
Update a website change monitor's configuration.
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 Brand.dev
HubSpot to Brand.devHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to Brand.devSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Brand.devGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Brand.devGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Brand.devGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
PagerDuty and Brand.dev, 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 Brand.dev when something happens in PagerDuty?
Any of Brand.dev's 19 actions, including Update a collection, Update a monitor, Add a monitor and Extract Products From a Brand's Website. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Brand.dev to PagerDuty?
Brand.dev has no triggers in the catalog today, so automations start in PagerDuty. If you need the other direction, ask: your agent reads Brand.dev's API documentation and adds it.
Do I have to build a connector for PagerDuty or Brand.dev?
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 Brand.dev 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.