Post to Telegram from n8n

Wire n8n 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

No custom node needed — an HTTP Request node and a workspace key is the whole integration. There is nothing to install on the n8n 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 {{$env.POSTWHARF_KEY}}
Content-Type: application/json

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

A typical Telegram automation

The whole integration is one HTTP Request node, sitting between your trigger and whatever comes after it. Trigger on a new RSS item, 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 n8n 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

If that node is set to retry on failure, a retry is a second post rather than a second attempt at the first one. Leave it off: PostWharf already retries the delivery itself, and the receipt is where you find out whether it worked.

Questions

Can n8n post to Telegram automatically?

Yes. n8n 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, n8n 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.