Post to Telegram from Zapier

Wire Zapier to one endpoint, then publish or schedule Telegram channel posts, media and albums from any trigger you already run — with a signed webhook for every delivery.

How it connects

A Webhooks by Zapier action, so any Zap trigger becomes a scheduled post. There is nothing to install on the Zapier side and no per-network module to configure — Telegram is a channel id in the request body.

POST https://api.postwharf.com/v1/posts
Authorization: Bearer YOUR_WORKSPACE_KEY
Content-Type: application/json

{
  "text": "Shipping today.",
  "channels": ["ch_your_telegram_channel"]
}

A typical Telegram automation

The whole integration is a Webhooks action at the end of a Zap, with the fields mapped from the trigger. Trigger on a new row in a sheet, then queue the post rather than publishing it straight away:

{
  "text": "New this week",
  "channels": ["ch_your_telegram_channel"],
  "publish_at": "2026-09-01T09:00:00Z"
}

Find the channel id once from GET /v1/channels — the one you want carries "platform": "telegram". Text longer than 4,096 characters is refused with a 422 in your hand, rather than accepted and rejected by Telegram minutes later.

What Telegram accepts

Character limit4,096
Counted onone message
Formatschannel posts, media and albums

Posts go to channels you administer through a bot token you create and control.

Getting the result back

Register a webhook and every delivery outcome is posted to you — published, retrying, failed, or removed after publishing. Each is signed with HMAC-SHA256, so Zapier can verify it came from us before acting on it. That is the difference between a run that succeeded and a post that landed, and only the second one is worth a notification.

One thing worth setting up correctly

A Zap runs in a line, which makes it tempting to build one per network. Do not — every channel id goes in the same `channels` array, so five networks is one action, one Zap task, and one post carrying five receipts.

Questions

Can Zapier post to Telegram automatically?

Yes. Zapier calls one REST endpoint with a workspace key, so any trigger you already have can publish or schedule to a connected Telegram channel without a Telegram-specific module.

What do I need before Telegram will work?

Posts go to channels you administer through a bot token you create and control. Once the channel is connected in PostWharf, Zapier reaches it the same way it reaches every other network.

How long can a Telegram post be?

4,096 characters, counted on one message. PostWharf checks that before the post is queued, so an over-length post is refused immediately rather than failing at Telegram after everything else in the same batch has already published.