You add it like any other step. Put a step after the one that produces the file or record. That step computes a SHA-256 fingerprint of the content, sends the fingerprint to a timestamping service, and saves the proof id and certificate link it gets back. You can also add a trigger that starts a later step once the timestamp is confirmed on the blockchain. You don't need to write code, but each tool wires this up a little differently, and the record has limits worth knowing before you rely on it.
What the step does, in any workflow tool
Zapier, Make and n8n work the same way here. The steps are:
1. Hash the content. A SHA-256 hash is a 256-bit fingerprint, written as 64 characters of letters and numbers. Change one byte of the file and the fingerprint changes completely. You can't rebuild the file from its fingerprint. 2. Send only the hash. The timestamping service gets the fingerprint. It never sees the file, the invoice, the signed form or the photo. 3. Keep what comes back. That's a proof id and a link to a certificate. Store both next to the record they belong to: a spreadsheet row, a CRM field, a database entry. 4. Act when the anchor lands (optional). "Anchoring" means writing the fingerprint into a public blockchain transaction. A trigger can fire when that happens and run your next step: update a status, email the certificate link, file a copy.
The result is a dated record that someone outside your business can check. A timestamp in your own spreadsheet is your word. A fingerprint written into a public blockchain transaction comes with a date that nobody in your company controls.
What the record proves, and what it doesn't
The proof says this exact content existed no later than the moment it was anchored. That's all it says.
It doesn't say who made the content, who owns it, or whether it's accurate. It doesn't say when a photo was taken or when a document was first written. It can only cover content from the moment it passed through your workflow and got anchored. It can't go back and date something that was never recorded.
Where the hash is computed also matters. The workflow tool holds the file while the scenario runs, so the fingerprint is computed wherever that tool runs. You're trusting the workflow tool to hash the bytes it received. A person checking the proof later doesn't have to trust it, though. They hash their own copy of the file and compare. If the fingerprints match, it's the same content. If they don't, it isn't.
Wiring it in n8n
ProofLedger publishes a community node for n8n, n8n-nodes-proofledger, on npm. You install it from Settings > Community Nodes in n8n. It's a community node, not one n8n has reviewed.
It adds two nodes.
The ProofLedger node is the action. Point it at a binary field from an earlier node, such as an email attachment, a form upload or a file from cloud storage. It hashes the file inside n8n and sends only the hash. A Send File Name switch lets you leave out the file's name too, so the fingerprint is the only thing that leaves n8n. If an earlier step already produced a hash, the node can take that instead, either one at a time or up to 100 in one call. The same node can also read a proof back, fetch its verification bundle, check a hash, and manage webhooks.
The ProofLedger Trigger starts a workflow when a proof is anchored. It registers its own webhook with ProofLedger and checks the signature on every delivery, so a request that didn't come from ProofLedger is rejected.
A typical flow: a form submission comes in, the ProofLedger node hashes the attachment, and a spreadsheet node saves the proof id and certificate link. Then a separate workflow starts from the Trigger and marks the row as anchored.
The source is at github.com/Fulcrum-Enterprises/n8n-nodes-proofledger.
Wiring it in Zapier
The Zapier integration is private. You add it to your account with an invite link, and it isn't listed in Zapier's public app directory.
Once it's added, you get these steps:
- Create Proof From File hashes the file inside the Zap run, so only the hash reaches ProofLedger.
- Create Proof From Hash is for a Zap that already has a SHA-256 hash from an earlier step.
- Find Proof by External ID and Verify Hash are searches. You can use them later in a Zap to look up a proof or check a fingerprint.
- Proof Anchored is the trigger. It fires when an anchor lands and checks the signature on each delivery.
Here's a common pattern. One Zap creates the proof when a file arrives and saves the certificate link. A second Zap starts from Proof Anchored and passes the confirmation on to whoever needs it.
Wiring it in Make
The Make app is a published custom app that you install with an invite link. It isn't in Make's app directory.
There's one difference from the other two: Make has no file module. The Create a proof module takes a SHA-256 hash, so an earlier module in your scenario has to produce that hash. The file stays in Make, and Create a proof sends the fingerprint.
The other modules are Get a proof, Get a proof by external ID, Get a proof bundle, Verify a hash, List proofs, Get certificate branding, and Make an API call for anything the named modules don't cover.
The trigger is Watch anchored proofs, an instant trigger. It works differently from the Zapier and n8n triggers. It doesn't check signatures on deliveries. It reads each proof again from the ProofLedger API, so the data your scenario gets comes straight from the API.
One thing to know about the "anchored" triggers
All three triggers rely on a webhook, a message ProofLedger sends to your workflow when an anchor lands. A webhook covers proofs created after it was registered. Set up the trigger before you start creating proofs you want it to react to. For proofs created earlier, use the lookup steps (Get a proof, Find Proof by External ID, List proofs) instead of waiting for an event.
Anchoring on Polygon usually happens within a minute of submission. Each proof gets its own public transaction.
How someone checks the record later
The step is only worth adding if the person relying on the record can check it without asking you. With ProofLedger, there are three ways to check:
- The certificate link. Every proof has a public verify page. That page looks the proof up in ProofLedger's records.
- The bundle. Each proof has a bundle, a small file holding the hash, the chain, the transaction id and the anchor time. The n8n node and the Make module can fetch it, and it's also included in every anchored webhook payload. Save it with the record.
- Offline, without ProofLedger. The open
verify-proofpackage compares a file with its bundle on the checker's own machine, with no network call. Then anyone can look up the Polygon transaction on a public block explorer. That way the check doesn't depend on ProofLedger being reachable.
That's the reason to keep the bundle in the workflow and not only the link. The link is convenient. The bundle is what still works if no vendor is involved.
Where to get the invite links
The Zapier and Make invite links and the n8n install details are collected on proofledger.io/platforms. Each proof counts toward your account's monthly allowance, the same as a proof sent through the API. Plans and allowances are listed on the pricing page.