n8n

The Verifycate community node connects a workspace to n8n, so certificate work can run inside the workflows your team already uses.

Repository: verifycate/n8n-nodes-verifycate

Install

The package is published as @verifycate/n8n-nodes-verifycate and is awaiting review for the n8n verified community node program. Self-hosted n8n can install it now from npm. Verified nodes can be installed from the nodes panel on n8n Cloud and self-hosted n8n.

Open Settings → Community nodes, choose Install a community node, and enter @verifycate/n8n-nodes-verifycate.

Connect

1. In Verifycate, open Workspace → API Keys and create a key with certificates:read and certificates:write.
2. In n8n, add a Verifycate action or Verifycate Trigger node.
3. Create a Verifycate API credential and paste the key.
4. Leave the base URL as https://api.verifycate.com unless Verifycate support gave you a staging URL.
5. Save. n8n confirms the key against GET /api/v1/workspaces/current.

The key identifies its workspace. There is no workspace slug to copy.

Actions

Resource	Operations
Certificate	Create, Get, Get Many, Update, Delete
Certificate Issue	Add Recipient, Get, Get Many, Issue, Update, Revoke, Replace, Reissue, Remind, Delete
Recipient	Get, Get Many
Request	Get Many, Approve, Reject, Reopen
Correction	Get Many, Approve, Reject, Reopen

Add Recipient loads the selected certificate's attributes into n8n's resource mapper. Re-enrolling an existing recipient returns the issue they already hold with already_enrolled: true, so a repeated workflow run does not fail.

Revoke, Replace, and Reissue check the current issue status first and explain what to do instead of returning a bare API error.

Trigger

The trigger subscribes to signed Verifycate webhooks. Choose one or more event types, or All Events, and optionally scope the trigger to one certificate.

The output is the Verifycate event envelope plus a verification_url and, unless disabled, the full certificate issue as issue.

Webhook requirements

Verifycate requires a public HTTPS endpoint. n8n Cloud provides one. For local n8n on http://localhost:5678, use a tunnel and set WEBHOOK_URL to the public HTTPS address before starting n8n.

Test a trigger

1. Click Test workflow in n8n.
2. In Verifycate, open Settings → Webhooks and find the subscription named after your workflow and node, for example n8n: New hire onboarding / Verifycate Trigger.
3. Send a test delivery for the event type, or complete a real certificate action.
4. The delivery appears in the n8n editor.

Deactivating the workflow removes the subscription. Reactivating it reuses the subscription when the URL, event list, and certificate filter still match.

Example workflows

Issue a certificate after a course

Use your LMS webhook or a schedule to find completed learners, then run Verifycate → Certificate Issue → Add Recipient with the certificate, recipient email, and mapped attributes. Send the returned verification_url to Slack.

Notify a channel when a certificate is verified

Start with Verifycate Trigger and the Engagement: Verified event, then send data.recipient_name, data.certificate_name, and verification_url to Slack, Teams, or a CRM.

Revoke on offboarding

Call Certificate Issue → Revoke with the employee's email and an audit reason. Use Replace only when the same person should receive a corrected credential; replacing costs one credit.

Troubleshooting

Symptom	Check
Credential test fails	The key may be revoked or missing certificates:read. Recreate it under Workspace → API Keys.
Activation says HTTPS is required	Set WEBHOOK_URL to a public HTTPS address, or use a tunnel for local development.
Trigger activates but no events arrive	Check the subscription event list and certificate filter, then inspect the delivery log in Verifycate.
Signature failures	Deactivate and reactivate the workflow so n8n creates a fresh subscription and signing secret.
Duplicate subscriptions	The trigger removes matching n8n subscriptions for the same webhook URL when it activates.

Delivery guarantees

Verifycate retries failed deliveries and can deliver the same event more than once. Store processed event ids or make the receiving step idempotent.

Source and issues

The node is MIT licensed and open source: verifycate/n8n-nodes-verifycate. Report issues there or contact hello@verifycate.com.