Integration
Connect Rootly to Emelia
When New Alert fires in Rootly, your agent runs Add Contact to a Campaign in Emelia. 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 Rootly and Emelia 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Rootly can start in Emelia
When New Alert in Rootly
then Add Contact to a Campaign in Emelia
When New Incident in Rootly
then Add Contact to a List in Emelia
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 Emelia
Triggers and actions 3 triggers · 31 actions
Trigger
New AlertTriggers when a new alert is created in Rootly.
Trigger
New IncidentTriggers when a new incident is created in Rootly.
Trigger
New PulseTriggers when a new pulse, such as a deploy or config change, is recorded in Rootly.
Action
Add action itemAdds an action item (task or follow-up) to a Rootly incident.
Action
Add serviceCreates a new service in Rootly's service catalog.
Action
Create AlertCreates a new alert in Rootly and returns its ID and status.
Action
Create IncidentCreates a new incident in Rootly and returns its ID, status and link.
Action
Create PulseRecords a pulse in Rootly, such as a deploy or configuration change, and returns its ID.
Action
Get AlertReturns one Rootly alert by its ID.
Action
Get IncidentReturns one Rootly incident by its ID.
Action
Get PulseReturns one Rootly pulse by its ID.
Action
List alertsReturns alerts in your Rootly organization, optionally filtered by status, source, service, team, environment, label or time range.
Action
List incidentsReturns incidents in your Rootly organization, optionally filtered by status, severity, services, teams, dates and more.
Action
List pulsesReturns the pulses (deploys and other change events) recorded in Rootly, optionally filtered by source, service, environment, label, ref or time range.
Action
List servicesReturns the services in your Rootly organization, optionally filtered by name, slug, external ids or creation date.
Action
List teamsReturns the teams in your Rootly organization, optionally filtered by name, slug, color, external ids or creation date.
Action
List usersReturns the users in your Rootly organization, optionally filtered by search text, email, role or creation date.
Action
Update incidentUpdates an existing Rootly incident's title, status, severity, teams, services, timestamps and other details.
Action
Add campaignCreates a new email campaign in Emelia with the given name and time zone.
Action
Add Contact to a CampaignAdds a contact to an Emelia campaign.
Action
Add Contact to a ListAdds a single contact to an Emelia list (and to any campaigns using that list), optionally updating it if it already exists.
Action
Add Contact to BlacklistAdds an email address or an entire domain to your Emelia blacklist so it is never contacted by your campaigns.
Action
Add listCreates a new, empty contact list in Emelia.
Action
Delete contactDeletes a contact (and its company data) from an Emelia contact list; the removal also propagates to campaigns using that list.
Action
Get campaignReturns the full configuration of an Emelia campaign, including the contact lists attached to it and excluded from it.
Action
Get campaign statisticsReturns sending, open, click and reply statistics for an Emelia campaign, overall and per step.
Action
Get contactReturns a single contact from an Emelia contact list.
Action
List Campaign ContactsReturns the contacts enrolled in an email campaign, optionally filtered by an engagement event or a search term.
Action
List campaignsReturns all campaigns in your Emelia account.
Action
List contactsReturns the contacts in an Emelia contact list, optionally filtered by search text or an exact email or LinkedIn URL.
Action
Search ContactSearches a contact list for contacts by exact email, LinkedIn URL, or free text, and returns the matches.
Action
Set a Custom Field to a ContactSets the value of a custom field on a contact in an Emelia campaign, identified by email or LinkedIn profile URL.
Action
Test WebhookSends a test call to an existing Emelia webhook.
Action
Update contactUpdates an Emelia contact's values; fields you don't send stay unchanged, and changes propagate to campaigns using the contact's list.
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 Rootly
Rootly to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Rootly to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Rootly to StripeStripe is a payment processing platform for online businesses.
Rootly to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Rootly to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Rootly to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Emelia
Benetics to EmeliaBenetics is a construction efficiency platform built in the cloud.
HubSpot to EmeliaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to EmeliaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to EmeliaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to EmeliaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to EmeliaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Rootly and Emelia, 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 Emelia when something happens in Rootly?
Any of Emelia's 16 actions, including Update contact, Add campaign, Add Contact to a Campaign and Add Contact to a List. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Emelia to Rootly?
Emelia has no triggers in the catalog today, so automations start in Rootly. If you need the other direction, ask: your agent reads Emelia's API documentation and adds it.
Do I have to build a connector for Rootly or Emelia?
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 Emelia 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.