Hogsend is brand new.Try it
Messages and /start links in, journey replies out.

Integrate Telegram into your lifecycle marketing

Inbound messages and /start deep-links become events your journeys trigger on; journeys reply with sendMessage / dm. A member whose email you don't have sends /link you@example.com, clicks the emailed confirmation link, and their Telegram binds to your contact — the PostHog identify fires client-side, so the location is the member's, not your datacenter's. It's a defineConnector in your repo.

How it works

A bot, a webhook, and your journeys

Point a Telegram bot at POST /v1/webhooks/telegram with TELEGRAM_BOT_TOKEN and TELEGRAM_WEBHOOK_SECRET. Inbound updates become telegram.message, telegram.started, telegram.linked, and telegram.link_requested events; journeys reply with sendMessage and dm. It's domain-agnostic — any Telegram bot, any topic.

What you can do

Six things it does the day you turn it on

Act on what they send

Inbound messages become telegram.message events you can trigger journeys on.

telegram.message

Welcome people who /start

A /start deep-link starts a journey, so the first reply is automatic.

/start

Reply from your journeys

Journeys answer with sendMessage and dm through sendConnectorAction.

sendMessage + dm

Bind a Telegram account to an email

A member runs /link you@example.com, clicks the emailed confirmation link, and they're emailable too.

/link

Identify from the member's device

The PostHog identify fires client-side on confirm, so the location is the member's, not your datacenter's.

client-side identify

One profile across everything

Telegram sits next to email, product activity, and PostHog on a single contact via telegram:<id>.

one contact
Linking

Bind a Telegram account to an email — by clicking a link

A member whose email you don't have sends /link you@example.com. Hogsend emails a confirmation link; clicking it binds their Telegram to your contact and fires the PostHog identify client-side, keyed to a server-proven contact key — so the location is the member's, not your datacenter's.

Get started

Set it up

Create a Telegram bot with BotFather, point its webhook at Hogsend, paste TELEGRAM_BOT_TOKEN and TELEGRAM_WEBHOOK_SECRET, and run it. The full walkthrough is in the docs.