Integration
Connect Drupal and incident.io
When New Content fires in Drupal, your agent runs Find Users On-Call in incident.io, or New Incident in incident.io to Create Content in Drupal. 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 Drupal and incident.io 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 Drupal and incident.io can do together
From Drupal to incident.io
When New Content in Drupal
then Find Users On-Call in incident.io
From incident.io to Drupal
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 Drupal and incident.io
Triggers and actions 2 triggers · 13 actions
- New Content
Triggers when new content (a node) of the content type you specify is created.
- Create Content
Creates a new content item (node) of the content type you specify, with a title and optional body.
- New Incident
Triggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode.
- Add follow-up
Creates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels.
- Add incident update
Shares an update on an incident: a message, a move to a new status, a new severity, or any combination.
- Create Incident
Creates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields.
- Find Users On-Call
Finds 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.
- Get incident
Returns a single incident, including its status, severity, role assignments, timestamps and custom field values.
- Get Schedule
Returns a single on-call schedule, including its rotations, time zone and current shifts.
- List actions
Returns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date.
- List incidents
Returns incidents in your incident.io account, optionally filtered by status, severity, type, mode and created/updated dates.
- List schedules
Returns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift.
- List severities
Returns every incident severity configured for your incident.io organisation.
- List users
Returns the users in your incident.io account, optionally filtered by email address or Slack user ID.
- Update incident
Edits 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.
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 Drupal
Drupal to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Drupal to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Drupal to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Drupal to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Drupal to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Drupal to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into incident.io
Google Drive to incident.ioGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to incident.ioActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Drupal and incident.io, answered
What can start an automation from Drupal?
Any of Drupal's 1 trigger in the catalog, including New Content. Describe the moment in plain language and your agent picks the right one.
What can your agent do in incident.io when something happens in Drupal?
Any of incident.io's 12 actions, including Create Incident, Update incident, Add follow-up and Add incident update. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from incident.io to Drupal?
Yes. When something happens in incident.io, your agent can act in Drupal too. This page covers both directions: incident.io's triggers and Drupal's actions are listed here as well.
Do I have to build a connector for Drupal or incident.io?
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 Drupal and incident.io 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.