Handle Certyneo e-signature webhooks and archive signed PDFs to Google Drive

by Certyneo · 2 views · created 2026-08-19 · Document Extraction

What this workflow does

This workflow has 15 nodes and runs manually, when you click “Execute workflow” (plus 2 other triggers). Along the way it connects Google Drive. It also calls certyneo.com over HTTP.

How it runs

Trigger: Manually, when you click “Execute workflow” (plus 2 other triggers).

1. Register the Certyneo webhook (HTTP Request): calls certyneo.com (POST)
2. Contract settings (Edit Fields (Set)): sets 6 fields: templateId, signerName, signerEmail…
3. Compute the expected signature (Crypto): hashes or encrypts values
4. Create the envelope in Certyneo (HTTP Request): calls certyneo.com (POST)
5. Signature valid? (If): checks a condition and branches into true / false
6. Send the envelope to the signer (HTTP Request): calls an HTTP API (POST)
7. Keep completed envelopes only (Filter): keeps only the items that match a condition
8. Reject the forged event (Stop and Error): stops the run with an error
9. Download the signed PDF (HTTP Request): calls an HTTP API (GET)
10. Archive the signed PDF (Google Drive): upload (file)

…plus 2 more steps. See the full node list below.

Services it uses

Google Drive

HTTP calls to: certyneo.com

Before you upgrade to n8n 3.0

Nodes used (9)

• Manual Triggern8n-nodes-base.manualTrigger
• HTTP Requestn8n-nodes-base.httpRequest
• Edit Fields (Set)n8n-nodes-base.set
• Webhookn8n-nodes-base.webhook
• Crypton8n-nodes-base.crypto
• Ifn8n-nodes-base.if
• Stop and Errorn8n-nodes-base.stopAndError
• Filtern8n-nodes-base.filter
• Google Driven8n-nodes-base.googleDrive

From the author

Quick overview Sends a contract for signature from a Certyneo template, verifies the HMAC signature on every event Certyneo posts back, then files the sealed PDF and its audit trail in Google Drive as soon as the signer is done. How it works 1. Everything you…

View the original on n8n.io → Check your own copy