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 Slack

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

toslackSlack
channel#alerts

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 Slack

Post to any channel in your workspace. Connect once with OAuth, pick the channel per pipeline.

01
connect your workspace
Authorize the ingestlayer Slack app over OAuth from the destinations page. We hold only a channel-scoped bot token, in-region, in the same KMS as your other credentials.
02
pick a channel
Choose any public channel, or invite the bot to a private one. The channel is set per pipeline, so different events can land in different places.
03
map the message
Reference event fields with $event.* in the message template. The default renders a titled block with the event name and its key fields.

in slackdelivered

┌─ #alerts ──────────────────────────────┐
│  ingestlayer  APP                       │
│  user.signed_up                         │
│  email   ada@acme.com                   │
│  plan    pro                            │
│  source  marketing-site                 │
└─────────────────────────────────────────┘

notes

Slack rate-limits to roughly one message per second per channel; bursts are queued and retried, never dropped.
The bot must be a member of a private channel before it can post there — invite it explicitly.
Block Kit caps a message at 50 blocks and 3000 characters per text field; oversized events are truncated with a link to the full payload.

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 →