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

3
packages/verae-zapier-middleware/test/unit/veraeClient.test.js
View file

@ -18,6 +18,9 @@ describe('veraeClient mock', () => {
it('create → wait → completed', async () => {
const login = await veraeClient.login({ username: 'u', password: 'p' });
assert.ok(login.token.startsWith('mock-jwt-'));
const again = await veraeClient.login({ username: 'u', password: 'p' });
assert.equal(login.user.id, again.user.id);
assert.match(login.user.id, /^vu_[0-9a-f]{16}$/);
const { jobId } = await veraeClient.createTimestamp(login.token, {
data: 'hello',