Integration

Connect Hex to PagerDuty Events API

When List Groups fires in Hex, your agent runs Send Change Event in PagerDuty Events API. 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 Hex and PagerDuty Events API to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One 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.ai

Start 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)

Hex tells you when an API-triggered run appears for a project, and the PagerDuty Events API turns that into something your on-call rotation can see. You can raise an alert on a failed run, record a non-alerting change event for a successful one, and acknowledge or resolve an existing alert by its dedup key once Hex reports the project is healthy again.

Example flows

What Hex can start in PagerDuty Events API

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 Hex and PagerDuty Events API

Triggers and actions 4 triggers · 3 actions

Each app on its own

Reviews

What our customers say

More from Hex

More into PagerDuty Events API

Questions

Hex and PagerDuty Events API, answered

Can the agent close a PagerDuty alert after a Hex project recovers?

Yes. The Change Alert State action acknowledges or resolves an existing alert using its dedup key, so a later New Project Run in Hex that comes back clean can resolve the alert raised by the earlier run.

Will this work the other way, from PagerDuty into Hex?

No. Hex offers triggers only and the PagerDuty Events API connector offers actions only, so every scenario starts with something found or run in Hex and ends in PagerDuty.

What can start an automation from Hex?

Any of Hex's 4 triggers in the catalog, including List Groups, List Projects, New Project Run and List Users. Describe the moment in plain language and your agent picks the right one.

What can your agent do in PagerDuty Events API when something happens in Hex?

Any of PagerDuty Events API's 3 actions, including Change Alert State, Send Change Event and Trigger Alert. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from PagerDuty Events API to Hex?

PagerDuty Events API has no triggers in the catalog today, so automations start in Hex. If you need the other direction, ask: your agent reads PagerDuty Events API's API documentation and adds it.

Do I have to build a connector for Hex or PagerDuty Events API?

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 Hex and PagerDuty Events API without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in PagerDuty Events API 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.