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

8
docs/modules/zappier/billing-nats.md
View file

@ -2,7 +2,7 @@
**Package:** `zappier`
**Source:** `packages/zappier/src/billing-nats.ts`
**Lines:** 130
**Lines:** 138
## What this module is
@ -29,11 +29,13 @@ Implementation module in `zappier`. The tables below are extracted from the sour
| `decode` | `buf: Uint8Array` | — | `unknown` | see Call graph |
| `authzAllow` | `plane: AccessPlane,
subject: string,
extra: { principal?: string; kind?: string } = {},` | — | `unknown` | see Call graph |
extra: { principal?: string; kind?: string; veraeUserId?: string } = {},` | — | `unknown` | see Call graph |
| `natsStatement` | `customerId: string,
plane: AccessPlane = 'web',` | — | `unknown` | see Call graph |
plane: AccessPlane = 'web',
veraeUserId?: string,` | — | `unknown` | see Call graph |
| `natsAdjust` | `payload: {
customerId: string;
veraeUserId?: string;
cents: number;
reason: string;
agent: string;