marchon/master-zapier-plan-draft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
master-zapier-plan-draft/packages/docs-master/modules/zappier/NATS.md
George Lambert 345aeeead9
Some checks are pending
offline / test (push) Waiting to run
Details
Bind each customer to a Verae userId for hop tracing 
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.
2026-09-11 16:18:06 -04:00

883 B
Raw Blame History

NATS — zappier-edge

Zapier cloud still never connects to NATS. The edge process does publish and request on the private billing bus.

Direction Address Peer Body
IN HTTPS /v1/* Zapier Platform app JSON + x-api-key
OUT HTTPS middleware /zapier/v1/* verae-middleware same tenant request
OUT NATS verae.billing.usage.recorded account-balance meter event (customerId, veraeUserId)
OUT NATS verae.billing.payment.recorded account-balance / others portal reload
OUT NATS verae.billing.credit.applied account-balance / others admin/CS credit
OUT NATS verae.billing.statement.get account-balance portal/admin review
OUT NATS verae.billing.balance.adjust account-balance prepaid mutation

Jobs, archive, and webhooks stay on middleware workers.