Integration
Connect incident.io and Tadabase
When New Incident fires in incident.io, your agent runs Find Record in Tadabase, or New Record in Tadabase 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 Tadabase 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)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 Tadabase can do together
From incident.io to Tadabase
When New Incident in incident.io
then Find Record in Tadabase
When New Incident in incident.io
then Get record in Tadabase
From Tadabase to incident.io
When New Record in Tadabase
then Find Users On-Call in incident.io
When Updated Record in Tadabase
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 Tadabase
Triggers and actions 3 triggers · 15 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 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.
Trigger
New RecordTriggers when a new record is added to the chosen Tadabase table.
Trigger
Updated RecordTriggers when a record in the selected Tadabase table is created or changed.
Action
Delete recordDeletes a record from a Tadabase data table.
Action
Find RecordFinds records in a Tadabase table where a field matches a value, returning up to 100 matches.
Action
Get recordReturns a single record from a Tadabase table by its record ID, including all of its field values.
Action
List recordsReturns the records stored in a Tadabase data table, with all of their field values.
Action
List tablesReturns every table in your Tadabase app with its ID and name.
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 Tadabase
HubSpot to TadabaseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TadabaseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TadabaseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TadabaseGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TadabaseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TadabaseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
incident.io and Tadabase, 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 Tadabase when something happens in incident.io?
Any of Tadabase's 5 actions, including Find Record, Get record, List records and List tables. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Tadabase to incident.io?
Yes. When something happens in Tadabase, your agent can act in incident.io too. This page covers both directions: Tadabase's triggers and incident.io's actions are listed here as well.
Do I have to build a connector for incident.io or Tadabase?
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 Tadabase 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.