When a file is uploaded, run the job on Neon

Neon has introduced `storage_object_created` triggers, enabling Neon Functions to run automatically when files are uploaded to a specified Neon Object Storage bucket, optionally limited by key prefixes. The event-driven functions receive the bucket name and object key through an HTTP POST, can process files alongside Postgres in the same region, and retain scale-to-zero behavior while supporting long-running work. Suggested uses include cataloging uploads in Postgres, producing image variants, generating AI metadata, extracting and indexing document or audio content, and moderating or redacting uploaded files, though triggers occur after uploads and should not be used as an upload-blocking gate. Because Neon’s infrastructure is branch-scoped, buckets, functions, and triggers are inherited by child branches, but inherited triggers are disabled by default to prevent duplicate processing during development. Developers can provision buckets, functions, and triggers together through a `neon.ts` configuration file, and the feature complements Neon’s recently released scheduled function triggers.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.