Your Neon Functions can now run on a schedule

Neon has introduced Function Triggers, beginning with cron-based schedules, to automatically invoke deployed Neon Functions for backend tasks while remaining compatible with scale-to-zero Postgres branches. Neon Functions run Node.js code in the same branch and region as a Lakebase Postgres database, with database, Object Storage, and AI Gateway credentials available automatically, making them suited to jobs such as synchronizing external APIs, generating embeddings, cleaning authentication data, resetting staging branches, and reconciling database records with stored objects. Triggers are branch-scoped, inherited by child branches in a disabled state, and can be modified independently to prevent test branches from affecting production schedules. Unlike pg_cron, which runs SQL or Postgres functions inside an active database compute and therefore does not run when the compute has scaled to zero, Function Triggers execute JavaScript or TypeScript functions and can make HTTP requests or access Neon services before writing results to Postgres. The announcement includes an uptime-check example and advises users replacing external schedulers to create idempotent function handlers, validate trigger invocations, use five-field UTC cron schedules, and configure triggers through the Neon API.

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.