Some checks are pending
offline / test (push) Waiting to run
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.
2 KiB
2 KiB
verae-zapier-middleware/workers/jobPollerWorker
Package: verae-zapier-middleware
Source: packages/verae-zapier-middleware/src/workers/jobPollerWorker.js
Lines: 161
What this module is
Implementation module in verae-zapier-middleware. The tables below are extracted from the source (signatures + JSDoc).
Exports
startJobPollerWorker, stopJobPollerWorker
Types / interfaces / classes
None extracted.
Functions
| Name | Parameters | Param types (JSDoc) | Returns | Calls (same file / helpers) |
|---|---|---|---|---|
resolveVeraeToken |
msg |
msg: object |
Promise<string> |
see Call graph |
handleWatch |
data, ctrl |
data: object |
unknown |
see Call graph |
startJobPollerWorker |
(none) |
— | Promise<{ stop: () => Promise<void> — >} |
see Call graph |
stopJobPollerWorker |
(none) |
— | Promise<void> |
see Call graph |
What it imports / requires
../debug/logger.js../config.js../nats/subjects.js../nats/connection.js../nats/publishers.js../clients/veraeClient.js../store/tenants.js../store/tokenRefs.js../debug/trace.js
Call graph (identifiers invoked)
createDebugger, polling, resolveVeraeToken, resolveTokenRef, getTenant, login, handleWatch, withTrace, async, publishJobEvent, ack, getStatus, debug, nak, startJobPollerWorker, stopJobPollerWorker, connectNats, ensureStreams, consumer, add, get, info, consume, parse, string, error, abort
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.
Return values (how to read this)
- HTTP route handlers return Express
res.json(...)bodies (see route docs). - Zapier
performfunctions return a single object (creates) or an array (triggers/searches). - Pricing functions return integer cents on
Quote.totalCents.