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 Webhook

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

towebhook.outWebhook
urlhttps://api.acme.com/hooks

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 Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

01
set the URL
Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.
02
choose auth
None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.
03
confirm receipt
Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered

POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

notes

Endpoints must respond within 10 seconds; slower responses are treated as failures and retried.
Retries use exponential backoff for several attempts before dead-lettering — make your handler idempotent.
Verify the HMAC signature before trusting a payload; the raw body is signed, so compute the digest before JSON parsing.

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 →