Integration

Connect Rootly to Zenserp

When New Alert fires in Rootly, your agent runs Reverse image search in Zenserp. Describe the whole flow and it is built, tested on every scenario and kept running.

Rootly3 triggers Rootly15 actions Zenserp9 actions

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 Rootly and Zenserp to do together?

Ask the assistant

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

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

Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide

Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide

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

Grok

Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.

Setup guide

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

Example flows

What Rootly can start in Zenserp

When New Alert in Rootlythen Reverse image search in Zenserp
When New Incident in Rootlythen Get trending Google searches in Zenserp

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 Rootly and Zenserp

Triggers and actions 3 triggers · 24 actions

Trigger
New Alert
Triggers when a new alert is created in Rootly.
Trigger
New Incident
Triggers when a new incident is created in Rootly.
Trigger
New Pulse
Triggers when a new pulse, such as a deploy or config change, is recorded in Rootly.
Action
Add action item
Adds an action item (task or follow-up) to a Rootly incident.
Action
Add service
Creates a new service in Rootly's service catalog.
Action
Create Alert
Creates a new alert in Rootly and returns its ID and status.
Action
Create Incident
Creates a new incident in Rootly and returns its ID, status and link.
Action
Create Pulse
Records a pulse in Rootly, such as a deploy or configuration change, and returns its ID.
Action
Get Alert
Returns one Rootly alert by its ID.
Action
Get Incident
Returns one Rootly incident by its ID.
Action
Get Pulse
Returns one Rootly pulse by its ID.
Action
List alerts
Returns alerts in your Rootly organization, optionally filtered by status, source, service, team, environment, label or time range.
Action
List incidents
Returns incidents in your Rootly organization, optionally filtered by status, severity, services, teams, dates and more.
Action
List pulses
Returns the pulses (deploys and other change events) recorded in Rootly, optionally filtered by source, service, environment, label, ref or time range.
Action
List services
Returns the services in your Rootly organization, optionally filtered by name, slug, external ids or creation date.
Action
List teams
Returns the teams in your Rootly organization, optionally filtered by name, slug, color, external ids or creation date.
Action
List users
Returns the users in your Rootly organization, optionally filtered by search text, email, role or creation date.
Action
Update incident
Updates an existing Rootly incident's title, status, severity, teams, services, timestamps and other details.
Action
Get trending Google searches
Lists searches currently trending on Google (up to the past 7 days), optionally narrowed to keywords, country, language or category.
Action
Reverse image search
Finds web pages that contain a given image, using Google reverse image search.
Action
Search Bing
Runs a live Bing search for a query and returns the organic results, related searches, images and videos from the results page.
Action
Search Google
Returns live Google search results for a query, including organic results and ads.
Action
Search Google images
Returns Google Images results for a search query, with optional location and image filters.
Action
Search Google maps
Searches Google Maps for local businesses matching a query and returns each place's name, address, rating, reviews and coordinates.
Action
Search Google news
Returns Google News articles matching a search query, optionally localized by location, language or date range.
Action
Search Google shopping
Searches Google Shopping and returns the product offers found for a query, with prices, stores, ratings and product ids.
Action
Search YouTube
Searches YouTube and returns the matching videos with their ranking, title, length and channel.

Each app on its own

Reviews

What our customers say

More into Zenserp

Questions

Rootly and Zenserp, answered

What can start an automation from Rootly?

Any of Rootly's 3 triggers in the catalog, including New Alert, New Incident and New Pulse. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Zenserp when something happens in Rootly?

Any of Zenserp's 9 actions, including Get trending Google searches, Reverse image search, Search Bing and Search Google. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Zenserp to Rootly?

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

Do I have to build a connector for Rootly or Zenserp?

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 Rootly and Zenserp 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.

Connect Rootly to Zenserp

What do you want Rootly and Zenserp to do together?

What Rootly can start in Zenserp

Triggers and actions 3 triggers · 24 actions

Each app on its own

What our customers say

More from Rootly

More into Zenserp

Rootly and Zenserp, answered

What can start an automation from Rootly?

What can your agent do in Zenserp when something happens in Rootly?

Can it also run from Zenserp to Rootly?

Do I have to build a connector for Rootly or Zenserp?

Can my AI client use Rootly and Zenserp without building an automation?

What happens when something fails?

Is there a free plan?