Developer map of the Verae Time × Zapier NATS message
fabric: what was designed, what is actually running on NS1, how
a Zapier timestamp job reaches api.veraetime.net (or the
mock) and comes back, and what is still unwired.
Forgejo:
https://git.georgelambert.org/marchon/dev-overview
SSH:
ssh://git@git.georgelambert.org:2223/marchon/dev-overview.git
Catalog:
https://zapier.georgelambert.org/packages/dev-overview/
Date: 2026-09-14
Zapier cloud never connects to NATS. It talks HTTPS
to https://zap.zapier.georgelambert.org (access-zapier)
then middleware. api.veraetime.net is HTTPS
only — middleware is the NATS client.
| Doc | What |
|---|---|
| 00-sources.md | Every other doc that names a NATS address or TCP route |
| 01-nats-routes.md | Transport ports + every verae.* address: designed vs
running |
| 02-endpoint-io.md | Per-address: purpose, inbound from, outbound to, how to connect Verae API |
| 03-zapier-verae-path.md | Zapier → middleware → Verae timestamp server → poll → events → Zapier |
| 04-gaps-and-finish.md | Modules not connected; billing/event/aux; ordered finish list |
| 05-developer-credentials.md | URLs, tokens, lab API keys, staff/IAM, git, env cheat sheet |
nats://10.10.10.21:4222,nats://10.10.10.22:4222,nats://10.10.10.23:4222JetStream streams (replicas=3, file): ZAPIER_JOBS,
ZAPIER_EVENTS, ZAPIER_WEBHOOKS,
ZAPIER_USAGE, VERAE_ARCHIVE.
Public token-gated client edge (not cluster routes):
nats://<token>@70.88.205.138:4222,
wss://nats.zapier.georgelambert.org. Do not put this in
Zapier.