Integration

Connect Peerdom to SIGNL4

When New Group fires in Peerdom, your agent runs Resolve Alert in SIGNL4. 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 Peerdom and SIGNL4 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)

Peerdom holds the circles, roles and projects your team works from; SIGNL4 reaches whoever is on duty. Joining them means changes in your org map show up as alerts on people's phones, and the agent can look up the role or peer record first so the alert carries real detail instead of a bare notice.

Example flows

What Peerdom can start in SIGNL4

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 Peerdom and SIGNL4

Triggers and actions 5 triggers · 27 actions

Each app on its own

Reviews

What our customers say

More from Peerdom

More into SIGNL4

Questions

Peerdom and SIGNL4, answered

Can something in SIGNL4 start a flow that changes Peerdom?

No. SIGNL4 has no triggers here, so every flow starts from a Peerdom event such as a new role, peer, group, project or map. From there the agent can send, fetch or resolve a SIGNL4 alert and write back to Peerdom with actions like Add Goal or Assign Role to Peer.

Can the alert include details about the new role or project?

Yes. The agent can run Get Role, Get Project or Get Peer in Peerdom first and put that detail into the title and text of the SIGNL4 alert. It tests every scenario, including the case where the record has no peer assigned yet.

What can start an automation from Peerdom?

Any of Peerdom's 5 triggers in the catalog, including New Group, New Map, New Peer and New Project. Describe the moment in plain language and your agent picks the right one.

What can your agent do in SIGNL4 when something happens in Peerdom?

Any of SIGNL4's 3 actions, including Resolve Alert, Send Alert and Get Alert. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from SIGNL4 to Peerdom?

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

Do I have to build a connector for Peerdom or SIGNL4?

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 Peerdom and SIGNL4 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.