Integration
Connect BaseLinker to Dwolla
When New Order fires in BaseLinker, 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 BaseLinker and Dwolla to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 BaseLinker can start in Dwolla
When New Order in BaseLinker
then Add customer in Dwolla
When New Order in BaseLinker
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 BaseLinker and Dwolla
Triggers and actions 1 trigger · 43 actions
Trigger
New OrderTriggers when a new confirmed order appears in the BaseLinker order manager.
Action
Add a Tracking NumberAdds a tracking number from a courier shipment created outside BaseLinker to an order.
Action
Add CRM clientCreates a new CRM client in BaseLinker, or updates an existing one when a CRM client ID is given. Returns the client's ID.
Action
Add InvoiceIssues an invoice for an order in the BaseLinker order manager.
Action
Add OrderCreates a new order in the Base (BaseLinker) order manager with buyer, delivery, billing and product details, and returns the new order's ID.
Action
Add order productAdds a product line item to an existing BaseLinker order and returns the new item's id.
Action
Add order returnCreates a new order return in the BaseLinker return manager, optionally linked to an existing order, and returns its ID.
Action
Add PaymentRecords a payment on a BaseLinker order, setting the order's paid amount, date and comment.
Action
Add productCreates a new product in a BaseLinker (Base) inventory catalog and returns its product ID.
Action
Delete orderDeletes an order from the BaseLinker order manager.
Action
Delete productDeletes a product from a BaseLinker product catalog.
Action
Find ordersFinds orders in the Base order manager matching the filters you give (order ID, buyer email, status, source, dates). Returns up to 100 orders.
Action
Get CRM clientsReturns CRM clients from BaseLinker, optionally filtered by client ID, email, phone, login, invoice company, tax ID, full name or status. Returns up to 100 clients.
Action
Get Order FieldsReturns the custom extra fields defined for orders in BaseLinker, with each field's ID, name, editor type and allowed options.
Action
Get Order PackageReturns the courier shipments (packages) created for a BaseLinker order, with tracking numbers, courier and tracking status.
Action
Get Order ReturnsReturns order returns from the BaseLinker return manager, optionally narrowed by order, return, date, status or source (up to 100 at a time).
Action
Get productReturns the full details of one product from a BaseLinker catalog, including prices, stock, text fields, images and variants.
Action
List inventoriesReturns the product catalogs (inventories) in your BaseLinker account, with their languages, price groups and warehouses.
Action
List order statusesReturns the order statuses created in the BaseLinker order manager, with their names, colors and groups.
Action
List productsReturns the basic data (ID, SKU, EAN, name, prices and stock) of products in a BaseLinker catalog, optionally filtered by category, tag, SKU, EAN, name, price or stock.
Action
Update OrderUpdates selected fields of an existing BaseLinker order, such as addresses, comments, delivery details and extra fields. Fields left blank are not changed.
Action
Update Order StatusChanges the status of a BaseLinker order to the status you choose.
Action
Update productUpdates an existing product in a BaseLinker catalog. Only the fields you fill in are changed.
Action
Update product pricesUpdates the gross prices of up to 1000 products or variants in a BaseLinker catalog, per price group.
Action
Update product stockUpdates the stock levels of products or variants in a BaseLinker catalog, per warehouse.
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 BaseLinker
BaseLinker to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
BaseLinker to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
BaseLinker to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
BaseLinker to Google SheetsGoogle Sheets
BaseLinker to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
BaseLinker to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
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
BaseLinker and Dwolla, answered
What can start an automation from BaseLinker?
Any of BaseLinker's 1 trigger in the catalog, including New Order. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Dwolla when something happens in BaseLinker?
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 BaseLinker?
Dwolla has no triggers in the catalog today, so automations start in BaseLinker. 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 BaseLinker 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.
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.