--- title: "Connect incident.io to Resend - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add Contact to Segment\" in Resend." canonical: "https://apiant.ai/connect/incident-io-to-resend" --- # Connect incident.io to Resend When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add Contact to Segment** in [Resend](https://apiant.ai/connections/resend). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Resend **28** 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 Resend 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 Resend - When **New Incident** in incident.io then **Add Contact to Segment** in Resend - When **New Incident** in incident.io then **Create Contact** in Resend 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 Resend ## Triggers and actions 1 trigger · 38 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 Contact to Segment** Adds a contact to a Resend segment. You can identify the contact by its ID or email address. - Action **Add Suppression** Adds an email address to your Resend suppression list so no further mail is sent to it. - Action **Cancel Email** Cancels a scheduled Resend email that has not been sent yet. - Action **Create API Key** Creates a new Resend API key. The key itself is returned once, so store it right away. - Action **Create Contact** Creates a contact in Resend. Returns the new contact's ID. - Action **Create Domain** Adds a sending domain to Resend. Returns the DNS records you need to add at your domain host to verify it. - Action **Create Segment** Creates a new segment in Resend for grouping contacts. - Action **Delete API Key** Deletes a Resend API key so it can no longer be used. - Action **Delete Contact** Deletes a contact from Resend. You can identify the contact by its ID or email address. - Action **Delete Domain** Removes a sending domain from Resend. - Action **Delete Segment** Deletes a segment from Resend. The contacts themselves are not deleted. - Action **List API Keys** Returns the API keys on your Resend account, with each key's name and when it was last used. The key values themselves are never returned. - Action **List Contacts** Returns the contacts in your Resend account, optionally limited to one segment. - Action **List Domains** Returns the sending domains on your Resend account and each one's verification status. - Action **List Segments** Returns the contact segments in your Resend account. - Action **List Sent Emails** Returns the emails you have sent through Resend, newest first, with each email's id, sender, recipients, subject, send time and latest delivery event. Supports paging before or after a given email id. - Action **List Suppressions** Returns the email addresses on your Resend suppression list, showing for each one the address, why it was suppressed (bounce, complaint or added manually), the email that triggered it and when it was added. - Action **Remove Contact From Segment** Removes a contact from one of your Resend segments. Identify the contact by its ID or by its email address, and name the segment to take it out of. The contact itself is not deleted. - Action **Remove Suppression** Takes an email address off your Resend suppression list so you can send to it again. Identify it by the suppression ID or by the email address itself. - Action **Retrieve Contact** Returns one contact from your Resend audience, including their name, email address, whether they have unsubscribed, when they were added, and any custom properties stored on them. Look the contact up by its ID or by its email address. - Action **Retrieve Domain** Returns one of your Resend sending domains, including its name, verification status, sending region, tracking settings and the DNS records it needs with each record's current status. - Action **Retrieve Segment** Returns one of your Resend segments by its ID, with the segment's name and when it was created. - Action **Retrieve Sent Email** Returns one email you sent through Resend, with its sender, recipients, subject, HTML and text body, tags, send time and latest delivery event. - Action **Send Batch Emails** Sends up to 100 emails through Resend in a single call. Give it a list of emails, each with a sender, recipients, subject and body, and it returns the id of every email it created. - Action **Send Email** Sends an email through Resend. Set the sender, recipients and subject, provide an HTML or plain text body, and optionally add CC/BCC, reply-to, attachments, tags or a send time. - Action **Update Contact** Updates a contact in your Resend audience. Identify the contact by ID or email address, then change the name, the subscribed/unsubscribed state, or the custom properties. Anything you leave blank stays as it is. - Action **Update Email** Reschedules an email you already queued in Resend, moving it to a new send date and time. Only emails that have not gone out yet can be changed. - Action **Verify Domain** Asks Resend to re-check the DNS records for one of your sending domains and start verifying it. Verification runs in the background, so the domain shows as pending until it finishes. ## 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) - [ **Resend** Resend is the email API for developers. It's designed for you to build, test, and send transactional and...](https://apiant.ai/connections/resend) 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 Resend - [ **Documenso to Resend** Documenso is an open-source digital signing platform.](https://apiant.ai/connect/documenso-to-resend) - [ **Google BigQuery to Resend** BigQuery is Google's serverless and highly scalable enterprise data warehouse, designed to make all your...](https://apiant.ai/connect/google-bigquery-to-resend) - [ **HubSpot to Resend** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-resend) - [ **Salesforce to Resend** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-resend) - [ **Slack to Resend** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-resend) - [ **Google Sheets to Resend** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-resend) Questions ## incident.io and Resend, 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 Resend when something happens in incident.io? Any of Resend's 28 actions, including Create API Key, Create Contact, Create Domain and Create Segment. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Resend to incident.io? Resend has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Resend's API documentation and adds it. ### ### Do I have to build a connector for incident.io or Resend? 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 Resend 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.