How to Send WordPress Form Submissions to Telegram
Send WordPress form submissions to a Telegram group or chat with your own bot. A live setup, chat IDs, message templates, retries and error fixes.
A lead from your website form is only useful if someone replies while the person is still interested. Most WordPress forms send that lead to an email inbox, and on a small team the inbox gets checked when somebody remembers. If your team already talks in Telegram, WordPress form Telegram notifications put every new submission in the chat they’re reading anyway.
The setup needs 3 things:
- a bot you create in Telegram
- the chat ID of the group or person who should get the alert
- one action on your form
The submission still saves in WordPress, so Telegram is the alert and WordPress stays the record.
Core Forms has this built in as the Send to Telegram action. It runs after a successful submission, alongside other actions such as email, webhooks and Google Sheets. It posts through your own bot, so the messages come from an account you control.
Telegram Notifications on a Live Site
Before going into the settings, I want to show you a setup that is already running. Anantam IAS, a UPSC coaching site, uses Core Forms for its course enquiries. Three of its forms post to the same Telegram group, where the team picks up new leads.
The PSIR enquiry form on Anantam IAS. Every submission reaches the team’s Telegram group.
Here is what each form sends to Telegram and what else it does after a submission:
| Form | Telegram message | Other actions on the form |
|---|---|---|
| PSIR QEP and Mentorship Programme 2027 Enquiry | Default: form title and every field | 2 emails, a webhook |
| Book Demo Class | Default: form title and every field | 2 emails, a webhook |
| UPSC Preparation Assessment Request | [all:label]: every field with its label | 2 emails, an auto-responder, Google Sheets |
Three parts of this setup are worth copying:
- Telegram sits next to email. Every form also emails the team, so a missed Telegram message doesn’t cost the lead.
- The Telegram action runs in the background. The visitor sees the confirmation right away, and a slow reply from Telegram never holds up the form.
- One bot and one group serve all 3 forms. Two forms use the default message, which starts with the form title and tells the team where the lead came from.
The PSIR enquiry form runs Send to Telegram after 2 emails and a webhook.
Create a Telegram Bot
Core Forms sends messages through a bot that belongs to you. If you already run a bot for something else, create a separate one for form alerts. A bot that hands its updates to another app through a webhook can’t use Find chats, which you’ll want in the next step.
- Open @BotFather in Telegram and send
/newbot. - Pick a display name and a username that ends in
bot. - Copy the token BotFather gives you and save it in a password manager.
- In WordPress, open your form, go to Actions and add Send to Telegram.
- Paste the token into Bot token and click Verify bot.
When the token is right, Core Forms shows “Connected to @yourbot. No message was sent.” Verification has limits:
- It confirms that Telegram accepts the token and that the token belongs to a bot.
- It doesn’t send a message, so it can’t tell you whether the bot is allowed to post in your group.
- A token in the wrong shape fails before any request goes out. Core Forms expects the full
123456789:AAH...format from BotFather.
The token works like a password for your bot. Anyone who has it can post as the bot, so keep it out of screenshots, page HTML and front-end code. If it leaks, send /revoke to BotFather and paste the new token into the action.
The Telegram action on the PSIR form. The token stays masked and the chat ID is a placeholder.
Find Your Telegram Chat ID
The chat ID tells the bot where to post. A bot can only post in a chat it has been let into, so give it access first and look up the ID after that.
| Destination | What to do first | What goes in Chat ID |
|---|---|---|
| Your own chat | Open the bot and press Start | Your numeric user ID |
| Group | Add the bot, then send /start@YourBot in the group | The group’s ID, a negative number |
| Private channel | Add the bot as an admin who can post | The channel’s ID, starting with -100 |
| Public channel | Add the bot as an admin who can post | @channelname or the numeric ID |
| Forum topic | Add the bot, then send /start@YourBot inside the topic | The group’s ID, plus the topic’s ID in Topic ID |
Then click Find chats. Core Forms reads the bot’s recent updates and lists the chats, groups, channels and topics the bot has seen, so you pick one instead of copying numbers by hand. These details catch people out:
- Your personal @username is not a chat ID. Only a public channel works with an @name.
- Group and channel IDs are negative. Keep the minus sign, and keep the
-100prefix on supergroups and channels. - Find chats reads updates without marking them as read, so it doesn’t take messages away from anything else that uses the bot.
- Find chats won’t run on a bot with an active webhook. Core Forms leaves the webhook alone and asks you to type the chat ID or use a separate bot.
One Telegram behavior is worth knowing in advance. Telegram sometimes upgrades a group to a supergroup, usually as the group grows or when an admin turns on certain features. The upgraded group gets a new ID, and the old one stops working. Core Forms follows Telegram’s pointer to the new ID once, delivers the message and saves the new ID into the action.
Write the Telegram Message
The Message field decides what lands in Telegram. You have three ways to fill it, and Anantam IAS happens to use two of them.
Leave the Message Empty
An empty Message field sends the form title in bold, then every submitted field on its own line. Core Forms builds each label from the field name, so target_year becomes “Target year”. For the PSIR form, a message looks like this (example values):
PSIR QEP and Mentorship Programme 2027 Enquiry
Name: Riya Sharma
Email: riya@example.com
Mobile: +1 202 555 0100
Target year: 2027
Programme: PSIR QEP
This is the right default when several forms share a group, because the first line names the form.
Use the [all:label] Variable
[all:label] sends every non-empty field with the label the visitor saw on the form. The assessment form on Anantam IAS uses it:

