marchon/master-zapier-plan-draft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

Bind each customer to a Verae userId for hop tracing
Some checks are pending
offline / test (push) Waiting to run
Details

Browse source 
Signup registers/binds a Verae central user and stores veraeUserId. Public access stays the zappier API key. Chain JWTs stay server-side behind tokenRef. Authz, billing, and jobs.watch carry veraeUserId.
This commit is contained in:
George Lambert 2026-09-11 16:18:06 -04:00
parent 1b199ca4d4
commit 345aeeead9
79 changed files with 703 additions and 95 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/sphinx/modules/verae-zapier-middleware/middleware/authenticate.md
View file

@ -2,7 +2,7 @@
**Package:** `verae-zapier-middleware`
**Source:** `packages/verae-zapier-middleware/src/middleware/authenticate.js`
**Lines:** 28
**Lines:** 34
## What this module is
@ -35,7 +35,7 @@ _No top-level functions extracted._
## Call graph (identifiers invoked)
`createDebugger`, `asyncHandler`, `async`, `extractBearerToken`, `resolveAuthContext`, `debug`, `next`
`createDebugger`, `asyncHandler`, `async`, `extractBearerToken`, `resolveAuthContext`, `startsWith`, `debug`, `next`
Each identifier is a call site in this file. Follow the import list to see the defining module; open that module’s MD for parameter and return types.