Integration
Connect Mailparser to Telegram
When something happens in Mailparser, your agent does the next thing in Telegram. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Mailparser and Telegram to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Mailparser and Telegram
Triggers and actions 3 triggers · 14 actions
Trigger
New Email Parsed (One Request Per Email)Triggered instantly when Mailparser finishes parsing an inbound email, with all of that email's parsed data delivered in a single request. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per Email". Parsed fields bind as {{ trigger.body.* }}. Use the One Request Per Row trigger instead when you are parsing tabular data and want each row handled as its own run.
- New Email Parsed (One Request Per Row)
Triggered instantly for EACH parsed table row when Mailparser finishes parsing an inbound email — one run per row, for tabular data such as invoice line items or price lists. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per row". That row's fields bind as {{ trigger.body.* }}. Use the One Request Per Email trigger instead when you want the whole email's parsed data in a single run.
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.
- Ban Chat Member
Ban a user from a group, supergroup or channel. POST https://api.telegram.org/bot{token}/banChatMember (chat_id, user_id).
- Delete Message
Delete a message from a chat. POST https://api.telegram.org/bot{token}/deleteMessage (chat_id, message_id).
- Forward Message
Forward an existing message from one chat to another. POST https://api.telegram.org/bot{token}/forwardMessage (chat_id, from_chat_id, message_id).
- Get Chat
Get up-to-date information about a chat (user, group, or channel). GET/POST https://api.telegram.org/bot{token}/getChat (chat_id).
- Get Chat Member
Look up one person's membership in a chat — whether they are a member, an administrator, restricted, or have left or been banned.
- React to Message
Sets an emoji reaction on an existing message.
- Send Chat Action
Send a chat action (e.g. typing, upload_photo) to indicate the bot is doing something. POST https://api.telegram.org/bot{token}/sendChatAction (chat_id, action).
- Send Document
Send a general file/document to a chat. POST https://api.telegram.org/bot{token}/sendDocument (chat_id, document, caption).
- Send Location
Send a point on the map to a chat. POST https://api.telegram.org/bot{token}/sendLocation (chat_id, latitude, longitude).
- Send Message
Sends a message from your bot.
- Send Photo
Sends a photo from your bot.
- Send Poll
Sends a poll from your bot.
- Send Video
Send a video to a chat. POST https://api.telegram.org/bot{token}/sendVideo (chat_id, video, caption).
- Update Message
Edit the text of a previously sent message. POST https://api.telegram.org/bot{token}/editMessageText (chat_id, message_id, text).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.