Integration
Connect Telegram to Dwolla
When New Update fires in Telegram, 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 Telegram 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 Telegram can start in Dwolla
When New Update in Telegram
then Add customer in Dwolla
When New Update in Telegram
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 Telegram and Dwolla
Triggers and actions 1 trigger · 33 actions
Trigger
New UpdateTriggers when Telegram delivers an update to your bot. Choose which kind of update to watch — a new message, a button press, a membership change, and so on. Telegram allows one webhook per bot, so use a single New Update trigger per bot token.
Action
Ban Chat MemberBan a user from a group, supergroup or channel.
Action
Delete MessageDelete a message from a chat.
Action
Forward MessageForward an existing message from one chat to another.
Action
Get ChatGet up-to-date information about a chat (user, group, or channel).
Action
Get Chat MemberLook up one person's membership in a chat — whether they are a member, an administrator, restricted, or have left or been banned.
Action
React to MessageSets an emoji reaction on an existing message.
Action
Send Chat ActionSend a chat action (e.g. typing, upload_photo) to indicate the bot is doing something.
Action
Send DocumentSend a general file/document to a chat.
Action
Send LocationSend a point on the map to a chat.
Action
Send MessageSends a message from your bot.
Action
Send PhotoSends a photo from your bot.
Action
Send PollSends a poll from your bot.
Action
Send VideoSend a video to a chat.
Action
Update MessageEdit the text of a previously sent message.
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 Telegram
Telegram to Aurora InboxAurora Inbox transforms your business WhatsApp into an intelligent sales hub.
Telegram to Base44Base44 is a platform that allows non-technical people to build their own Apps using AI.
Telegram to Brazil CNPJQuery Brazilian companies by CNPJ with full Receita Federal registry data, no key required
Telegram to GalileoGalileo is a tool that turns text into beautiful UI designs instantly with Galileo AI—fast, smart, and ready...
Telegram to GoTranscriptGoTranscript specializes in providing top-tier transcription services, transcribing both audio and video...
Telegram to NewtonNewton is a symbolic and arithmetic mathematics engine exposed over HTTP.
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
Telegram and Dwolla, answered
What can start an automation from Telegram?
Any of Telegram's 1 trigger in the catalog, including New Update. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Dwolla when something happens in Telegram?
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 Telegram?
Dwolla has no triggers in the catalog today, so automations start in Telegram. 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 Telegram 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.