--- title: "Connect incident.io to Dwolla - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add customer\" in Dwolla." canonical: "https://apiant.ai/connect/incident-io-to-dwolla" --- # Connect incident.io to Dwolla When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add customer** in [Dwolla](https://apiant.ai/connections/dwolla). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Dwolla **19** 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 Dwolla 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 Dwolla - When **New Incident** in incident.io then **Add customer** in Dwolla - When **New Incident** in incident.io then **Update customer** in Dwolla 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 Dwolla ## Triggers and actions 1 trigger · 29 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 beneficial owner** Adds a beneficial owner (an individual owning 25% or more) to a verified business customer, identified by SSN for US owners or by passport for non-US owners. - Action **Add customer** Creates a Dwolla customer — receive-only, unverified, verified personal, or verified business. - Action **Add document** Uploads an identity verification document (passport, license, ID card) for a Dwolla customer. - Action **Add funding source** Creates a bank account, virtual account number or debit card funding source for a Dwolla customer. - Action **Add mass payment** Creates a mass payment that sends up to 5,000 individual payments from one Dwolla funding source in a single batch. - Action **Add transfer** Initiates a Dwolla transfer of money from one funding source to another, returning the new transfer's id and link. - Action **Cancel transfer** Cancels a pending Dwolla transfer and returns the updated transfer. - Action **Delete funding source** Removes a bank or debit card funding source in Dwolla. The funding source is soft deleted and stays readable, marked as removed. - Action **Find customers** Searches Dwolla customers by name, business name or email, optionally filtered by verification status. - Action **Get customer** Returns a Dwolla customer's details, including name, email, type and verification status. - Action **Get funding source** Returns a Dwolla funding source (bank account or balance) by its ID, including its type, status and bank details. - Action **Get funding source balance** Returns the current balance of a Dwolla funding source — balance and total for a Dwolla balance, available and closing for a bank account, available for a settlement account. - Action **Get mass payment** Returns a Dwolla mass payment by its ID, including its processing status (pending, processing or complete), creation date, totals and metadata. - Action **List beneficial owners** Returns all beneficial owners associated with a business verified Dwolla customer. - Action **List documents** Returns all identity verification documents submitted for a Dwolla customer, including their type, review status and verification result. - Action **List events** Returns the recent events (state changes to customers, transfers, funding sources and more) in your Dwolla application, newest first. - Action **List funding sources** Returns all funding sources for a Dwolla customer, including bank accounts, debit cards and the Dwolla balance, with their verification status. - Action **List transfers** Returns the transfers for a Dwolla customer, optionally filtered by amount range, date range, status, correlation ID or a name/email search. - Action **Update customer** Updates a Dwolla customer's information, upgrades or retries verification, or suspends, deactivates or reactivates the customer. ## 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) - [ **Dwolla** Say goodbye to plastic cards, ATM fees, hidden charges and fine print.](https://apiant.ai/connections/dwolla) 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 Dwolla - [ **HubSpot to Dwolla** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-dwolla) - [ **Salesforce to Dwolla** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-dwolla) - [ **Slack to Dwolla** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-dwolla) - [ **Google Sheets to Dwolla** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-dwolla) - [ **Gmail to Dwolla** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-dwolla) - [ **Google Calendar to Dwolla** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-dwolla) Questions ## incident.io and Dwolla, 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 Dwolla when something happens in incident.io? Any of Dwolla's 19 actions, including Update customer, Add beneficial owner, Add customer and Add document. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Dwolla to incident.io? Dwolla has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Dwolla's API documentation and adds it. ### ### Do I have to build a connector for incident.io or Dwolla? 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 Dwolla 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.