Telegram work email finder

What it is

This n8n workflow finds a person’s work email through a Telegram bot. You message the bot a first name, a last name and a company domain. One Code node splits the message, a second builds likely address shapes from the name, and the first four go to Anymail Finder to be checked one by one. Whatever verifies comes back to the chat, and a short note comes back when nothing does.

Who it suits

Sales reps, recruiters and outreach specialists who already have a name and a company and need the address, and who would rather ask a chat than open another tool.

You need some n8n, a Telegram bot and an Anymail Finder account with credit. It tests guessed address shapes, so a company with an unusual format can return nothing. Its author puts setup at about 8 minutes, which assumes the accounts already exist.

Where to use it

Any n8n that Telegram can reach over HTTPS will do, whether it runs on n8n Cloud or on your own server, since the trigger works through a webhook that Telegram calls.

• n8n Cloud: import the file into a new workflow there
• Your own n8n server: the same file, on a public HTTPS address
• Telegram: any chat with your bot, on a phone or a desktop
• Another chat tool: replace the Telegram nodes with the ones for Slack

Setup

Get it saves a zip with workflow.json and Mindket’s setup notes in your downloads folder. Have these ready before you import it.

1. In n8n, create a workflow, open its menu, choose Import from File and pick workflow.json.
2. In Telegram, ask BotFather for a bot, then add a Telegram API credential with its token in n8n.
3. Select that credential in Telegram Trigger, Telegram and Telegram1.
4. In HTTP Request1, replace YOUR_ANYMAILFINDER_KEY in the Authorization header with your key.
5. Save, then press Publish. The trigger only listens while the workflow is published.
6. Open your bot in Telegram, press Start and send a first message.

Anymail Finder’s documentation, read on 2 November 2026, shows the key as the whole header value, with no prefix. One line of the file differs from the source: Clean & Format Data split messages with /s+/, which cuts on the letter s, so a message like Jane Doe acme.com was refused. It now reads /\s+/, a split on spaces.

How to use it

Send the bot three words with a space between them: first name, last name and domain. The reply follows once Anymail Finder has checked the four addresses, and holds one message for each address that verified or a note that none did. Fewer than three words stops the run with an error under Executions, and the chat gets no answer.

Example

This message to the bot:

Jane Doe acme.com

The bot checks jane@acme.com, janedoe@acme.com, jane.doe@acme.com and jdoe@acme.com. If two of them come back valid, you get two replies, each naming the address and its status.

For newcomers and experts

If you are new. n8n draws a workflow as boxes joined by lines, and each box, a node, does one job. This one listens to a Telegram bot, runs two short scripts and calls a verification service. You can read the scripts in the two Code nodes without changing them. Publish, message the bot, then open Executions to see what each node received.

For experts. The guess list is code, so the useful edits are there. It builds up to 36 shapes, puts five common ones first and returns the first four. Its own comment says 50, but the last line returns four.

Good to know

Each message costs credits, and the bot answers anyone who finds it.

• Billing: Anymail Finder charges 0.2 credits per verification whatever the result, and repeats within 30 days are free, so one message costs about 0.8 credits
• Open bot: anyone who finds the bot’s username can message it and spend your credits, so limit the trigger to your own chat or user ID
• Guesses: a valid result shows that a mailbox exists, not that it belongs to that person
• Your data: the name and domain go to Anymail Finder. Check the rules for cold email where you send before you write to anyone
• Credentials: the JSON holds none, and nothing from its author’s account