--- title: "Connect BigMailer and incident.io - APIANT.ai" description: "When \"New Contact\" fires in BigMailer, your agent runs \"Find Users On-Call\" in incident.io." canonical: "https://apiant.ai/connect/bigmailer-to-incident-io" --- # Connect BigMailer and incident.io When **New Contact** fires in [BigMailer](https://apiant.ai/connections/bigmailer), your agent runs **Find Users On-Call** in [incident.io](https://apiant.ai/connections/incident-io), or **New Incident** in incident.io to **Add/Update Contact** in BigMailer. Describe the whole flow and it is built, tested on every scenario and kept running. BigMailer **1** trigger BigMailer **35** 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 BigMailer 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 BigMailer and incident.io can do together ### From BigMailer to incident.io - When **New Contact** in BigMailer then **Find Users On-Call** in incident.io - When **New Contact** in BigMailer then **Add follow-up** in incident.io ### From incident.io to BigMailer - When **New Incident** in incident.io then **Add/Update Contact** in BigMailer - When **New Incident** in incident.io then **Create a bulk campaign** in BigMailer 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 BigMailer and incident.io ## Triggers and actions 2 triggers · 45 actions - Trigger **New Contact** Triggered when a new contact is created in a BigMailer brand. - Action **Add/Update Contact** Creates a BigMailer contact, or updates the existing contact with that email address. Custom fields for the selected brand can be mapped alongside list membership and unsubscribe settings. - Action **Create a bulk campaign** Creates a bulk email campaign in a BigMailer brand — name, subject, sender, content, recipient lists, tracking and optional schedule. - Action **Create an RSS campaign** Creates an RSS-to-email campaign in a BigMailer brand: watches a feed URL and emails new items on the schedule you choose. - Action **Create a transactional campaign** Creates a transactional campaign in a BigMailer brand — the reusable email template and settings you later send one-off emails with. - Action **Create list** Creates a new contact list inside a BigMailer brand. - Action **Create segment** Creates a segment in a BigMailer brand: a saved set of conditions that picks out the contacts you want to target. - Action **Create template** Creates a reusable email or landing-page template in a BigMailer brand. - Action **Delete contact** Deletes a contact from a BigMailer brand, by contact ID or email address. - Action **Delete list** Deletes a contact list from a BigMailer brand. - Action **Delete segment** Deletes a segment from a BigMailer brand. - Action **Delete template** Deletes a template from a BigMailer brand. - Action **Get brand** Returns one BigMailer brand: its name, default sender, bounce settings, contact count and engagement stats. - Action **Get bulk campaign** Returns one bulk campaign from a BigMailer brand, including its content, recipients and send statistics. - Action **Get contact** Returns one BigMailer contact by ID or email address, including its custom field values. - Action **Get list** Returns one contact list from a BigMailer brand. - Action **Get RSS campaign** Returns one RSS campaign from a BigMailer brand, including its feed URL, schedule and content. - Action **Get segment** Returns one segment from a BigMailer brand, including the conditions that define it. - Action **Get template** Returns one template from a BigMailer brand, including its HTML. - Action **Get transactional campaign** Returns one transactional campaign from a BigMailer brand, including its content and send statistics. - Action **List brands** Lists the brands in your BigMailer account. - Action **List bulk campaigns** Lists the bulk campaigns in a BigMailer brand. - Action **List contacts** Lists the contacts in a BigMailer brand, optionally limited to one list. - Action **List lists** Lists the contact lists in a BigMailer brand. - Action **List RSS campaigns** Lists the RSS campaigns in a BigMailer brand. - Action **List segments** Lists the segments in a BigMailer brand. - Action **List senders** Lists the sending identities in a BigMailer brand. - Action **List templates** Lists the templates in a BigMailer brand. - Action **List transactional campaigns** Lists the transactional campaigns in a BigMailer brand. - Action **Update a bulk campaign** Updates an existing bulk campaign in a BigMailer brand. Only the fields you fill in are changed. - Action **Update an RSS campaign** Updates an existing RSS campaign in a BigMailer brand. Only the fields you fill in are changed. - Action **Update a transactional campaign** Updates an existing transactional campaign in a BigMailer brand. Only the fields you fill in are changed. - Action **Update brand** Updates an existing BigMailer brand — its name, default sender name and email, website URL, unsubscribe text, bounce thresholds, contact limit and logo. Only the fields you fill in are changed. - Action **Update list** Renames an existing contact list inside a BigMailer brand. - Action **Update segment** Updates an existing BigMailer segment — its name, match operator (all/any) and its list of conditions. Only the fields you fill in are changed. - Action **Update template** Updates an existing BigMailer template — its name, type, HTML content and account-wide sharing. Only the fields you fill in are changed. - 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 - [ **BigMailer** BigMailer is email marketing software for agencies and developers.](https://apiant.ai/connections/bigmailer) - [ **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 BigMailer - [ **BigMailer to MINDBODY** MINDBODY is a powerful business management software that combines your scheduling, task automation...](https://apiant.ai/connect/bigmailer-to-mindbody) - [ **BigMailer to BridgeDb** bridgedb webservices](https://apiant.ai/connect/bigmailer-to-bridgedb) - [ **BigMailer to Salesmap** SalesMap is a data-driven CRM for sales growth.](https://apiant.ai/connect/bigmailer-to-salesmap) - [ **BigMailer to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/bigmailer-to-hubspot) - [ **BigMailer to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/bigmailer-to-salesforce) - [ **BigMailer to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/bigmailer-to-slack) ## 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 ## BigMailer and incident.io, answered ### ### What can start an automation from BigMailer? Any of BigMailer's 1 trigger in the catalog, including New Contact. 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 BigMailer? 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 BigMailer? Yes. When something happens in incident.io, your agent can act in BigMailer too. This page covers both directions: incident.io's triggers and BigMailer's actions are listed here as well. ### ### Do I have to build a connector for BigMailer 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 BigMailer 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.