A question that comes up here now and then: “how do I generate/issue certificates to my users from a workflow, and make them actually checkable — not a photoshoppable PDF?” Sharing a small tutorial in case it saves someone time. Two ways, pick whichever fits — no account signup needed to try either.
What you get: each certificate gets a permanent public verify page with an Ed25519 signature, so the recipient (or whoever they show it to) can confirm it’s genuine and unaltered — unlike a PDF, which anyone can edit.
Option A — the community node (n8n-nodes-attestify)
- In Settings → Community Nodes → Install, add
n8n-nodes-attestify(verified node, searchable in-app). - Drop the Attestify node into your flow after whatever event should mint a cert (course completed, form submitted, deal closed).
- Set issuer + recipient name/email + the credential fields → run. The node returns the cert id and the public verify URL.
Option B — no install, just an HTTP Request node (30-second version)
If you’d rather not install a community node, one core HTTP Request node does it:
- Method POST →
https://attestify.novadyne.ai/cert/issue - Body (JSON):
{
"issuer": "Your Academy",
"course": "Advanced Workflow Automation 2026",
"recipients": [{ "name": "Jane Doe", "email": "jane@example.com" }]
}
- The response includes each cert’s public verify URL. That’s it — importable workflow here: n8n-nodes-attestify/workflows/issue-verifiable-certificate.json at main · novadyne-hq/n8n-nodes-attestify · GitHub
Checking a cert is just opening its verify URL — the page reads the authoritative signed record and shows Verified + the details, or flags a mismatch.
Full disclosure: I work on Attestify (it’s the tool in both options). Happy to answer questions on either approach, or on wiring it to a specific trigger.