Integration
Connect incident.io and Opteo
When New Incident fires in incident.io, your agent runs Update Changelog Email in Opteo, or Budget Updated in Opteo to Find Users On-Call in incident.io. 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 incident.io and Opteo 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 incident.io and Opteo can do together
From incident.io to Opteo
When New Incident in incident.io
then Update Changelog Email in Opteo
When New Incident in incident.io
then List Completed Improvements in Opteo
From Opteo to incident.io
When Budget Updated in Opteo
then Find Users On-Call in incident.io
When New Alert in Opteo
then Add follow-up in incident.io
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 incident.io and Opteo
Triggers and actions 5 triggers · 30 actions
Trigger
New IncidentTriggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode.
Action
Add follow-upCreates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels.
Action
Add incident updateShares an update on an incident: a message, a move to a new status, a new severity, or any combination.
Action
Create IncidentCreates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields.
Action
Find Users On-CallFinds the users on-call for a schedule over a window of time (or right now), returning each effective shift with its user after overrides are applied.
Action
Get incidentReturns a single incident, including its status, severity, role assignments, timestamps and custom field values.
Action
Get ScheduleReturns a single on-call schedule, including its rotations, time zone and current shifts.
Action
List actionsReturns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date.
Action
List incidentsReturns incidents in your incident.io account, optionally filtered by status, severity, type, mode and created/updated dates.
Action
List schedulesReturns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift.
Action
List severitiesReturns every incident severity configured for your incident.io organisation.
Action
List usersReturns the users in your incident.io account, optionally filtered by email address or Slack user ID.
Action
Update incidentEdits an existing incident's name, summary, severity, status, call link, Slack channel name, custom fields, role assignments or timestamps. Only the values you provide are changed.
Trigger
Budget UpdatedTriggers when an ad account's Opteo budget is changed.
Trigger
New AlertTriggers when Opteo raises a new alert on any of your linked ad accounts.
Trigger
New Completed ImprovementTriggers when an improvement is completed on an ad account.
Trigger
New Linked AccountTriggers when a new ad account is linked in Opteo.
Action
Get BudgetReturns the monthly budget set in Opteo for an ad account.
Action
Get Customer Linking StateReturns which team members are connected to an ad account and the changelog email options.
Action
Get Performance GoalsReturns an ad account's performance goals: primary and secondary goal, goal cycle and target amount.
Action
Get Performance ModeReturns whether an ad account is in CPA or ROAS performance mode.
Action
List Account AlertsReturns alerts from the last 90 days for one ad account, newest first (up to 500).
Action
List Active ImprovementsReturns the improvements currently on an ad account's Active tab, sorted by priority.
Action
List AlertsReturns alerts from the last 90 days across all linked ad accounts, newest first (up to 500).
Action
List Completed ImprovementsReturns the improvements completed on an ad account, newest first.
Action
List CustomersReturns the ad accounts your Opteo API key can access, optionally including unlinked ones.
Action
List ReportsReturns all reports for your linked ad accounts, each with the path to its PDF.
Action
List UsersReturns the users in your Opteo team.
Action
Run AgentStarts an Opteo AI agent run on an ad account. It returns at once with a running status; Opteo posts the answer to your callback URL when it finishes.
Action
Run GAQL QueryRuns a Google Ads Query Language (GAQL) query against a Google Ads account and returns the rows.
Action
Update BudgetSets the monthly budget in Opteo for an ad account.
Action
Update Changelog EmailSets which connection email is used for changelog actions on an ad account.
Action
Update Connected Team MembersReplaces the set of team members connected to an ad account. An empty list disconnects everyone.
Action
Update Performance GoalsUpdates some or all of an ad account's performance goals. Only the fields you supply are changed.
Action
Update Performance ModeSwitches an ad account between CPA and ROAS performance mode.
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 incident.io
incident.io to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
incident.io to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
incident.io to MailchimpMailchimp marketing automation and email platform.
incident.io to StripeStripe is a payment processing platform for online businesses.
incident.io to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
incident.io to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Opteo
HubSpot to OpteoHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to OpteoGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to OpteoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to OpteoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to OpteoGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to OpteoMailchimp marketing automation and email platform.
Questions
incident.io and Opteo, answered
What can start an automation from incident.io?
Any of incident.io's 1 trigger in the catalog, including New Incident. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Opteo when something happens in incident.io?
Any of Opteo's 18 actions, including List Completed Improvements, Update Budget, Update Changelog Email and Update Connected Team Members. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Opteo to incident.io?
Yes. When something happens in Opteo, your agent can act in incident.io too. This page covers both directions: Opteo's triggers and incident.io's actions are listed here as well.
Do I have to build a connector for incident.io or Opteo?
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 incident.io and Opteo 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.