And this is what the team gets in Telegram:
A lead from the assessment form in the team’s Telegram group. The name, phone number and free-text answer are blurred.
The message is easy to read, and it also shows three things to plan for:
- It has no form title.
[all:label]starts with the first field. In a group shared by 3 forms, the team has to guess the source from the fields. - Choice fields send their stored value. “working_student” and “2029_later” are the values saved behind the options the visitor clicked. Readable option values fix this.
- Hidden fields come along. The consent fields “Assessment Permission” and “Permission Version” matter in WordPress and add noise in a chat.
Write a Short Template
A custom template gives you the most control. Click Insert field to add a field, or type its name in square brackets. Core Forms also has system variables such as [CF_FORM_TITLE], [CF_SUBMISSION_ID] and [CF_REFERRER_URL]:
<b>[CF_FORM_TITLE]</b>
Name: [name]
Mobile: [mobile]
Target year: [target_year]
Page: [CF_REFERRER_URL]
Entry #[CF_SUBMISSION_ID]
This is the template I’d use for a shared group. It names the form, gives the person replying what they need for the first call and leaves everything else in WordPress. The full list is in the data variables documentation.
The Message format setting changes how Telegram reads your template:
- HTML formatting keeps Telegram’s tags such as
<b>,<i>and<code>from your template. - Plain text sends exactly what you write.
- Submitted values are escaped in both modes, so a visitor can’t slip formatting into the message.
- Telegram allows 4,096 characters after formatting. Core Forms checks the length before sending and fails the action with a clear message if the text runs over.
A word on privacy. The blurred line in the screenshot above is a free-text answer, and people type personal things into free-text boxes. Everyone in the group reads every message, so it is wise to send only the fields needed for the first reply and keep the full entry in WordPress.
Send a Test Message
Every Telegram action has a Test Telegram message panel. It sends a real message to the chat you picked, using sample values written as JSON.
The test panel on the PSIR form, with Run in the background turned on.
- Click Use form field samples to fill the JSON from your form’s fields, or edit the values yourself.
- Click Send test message and check that it lands in the right chat or topic.
- Save the form. The test uses the settings on screen, but they only stick after you save.
- Submit the live form once with made-up details and compare the saved entry with the Telegram message.
- Delete the test entry and the test messages.
The two tests check different things. The test panel checks the bot, the chat and your template. The live submission checks your field names, any conditions on the action and the background queue.
Retries and Failed Messages
Run in the background should be on for Telegram. Core Forms saves the submission, shows the visitor the confirmation and then sends the message from a queue, so a slow Telegram response never reaches the visitor. Background mode needs submission storage, because retries read the saved entry. Without storage, the action runs immediately instead.
The queue retries only the failures that can clear up on their own:
- Retried: Telegram rate limits (429), Telegram server errors (5xx), timeouts and network failures. Core Forms tries again up to 3 times, about 2, 4 and 8 minutes apart, or later when Telegram asks it to wait longer.
- Not retried: a bad token, a missing chat, a bot without permission or broken HTML. The same request would fail the same way every time.
Failed background actions land in Core Forms > Delivery recovery with the last recorded message. On Anantam IAS, two Book Demo Class alerts are sitting there:
Two Telegram alerts that Telegram rejected with HTTP 400. Both entries are still saved in WordPress.
The “1 attempt” is the part to notice. A 400 means Telegram refused the request itself, so Core Forms stopped instead of repeating something that can’t work. Both entries are still saved, and the form’s email actions run separately from Telegram. After you fix the cause, Retry background action sends the same message again. The retries and logs documentation covers the queue in more detail.
Fix Common Telegram Errors
Start with the message Core Forms shows. Changing every setting at once makes the real cause harder to find. If Delivery recovery shows only an HTTP code, send a test message from the action to see the specific reason.
| What you see | What it means | Fix |
|---|---|---|
| “Enter the complete bot token from @BotFather.” | The token isn’t in Telegram’s format | Copy the whole token again, including the numbers before the colon |
| “Telegram rejected the bot token” (401) | The token was revoked or mistyped | Paste the current token from BotFather |
| “The bot cannot post here” (403) | The bot is blocked or lacks permission | Press Start in a private chat, unblock the bot or let it post in the group or channel |
| “Chat not found” (400) | Wrong ID, or the bot isn’t in that chat | Add the bot, then run Find chats again |
| “Telegram could not read the HTML formatting” (400) | A tag in your template is broken or unsupported | Fix the tag or switch to Plain text |
| “Telegram could not find this topic” (400) | The Topic ID doesn’t belong to that group | Check the Topic ID or leave it empty |
| “This group has moved to a supergroup” (400) | The group has a new ID | Run Find chats and pick the new ID |
| “Another service is receiving this bot’s updates” (409) | A webhook owns the bot’s updates | Type the chat ID by hand or use a separate bot |
| “Telegram is rate limiting this bot” (429) | Too many messages in a short time | Wait; the background queue retries after Telegram’s delay |
| “Use between 1 and 4,096 characters” | The message is empty or too long | Send fewer fields |
The Telegram integration documentation lists every control in the action. If your team works in Slack instead, the Slack form inbox guide sets up the same pattern there.
FAQs on WordPress Form Telegram Notifications
Does this create a form inside Telegram?
No. The visitor fills out the form on your WordPress site, and Telegram receives the notification. A bot that asks questions inside the chat is a different kind of bot.
Can a Telegram bot message someone who hasn’t started it?
No. As Telegram’s bot documentation explains, a bot can’t start a private conversation. The person has to open the bot and press Start once, and after that the bot can message them.
Can several forms post to the same Telegram group?
Yes. Use the same bot token and chat ID in each form’s action. If you write custom templates, start each one with [CF_FORM_TITLE] so the team can tell the forms apart.
What happens to the submission if the Telegram message fails?
The entry stays in WordPress as long as submission storage is on. The form’s other actions run separately, and a failed background message waits in Delivery recovery until you retry it.