Can I flag unexpected file types?

Branch on the mime field so an executable in a documents bucket reaches the channel while ordinary uploads stay quiet.

How do I watch storage growth?

Land every upload in Postgres with size_bytes and bucket, and aggregate by bucket over time.

Does the file itself pass through?

No — only the metadata you send. The bytes stay in your storage; ingestlayer routes the event, not the object.

Track file uploads in Telegram

Keep an eye on what's being uploaded — large files, unusual types, heavy buckets — and route the ones worth a second look.

01source

sourcesdk.eventTypeScript SDK

matchfile.uploaded

02pipeline · 1 steps

01CTLfilter.matchsize ≥ 100 MB only

03destinations · 1

totelegramTelegram
chat@oncall

the event

You emit file.uploaded with this shape. The TypeScript SDK keeps the call type-safe, and the event is stored whole — so every field below is available to the pipeline by name.

user_idstring
file_idstring
size_bytesnumber
mimestringcontent type
bucketstring

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit file.uploaded

import { ingest } from "@ingestlayer/sdk";

await ingest("file.uploaded", {
  user_id:    ctx.user.id,
  file_id:    object.key,
  size_bytes: object.size,
  mime:       object.contentType,
  bucket:     object.bucket,
}, {
  idempotencyKey: object.key,
});

route it to Telegram

Message a person, group, or channel through a connected bot.

01
connect a bot
Create a bot with @BotFather and paste its token. We register the webhook and verify it in-region.
02
start a chat
Send /start to the bot from the target chat — or add it to the group/channel — then pick the chat from the list.
03
format the text
Messages use MarkdownV2; the default template bolds the event name and lists fields. Reserved characters in field values are escaped for you.

in telegramdelivered

oncall
*support.ticket.created*
ticket    T-4821
subject   API returning 500s
tier      enterprise
urgency   critical

notes

Telegram caps a bot at roughly 30 messages per second overall, and one per second to a single chat.
The bot must be added to a group — and promoted to admin for a channel — before it can post.
MarkdownV2 requires escaping characters like _ * [ ] ( ); ingestlayer escapes field values, but custom templates are your responsibility.

questions

Can I flag unexpected file types?: Branch on the mime field so an executable in a documents bucket reaches the channel while ordinary uploads stay quiet.
How do I watch storage growth?: Land every upload in Postgres with size_bytes and bucket, and aggregate by bucket over time.
Does the file itself pass through?: No — only the metadata you send. The bytes stay in your storage; ingestlayer routes the event, not the object.

build this pipeline or read the quickstart →