George Lambert
f3dc0e6eee
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.
1.3 KiB
1.3 KiB
4. Register a SHA-256 (create timestamp)
Two Zapier creates:
| Action | What happens | What you get back |
|---|---|---|
| Create Timestamp (async) | Submit hash, return immediately | jobId, sha256, existing |
| Create Timestamp and Wait | Submit hash, hold the Zap step until the certificate exists (or timeout) | status, receipts[], completedAt |
Inputs
- Data — raw text/bytes. Middleware hashes it with SHA-256. Prefer this when the previous Zap step has the document contents.
- SHA256 — 64 hex characters if you already hashed the file outside Zapier (recommended for large files: hash locally, send only the digest).
- Hash algorithm —
SHA256(default).
Do not send the whole PDF to the blockchain. Only the digest is sealed.
Already registered
If that SHA-256 was sealed before, you get the original jobId and certificate. A second chain write is not created. existing: true.
Example Zap
- Trigger: “New file in Google Drive”.
- Action (optional): compute SHA-256 in a Code step, or pass file contents as Data.
- Action: Create Timestamp and Wait.
- Action: store
jobId,sha256, and certificate in your sheet/CRM.
Simulator: scenario Register (wait + includeAttached).