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 Email

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

toemail.outEmail
toalerts@acme.com

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 Email

Send a transactional email to one or more recipients, addressable from event fields.

01
set the recipient
Enter a fixed address, or reference an event field like $event.payload.email to route per event.
02
write subject and body
Both accept $event.* templates. The body renders as plain text with an optional summary table of the payload.
03
confirm the sender
Mail goes out from mail@notify.ingestlayer.com with SPF and DKIM aligned. Set a reply-to if you want responses to reach you.

in emaildelivered

From:    mail@notify.ingestlayer.com
To:      alerts@acme.com
Subject: Payment failed — acme-inc (€240.00)

A charge failed for acme-inc.
  amount   €240.00
  reason   insufficient_funds
  attempt  2

notes

Outbound email is metered against a monthly quota that scales with your plan; over-quota sends are deferred, not dropped.
Sending from a fixed ingestlayer domain keeps deliverability high, but the From address is not your own domain.
Recipient addresses pulled from event fields are validated at send time; a malformed address dead-letters that delivery.

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 →