marchon/zapier-user-docs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Initial import of zapier-user-docs from zapier monorepo

Browse source
This commit is contained in:
George Lambert 2026-09-11 13:26:20 -04:00
commit e498e40f1a
16 changed files with 298 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
01-what-you-get.md Normal file
View file

@ -0,0 +1,19 @@
# 1. What you get
Verae Time proves that a SHA-256 existed at a given time. Zapier lets you do that from the tools you already use (Drive, email, CRM, forms) without writing HTTP clients.
Three kinds of proof:
| Proof | Where it lives | Zapier search |
|-------|----------------|---------------|
| **Itemized seal** | Main Verae chain (`api.veraetime.net`) | Find Timestamp by SHA256 |
| **Bulk Merkle root** | Main chain, one seal for many items | Create Batch Timestamps |
| **Leaf inclusion** | External tree-node archives (NATS, never Zapier) | Find Hash (tree nodes + central chain) |
You also get:
- A **zappier** customer portal: account, API key, usage, invoices, prepaid balance.
- A **Zapier** integration: creates, searches, and a “timestamp completed” trigger.
- Optional **public metadata**, **encrypted private metadata**, and **file attachments** stored on WORM archives — not on the blockchain.
Zapier talks **HTTPS only** to zappier-edge. zappier meters the call and forwards to Verae middleware. Middleware talks to the chain and, when asked, to archive/tree-node NATS servers. You never configure NATS in Zapier.