|
Some checks are pending
offline / test (push) Waiting to run
In-process trace console validates hops, faults, recoveries, and suggested changes before zapier-platform push. User guide covers signup through central-chain and bulk-summary tree-node hash lookup. |
||
|---|---|---|
| .. | ||
| 01-what-you-get.md | ||
| 02-signup-zappier-portal.md | ||
| 03-connect-zapier.md | ||
| 04-register-a-hash.md | ||
| 05-wait-async-hooks.md | ||
| 06-lookup-central-chain.md | ||
| 07-attachments-and-metadata.md | ||
| 08-bulk-merkle-summaries.md | ||
| 09-lookup-tree-nodes.md | ||
| 10-reading-receipts.md | ||
| 11-errors-billing-retries.md | ||
| 12-security.md | ||
| NATS.md | ||
| package.json | ||
| README.md | ||
| SUMMARY.md | ||
Verae Time for Zapier — user guide
How to go from zero account to registering SHA-256 hashes, looking them up on the central Verae chain, and finding hashes that were only sealed as part of a bulk Merkle summary on external tree-node archives.
This is the customer-facing guide (signup → Zaps). Developers: see zapier-docs-master and the simulator at verae-zapier-simulator.
Live catalog: https://zapier.georgelambert.org/
Clone: ssh://git@git.georgelambert.org:2223/marchon/zapier-user-docs.git
Contents
- What you get
- Sign up for a Verae / zappier account
- Connect the Zapier app
- Register a SHA-256 (create timestamp)
- Wait, async, and completed hooks
- Look up a hash on the central Verae chain
- Attachments and metadata (not on chain)
- Bulk Merkle summaries
- Look up a hash on tree-node archives
- Reading receipts
- Errors, billing, retries
- Security: what Zapier never sees
Try it without going live
The interface simulator is a Zapier-like form plus a trace console. Run Batch Merkle, copy a leaf SHA-256, then Find Timestamp by SHA256 (miss) vs Find Hash (tree nodes) (proof).