Guides
n8n E-Signature Automation: Save Signed Documents to Google Drive with Firma.dev
Every signed document that lands in Firma.dev can kick off whatever happens next automatically. This guide covers the simplest version of that: the moment a signing request completes, n8n grabs the finished document and drops it straight into Google Drive. No polling, no manual downloads, no one on teh team remembering to file the paperwork away.
The workflow is four steps, and the video below walks through building the whole thing in under nine minutes.
Prerequisites
An n8n instance, cloud or self-hosted
A Firma.dev account and a workspace-level API key (more on why "workspace-level" matters below)
The Firma.dev community node installed in n8n, it covers the full API surface, trigger included. Install steps and the full operation list live in the n8n integration docs
A connected Google Drive account in n8n
The four-step workflow
1. Trigger on Signing Request Completed
Add a new workflow, search for Firma.dev in the node picker, and add the trigger. Choose the Signing Request Completed event.
Connect your Firma.dev account and enter your workspace ID, then copy the webhook URL n8n generates. Head into your Firma.dev dashboard: Settings → Webhooks → Webhook Endpoints → Add a webhook, paste the URL, select Signing Request Completed, and hit Create Webhook. Firma.dev hands back a webhook secret. That goes into the n8n credential alongside the API key.
Use the API key from the specific workspace you're automating, not the account-level key. Workspaces let you keep customers or departments separate, each with its own branding and its own scoped key, and the account-level key can create and delete workspaces outright. For something as narrow as this automation, the workspace key is the safer default.
Test it before moving on: hit Execute Step so the trigger starts listening, then send a real signing request (a single-signer template works well) so the rest of the workflow has actual data to work with.
2. Get Signing Request
Add a second step, search Firma.dev again, and choose Get Signing Request. Drag the signing request ID from the trigger's output into this node, not the ID of the webhook delivery itself. The two sit right next to each other and look similar, but this node needs the signing request ID specifically. Execute the step and it pulls the full detail for that request.
3. Download the signed file over HTTP
Add an HTTP Request node. The Get Signing Request output has more than one URL in it, and the one labeled the original document is the unsigned version. What you want is the final downloaded URL, the signed file with signatures, completion data, and certificate attached. Drag that field into the HTTP Request node and execute the step. n8n pulls the file down as binary data, ready for the last node.
4. Upload to Google Drive
Add a Google Drive node set to Upload a file, and connect your Drive account. The file name field takes either a fixed value or an n8n expression, so you can build a dynamic name from fields earlier in the workflow, like the signer's name or the document title, instead of a generic filename. Pick the destination folder and you're done.
Common gotchas
Use a workspace-scoped API key, not the account-level one. The account key can create and delete workspaces, which is more access than an automation like this needs.
Grab the signing request ID, not the ID of the webhook delivery that triggered the workflow. They sit next to each other in the trigger's output.
Download the final document URL, not the original document URL. The original is unsigned.
The webhook secret goes both ways. Firma.dev generates it when you create the webhook, and it has to be pasted into the n8n credential before the trigger will validate incoming requests.
Beyond Google Drive
Saving to Drive is one option out of many once a signing request completes. The same trigger can email recipients, post a notification, write a row to a database, or feed into a larger workflow chained together in n8n, so your team always receives the finished document without anyone checking for it manually. Swap the last node for whatever the workflow actually needs, the first three steps stay the same.
If this is your first time connecting Firma.dev to n8n, the n8n integration guide covers sending and reacting to signing requests more broadly, this post is the deep dive on one specific destination. For the full operation list and the AI-agent-tool method for natural-language control, see the n8n integration docs. Firma.dev also supports Zapier if that fits the stack better, and workspace-scoped webhooks work the same way outside of n8n entirely.
Get 50 free envelopes: Firma.dev customers coming from n8n can sign up with code N8N-FIRMA26 already applied for 50 envelopes free on their first purchase, or enter the code manually at purchase if they already have an account. Offer expires October 1, 2026.
Get started with Firma.dev for free, no credit card required.
Related articles
Our platform is designed to empower businesses of all sizes to work smarter and achieve their goals with confidence.
