plan gallery · webhook
Auth0 → Neon → Inngest
Background job auth — JWT from Auth0, queries on Neon, work on Inngest.
Architecture
- 01auth0post-login action or api audience token
- 02neonjob writes land with the auth0 sub as owner
- 03inngestfan-out work that must not run as anon
Env-var matrix
Security checklist
- verify inngest signing key on the serve endpointanyone can POST fake job events otherwise
- pass auth0 sub explicitly into job payloadsbackground workers have no browser cookie
- use a pooled neon url in serverlessconnection exhaustion looks like flaky auth
Folders
· src/inngest/client.ts · src/inngest/functions/onboarding.ts · src/db/neon.ts