--- title: "Connect incident.io and Saasu - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Create Contact\" in Saasu, or \"New Contact\" in Saasu to \"Find Users On-Call\" in incident.io." canonical: "https://apiant.ai/connect/incident-io-to-saasu" --- # Connect incident.io and Saasu When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Create Contact** in [Saasu](https://apiant.ai/connections/saasu), or **New Contact** in Saasu to **Find Users On-Call** in incident.io. Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Saasu **1** trigger Saasu **21** 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 Saasu 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 and Saasu can do together ### From incident.io to Saasu - When **New Incident** in incident.io then **Create Contact** in Saasu - When **New Incident** in incident.io then **Create Item Invoice** in Saasu ### From Saasu to incident.io - When **New Contact** in Saasu then **Find Users On-Call** in incident.io - When **New Contact** in Saasu 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 Saasu ## Triggers and actions 2 triggers · 31 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. - Trigger **New Contact** Triggers when a new contact is added to your Saasu file. - Action **Add activity** Creates an activity (task, call, meeting, note) in your Saasu file, optionally attached to a contact or transaction. - Action **Add company** Creates a company record in Saasu. - Action **Add item** Creates an inventory or combo item in Saasu. - Action **Add journal** Creates a manual journal entry with debit and credit lines in a Saasu file. - Action **Create Contact** Creates a new contact (person) in your Saasu file and returns its id. - Action **Create Item Invoice** Creates an item-layout invoice, quote or order in Saasu with inventory item line items. - Action **Create Service Invoice** Creates a service-layout sale or purchase invoice in Saasu, with line items described by account and amount. - Action **Delete contact** Deletes a contact from your Saasu file. - Action **Delete invoice** Deletes a sale or purchase invoice from the Saasu file. - Action **Delete item** Deletes an inventory item from the Saasu file. - Action **Email invoice** Emails a Saasu invoice to the email address you specify. - Action **Find accounts** Returns the accounts in your Saasu chart of accounts, filtered by type, status, bank-account flag or header account. - Action **Find companies** Returns the companies in your Saasu file whose name matches, optionally limited to a last-modified date range. - Action **Find Contact** Finds Saasu contacts matching an email, name, company or other criteria and returns the matching contacts. - Action **Find items** Returns the inventory and combo items whose code or description matches the search text. - Action **Get contact** Returns a single Saasu contact by its ID. - Action **Get invoice** Returns a single Saasu invoice (sale or purchase) by its ID, including line items and totals. - Action **Get journal** Returns a single journal transaction, including its date, reference, summary and journal line items. - Action **Update contact** Updates an existing contact in Saasu, such as their name, email, phone numbers, addresses and customer/supplier flags. - Action **Update invoice** Updates an existing Saasu sale or purchase invoice, replacing its details and line items. - Action **Update item** Updates an existing inventory or combo item in Saasu, such as its code, description, prices, accounts and tax codes. ## 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) - [ **Saasu** Fast, simple online accounting for small business that includes cashflow, invoicing, inventory, payroll and...](https://apiant.ai/connections/saasu) 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 Saasu - [ **HubSpot to Saasu** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-saasu) - [ **Google Sheets to Saasu** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-saasu) - [ **Gmail to Saasu** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-saasu) - [ **Google Calendar to Saasu** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-saasu) - [ **Google Drive to Saasu** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-saasu) - [ **Mailchimp to Saasu** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-saasu) Questions ## incident.io and Saasu, 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 Saasu when something happens in incident.io? Any of Saasu's 21 actions, including Create Contact, Create Item Invoice, Create Service Invoice and Update contact. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Saasu to incident.io? Yes. When something happens in Saasu, your agent can act in incident.io too. This page covers both directions: Saasu's triggers and incident.io's actions are listed here as well. ### ### Do I have to build a connector for incident.io or Saasu? 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 Saasu 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.