Integration
Connect Chaport to Dwolla
When Chat Stage Updated (instant) fires in Chaport, your agent runs Add customer in Dwolla. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Chaport and Dwolla to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Chaport can start in Dwolla
When Chat Stage Updated (instant) in Chaport
then Add customer in Dwolla
When New Chat Started in Chaport
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 Chaport and Dwolla
Triggers and actions 8 triggers · 31 actions
Trigger
Chat Closed (instant)Fires when a chat is closed. Webhook event: chat.closed.
Trigger
Chat FinishedTriggers when chat is finished.
Trigger
Chat Stage Updated (instant)Fires when a chat's stage changes. Webhook event: chat.stageUpdated.
Trigger
Message Read (instant)Fires when a message is read. Webhook event: message.read.
Trigger
New Chat StartedTriggers when chat is started.
Trigger
New Message Sent (instant)Fires when a new message is sent in a chat. Webhook event: message.sent.
Trigger
New Visitor (instant)Fires when a new visitor is created. Webhook event: visitor.created.
Trigger
Visitor UpdatedTriggers when visitor data is updated.
Action
Create an OperatorAdds a new operator to your Chaport account and returns the created operator.
Action
Delete a MessageDeletes one message from a Chaport chat. Identify the visitor and the message you want removed.
Action
Delete an OperatorRemoves an operator from your Chaport account.
Action
List OperatorsReturns every operator in your Chaport account, with each operator's name, email, role and status.
Action
List VisitorsReturns the visitors in your Chaport account, one page at a time.
Action
Retrieve an OperatorReturns one Chaport operator with their name, email, role, job title and current status.
Action
Retrieve a VisitorReturns one Chaport visitor with their name, contact details, notes and any custom data held about them.
Action
Retrieve Last Visitor ChatReturns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.
Action
Send a MessagePosts a message into a Chaport visitor's chat, starting a chat if there isn't one open.
Action
Update an OperatorUpdates a Chaport operator's details. Anything you leave blank keeps its current value.
Action
Update a VisitorUpdates an existing Chaport visitor's contact details, notes and custom data. Only the fields you fill in are changed; blank fields are left untouched.
Action
Update Operator StatusSets a Chaport operator's availability status, such as online or offline, optionally for a limited time.
Action
Add beneficial ownerAdds 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 customerCreates a Dwolla customer — receive-only, unverified, verified personal, or verified business.
Action
Add documentUploads an identity verification document (passport, license, ID card) for a Dwolla customer.
Action
Add funding sourceCreates a bank account, virtual account number or debit card funding source for a Dwolla customer.
Action
Add mass paymentCreates a mass payment that sends up to 5,000 individual payments from one Dwolla funding source in a single batch.
Action
Add transferInitiates a Dwolla transfer of money from one funding source to another, returning the new transfer's id and link.
Action
Cancel transferCancels a pending Dwolla transfer and returns the updated transfer.
Action
Delete funding sourceRemoves a bank or debit card funding source in Dwolla. The funding source is soft deleted and stays readable, marked as removed.
Action
Find customersSearches Dwolla customers by name, business name or email, optionally filtered by verification status.
Action
Get customerReturns a Dwolla customer's details, including name, email, type and verification status.
Action
Get funding sourceReturns a Dwolla funding source (bank account or balance) by its ID, including its type, status and bank details.
Action
Get funding source balanceReturns 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 paymentReturns a Dwolla mass payment by its ID, including its processing status (pending, processing or complete), creation date, totals and metadata.
Action
List beneficial ownersReturns all beneficial owners associated with a business verified Dwolla customer.
Action
List documentsReturns all identity verification documents submitted for a Dwolla customer, including their type, review status and verification result.
Action
List eventsReturns the recent events (state changes to customers, transfers, funding sources and more) in your Dwolla application, newest first.
Action
List funding sourcesReturns all funding sources for a Dwolla customer, including bank accounts, debit cards and the Dwolla balance, with their verification status.
Action
List transfersReturns the transfers for a Dwolla customer, optionally filtered by amount range, date range, status, correlation ID or a name/email search.
Action
Update customerUpdates a Dwolla customer's information, upgrades or retries verification, or suspends, deactivates or reactivates the customer.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Chaport
Chaport to StripeStripe is a payment processing platform for online businesses.
Chaport to ChatraceOmnichannel chatbot platform for automating customer support and sales via WhatsApp, SMS, Messenger...
Chaport to keycdn IP Location FinderGet the IP geolocation data through the simple REST API. All the responses are JSON encoded
Chaport to ProxiedMailProxiedMail provides creating email addresses, forwarding and receiving emails with full context.
Chaport to PublicaWith Publica, you can sell, share and consume all kinds of digital content directly through a reliable and...
Chaport to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
More into Dwolla
HubSpot to DwollaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to DwollaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to DwollaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to DwollaGoogle Sheets
Gmail to DwollaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to DwollaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Chaport and Dwolla, answered
What can start an automation from Chaport?
Any of Chaport's 8 triggers in the catalog, including Chat Stage Updated (instant), New Chat Started, New Message Sent (instant) and New Visitor (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Dwolla when something happens in Chaport?
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 Chaport?
Dwolla has no triggers in the catalog today, so automations start in Chaport. 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 Chaport 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 Chaport 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.