--- title: "Connect incident.io to Mx Technologies - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add user\" in Mx Technologies." canonical: "https://apiant.ai/connect/incident-io-to-mx-technologies" --- # Connect incident.io to Mx Technologies When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add user** in [Mx Technologies](https://apiant.ai/connections/mx-technologies). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Mx Technologies **35** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want incident.io and Mx Technologies 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 incident.io can start in Mx Technologies - When **New Incident** in incident.io then **Add user** in Mx Technologies - When **New Incident** in incident.io then **Add account** in Mx Technologies 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 Mx Technologies ## Triggers and actions 1 trigger · 45 actions - 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. - Action **Add account** Creates a manual account for an MX user. Manual accounts sit under the Manual Institution member and never aggregate data from a financial institution. - Action **Add budget** Creates a budget for a category on an MX user. - Action **Add category** Create a custom category for a user. - Action **Add goal** Create a goal for a user. - Action **Add member** Create a member (connection between a user and a financial institution) to start aggregation. - Action **Add transaction** Creates a manual transaction on a manual account belonging to an MX user. - Action **Add user** Creates a new MX user. The returned user guid is what other MX actions (such as Add member) use to identify the user. - Action **Aggregate member** Starts an aggregation for a member, pulling the latest account and transaction data from the connected institution. MX may skip the aggregation if the data was updated recently. - Action **Delete account** Delete a manually created account. - Action **Delete budget** Deletes a budget belonging to an MX user. - Action **Delete category** Delete a custom category. - Action **Delete goal** Delete a goal. - Action **Delete member** Delete a member connection. - Action **Delete user** Delete a user. - Action **Get account** Read an account's attributes. - Action **Get budget** Retrieves a specific budget for an MX user. - Action **Get institution** Read an institution's attributes. - Action **Get member** Read a member's attributes and connection status. - Action **Get merchant** Returns information about a particular merchant, such as its logo, name, and website. - Action **Get transaction** Read a transaction's attributes. - Action **Get user** Retrieves the attributes of a specific MX user. - Action **List accounts** Lists all accounts belonging to an MX user. Returns up to 1000 accounts in one call. - Action **List categories** Lists all categories for an MX user, including default and custom categories. - Action **List goals** Lists all goals for an MX user. - Action **List institutions** Lists financial institutions available through MX, optionally filtered by name, country and supported product. - Action **List members** List all members belonging to a user. - Action **List merchants** Lists merchants in the MX system, optionally filtered by a name substring. - Action **List transactions** List all transactions for a user. - Action **Update account** Updates an account belonging to a member. Manual accounts can have every field updated; aggregated accounts only accept changes to Is Business, Is Hidden and Metadata. - Action **Update budget** Update a specific budget. - Action **Update category** Update a custom category. - Action **Update goal** Updates an existing savings or payoff goal for an MX user. Only the fields you fill in are changed. - Action **Update member** Updates a member's credentials, id, metadata, background aggregation setting or use cases. At least one value to update must be supplied. - Action **Update transaction** Update a transaction's category, description, or other editable attributes. - Action **Update user** Update a user's attributes. ## Each app on its own - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) - [ **Mx Technologies** API for aggregating and enriching consumer bank account and transaction data for financial apps.](https://apiant.ai/connections/mx-technologies) Reviews ## What our customers say ## More from incident.io - [ **incident.io to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/incident-io-to-salesforce) - [ **incident.io to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/incident-io-to-slack) - [ **incident.io to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/incident-io-to-mailchimp) - [ **incident.io to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/incident-io-to-stripe) - [ **incident.io to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/incident-io-to-shopify) - [ **incident.io to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/incident-io-to-quickbooks-online) ## More into Mx Technologies - [ **HubSpot to Mx Technologies** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-mx-technologies) - [ **Salesforce to Mx Technologies** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-mx-technologies) - [ **Slack to Mx Technologies** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-mx-technologies) - [ **Google Sheets to Mx Technologies** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-mx-technologies) - [ **Gmail to Mx Technologies** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-mx-technologies) - [ **Google Calendar to Mx Technologies** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-mx-technologies) Questions ## incident.io and Mx Technologies, 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 Mx Technologies when something happens in incident.io? Any of Mx Technologies's 35 actions, including Update account, Update budget, Update category and Update goal. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Mx Technologies to incident.io? Mx Technologies has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Mx Technologies's API documentation and adds it. ### ### Do I have to build a connector for incident.io or Mx Technologies? 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 Mx Technologies 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.