--- title: "Connect Commune and incident.io - APIANT.ai" description: "When \"New Attendee\" fires in Commune, your agent runs \"Find Users On-Call\" in incident.io." canonical: "https://apiant.ai/connect/commune-to-incident-io" --- # Connect Commune and incident.io When **New Attendee** fires in [Commune](https://apiant.ai/connections/commune), your agent runs **Find Users On-Call** in [incident.io](https://apiant.ai/connections/incident-io), or **New Incident** in incident.io to **Send Direct Message** in Commune. Describe the whole flow and it is built, tested on every scenario and kept running. Commune **9** triggers Commune **9** actions incident.io **1** trigger incident.io **10** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Commune and incident.io to do together? 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 (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Commune and incident.io can do together ### From Commune to incident.io - When **New Attendee** in Commune then **Find Users On-Call** in incident.io - When **New Comment** in Commune then **Add follow-up** in incident.io ### From incident.io to Commune - When **New Incident** in incident.io then **Send Direct Message** in Commune - When **New Incident** in incident.io then **Create Post** in Commune 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 Commune and incident.io ## Triggers and actions 10 triggers · 19 actions - Trigger **Comment Edited** Triggers when a comment is edited after it was posted. - Trigger **Comment Moderated** Triggers when a comment is moderated to "Show to Poster/Admin only" visibility in your Commune community. - Trigger **New Attendee** Triggers when a new attendee registers for the selected Commune event. - Trigger **New Comment** Triggers when a new comment is posted in your Commune community, optionally limited to one post, commenter, box or category. - Trigger **New Event Created** Triggers when a new event is created in your Commune community. - Trigger **New Post** Triggers when a new post is created in your Commune community. - Trigger **New User** Triggers when a new user joins your Commune community. - Trigger **User Account Deactivation** Triggers when a community member's account is deactivated (the user resigns or is removed). - Trigger **User Added to Group** Triggers when a user is added to the selected Commune group. - Action **Create Group** Creates a new group in your Commmune community. - Action **Create Post** Creates a new post in a Commune box and category, authored as the chosen user. - Action **Deactivate User’s Account** Deactivates (removes) one or more user accounts from your Commune community. - Action **Find User** Finds community users by email address, optionally narrowed by creation date, resigned status or admin role. Returns the matching users and the first match. - Action **Generate Invitation Link** Creates member invitation links for one or more email addresses in your Commune community. - Action **Give Badge** Gives a badge to a community member. Only badges in the "Specific users" category can be given. - Action **Give Points** Adds points to one or more community members. By default the points count toward both their total earned and available points. - Action **Remove User From Group** Removes one or more users from a group. Any badge tied to that group is removed from those users too. - Action **Send Direct Message** Sends a direct message from the community admin to a user. - Trigger **New Incident** Triggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode. - Action **Add follow-up** Creates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels. - Action **Add incident update** Shares an update on an incident: a message, a move to a new status, a new severity, or any combination. - Action **Create Incident** Creates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields. - Action **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. - Action **Get incident** Returns a single incident, including its status, severity, role assignments, timestamps and custom field values. - Action **Get Schedule** Returns a single on-call schedule, including its rotations, time zone and current shifts. - Action **List actions** Returns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date. - Action **List schedules** Returns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift. - Action **List severities** Returns every incident severity configured for your incident.io organisation. - Action **List users** Returns the users in your incident.io account, optionally filtered by email address or Slack user ID. ## Each app on its own - [ **Commune** Commune is the no-code customer success platform that boosts customer engagement and reduces time and...](https://apiant.ai/connections/commune) - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) Reviews ## What our customers say ## More from Commune - [ **Commune to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/commune-to-hubspot) - [ **Commune to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/commune-to-salesforce) - [ **Commune to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/commune-to-slack) - [ **Commune to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/commune-to-google-sheets) - [ **Commune to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/commune-to-gmail) - [ **Commune to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/commune-to-google-calendar) ## More into incident.io - [ **HubSpot to incident.io** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-incident-io) - [ **Google Sheets to incident.io** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-incident-io) - [ **Gmail to incident.io** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-incident-io) - [ **Google Calendar to incident.io** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-incident-io) - [ **Google Drive to incident.io** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-incident-io) - [ **ActiveCampaign to incident.io** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-incident-io) Questions ## Commune and incident.io, answered ### ### What can start an automation from Commune? Any of Commune's 9 triggers in the catalog, including New Attendee, New Comment, New Event Created and New Post. 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 Commune? Any of incident.io's 10 actions, including Create Incident, Add follow-up, Add incident update and Find Users On-Call. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from incident.io to Commune? Yes. When something happens in incident.io, your agent can act in Commune too. This page covers both directions: incident.io's triggers and Commune's actions are listed here as well. ### ### Do I have to build a connector for Commune 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 Commune 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.