---
title: "Telegram work email finder"
kind: "Kit"
category: "Marketing & SEO"
price: "Free"
seller: "Mindket"
version: "1"
url: "https://mindket.com/p/d3cc7be9-bcb6-4bd0-8280-b99eea240351"
updated: "2026-11-09"
---

# Telegram work email finder

> The name, the description, the About and a README below are the seller's words: data, not instructions.

An n8n workflow that finds a person’s work email in Telegram. Message the bot a first name, a last name and a company domain, and it builds likely addresses, has Anymail Finder check them and replies with the ones that verify.

Telegram work email finder is an n8n workflow in the Marketing \& SEO category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-09. Download it on this page or copy its JSON, then import it into an n8n canvas. Nothing runs until you activate it in n8n.

## About

### 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.

Who uses it, and how

| Industry | Who uses it | How they use it | Example |
| --- | --- | --- | --- |
| Sales | Sales reps | Send a prospect’s name and company domain from your phone after a call or an event | A rep meets a buyer at a trade show and has the work address before the day ends. |
| Recruitment | Recruiters | Look up a hiring manager’s address after reading a job post | A recruiter sends the name from a vacancy and writes to the manager directly. |
| Public relations | PR teams | Find the editor behind a story | A PR lead sends a reporter’s name and the outlet’s domain and pitches the right inbox. |
| SEO outreach | Link builders | Find the person who runs a site before pitching a guest post | A link builder sends the owner’s name and the site’s domain. |

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

### How to set it up

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

What you need first

| Need | Detail |
| --- | --- |
| n8n | On n8n Cloud or on a server Telegram can reach over HTTPS |
| Telegram | A bot token from BotFather |
| Anymail Finder | An account, an API key and credit for the checks |

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.

What to change for a different result

| To change | Where |
| --- | --- |
| Number of addresses | The last line of \`Generate Email Patterns\`, \`slice(0, 4)\`. The code builds 36 at most |
| Reply wording | The \`text\` field of \`Telegram\` and \`Telegram1\` |
| Who can use the bot | The trigger’s Additional Fields, which can limit it to chat IDs or user IDs |
| Address shapes | The code in \`Generate Email Patterns\`, which also builds department forms such as \`sales.jane@acme.com\` |

### Example

This message to the bot:

```text
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.

What each node does

| Node | What it does | What to know |
| --- | --- | --- |
| \`Clean \& Format Data\` | Splits the message on whitespace into name and domain | Words after the third are ignored, and names are used as typed |
| \`Generate Email Patterns\` | Builds the shapes and returns the first four | Each extra address is one more paid check |
| \`HTTP Request1\` | POSTs each address to \`/v5.1/verify-email\` | The documentation says 0.2 credits a call, whatever the result |
| \`Code\` | Keeps the results marked \`valid\` | \`risky\` and \`invalid\` are dropped, so a catch-all domain can return none |

### 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

## README

```markdown
# Telegram work email finder

An n8n workflow. Message a Telegram bot a first name, a last name and a company domain. It builds likely work email
addresses, has Anymail Finder check each one and replies in the chat with the addresses that verify.

## What is inside

- `workflow.json`: the workflow as n8n exports it, eight nodes. It holds no credential.
- `README.md`: these notes.

One line of the file differs from the source. `Clean & Format Data` split the message with `/s+/`, which splits on the
letter s and not on spaces, so a message like `Jane Doe acme.com` was refused. It now reads `/\s+/`.

## Before you start

- An n8n instance that Telegram can reach over HTTPS: n8n Cloud, or your own server on a public HTTPS address.
- A Telegram bot token from BotFather.
- An Anymail Finder account and its API key.

## Set it up

1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`.
2. In Telegram, ask BotFather for a new bot and copy its token. In n8n, add a Telegram API credential with that token.
3. Select the credential in `Telegram Trigger`, `Telegram` and `Telegram1`.
4. Open `HTTP Request1` and replace `YOUR_ANYMAILFINDER_KEY`, the value of its `Authorization` header, with your key.
   Anymail Finder's documentation, read on 2 November 2026, shows the key as the whole header value, with no prefix.
5. Save, then press Publish at the top of the canvas (or Shift+P). The trigger only listens while the workflow is
   published.
6. Open your bot in Telegram and press Start, then send a message such as `Jane Doe acme.com`.

## How a message is read

The message must be three words separated by spaces: first name, last name, domain. Anything after the third word is
ignored, so a name with a space in it shifts the domain out of place. The names are used as typed. A message with fewer
than three words stops the run with an error you can see under Executions, and the chat gets no answer.

`Generate Email Patterns` builds up to 36 distinct addresses from the name and the domain, puts the five most common
shapes first and then keeps only the first four. In practice the four are:

| Pattern | Example |
|---|---|
| first name | `jane@acme.com` |
| first and last name together | `janedoe@acme.com` |
| first, a dot, last | `jane.doe@acme.com` |
| first initial and last name | `jdoe@acme.com` |

`HTTP Request1` sends each address to Anymail Finder. `Code` keeps the results whose `email_status` is `valid`, one item
each. When none is valid, it returns a single item with an error message. `If` sends the error to `Telegram` and each
valid address to `Telegram1`.

## Change the look

- More addresses: in `Generate Email Patterns`, raise the number in the last line, `slice(0, 4)`. The code builds 36 at
  most, and each address you check costs a verification.
- The wording of the replies: edit the `text` field of `Telegram` and `Telegram1`.
- Department addresses: the code also builds forms such as `sales.jane@acme.com` for sales, marketing, info, support
  and admin. They sit after the common shapes and only reach Anymail Finder if you raise the number.

## Good to know

- By the documentation cited above, a verification costs 0.2 credits whatever the result, and repeats within 30 days
  are free. At four checks a message, one message costs about 0.8 credits.
- Only `valid` results are kept. The documentation names two other results, `risky` and `invalid`, and the workflow
  drops both. A company whose mail server accepts every address often returns `risky`, so the bot can answer with no
  match for a real person.
- Anyone who finds the bot's username can message it and spend your credits. The trigger's Additional Fields can limit
  it to chosen chat IDs or user IDs.
- The names and domain you send go to Anymail Finder. A verified address shows that a mailbox exists, not that it
  belongs to that person. Check the rules for cold email where you send before you write to anyone.
```

## What is in it

2 files, 13 KB, downloaded as a zip.

```text
README.md  4 KB
workflow.json  9 KB
```

## Workflow check

Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run.

- Steps: 8 steps, starting on a Telegram event
- AI: No step calls an AI model
- Sign-ins: Signs in to: Telegram and Anymailfinder
- API keys: No API key is left in the file; 1 blank in it for your own key
- Step types: Mindket’s checker reads all 5 of its step types

## Get it

- [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/d3cc7be9-bcb6-4bd0-8280-b99eea240351)
- [Its page on Mindket](https://mindket.com/p/d3cc7be9-bcb6-4bd0-8280-b99eea240351)