This is the express version of our earlier n8n and Pipedrive guide. The automation stays the same: a deal moves into a chosen stage, n8n looks up the contact in Pipedrive, and Firma.dev sends a signing request from a saved template. What changes is the setup. You import a finsihed workflow file and adjust a few values, which takes minutes where building each node by hand takes roughly twenty.
Firma.dev costs €0.049 per envelope (~5¢ USD) with no per-seat fees and no monthly minimums, so you pay only when a document actually goes out. A CRM trigger like this stays cheap even when every deal that reaches the stage gets an agreement... and nobody on the sales team has to remember to send it.
Download the workflow template
Import it into n8n, then connect your Pipedrive account, swap in your stage IDs, template ID and workspace API key.
If you would rather see every node built from scratch, the original walkthrough covers that.
Prerequisites
A Pipedrive account you can connect to n8n
An n8n instance, cloud or self-hosted
A Firma.dev account and a workspace API key (Workspace Settings, then API)
A signing template already built in your Firma.dev workspace
Import the template
In n8n, click Create Workflow, choose Import from File, and select the JSON template you downloaded above. n8n loads a four-node automation: a Pipedrive trigger that fires when a deal is updated, a filter that checks whether the deal moved into the right stage, a Get Contact Person lookup for the signer's details, and the Firma.dev node that sends the agreement. Each of the four needs a small amount of customizing, covered next.
Customize the four nodes
1. Pipedrive trigger
Open the trigger node and connect your Pipedrive account. Leave everything else as it is. Click Execute Step so n8n starts listening, then move a test deal between stages in Pipedrive. The deal's data lands in n8n and shows the stage IDs on both sides of the move. In the video the deal went from stage 12 to stage 13, and 13 was the target, the Intro Booked stage.
2. Stage filter
Your pipeline will have different stage numbers, so change the values in the filter to match the IDs you just read off the trigger's output. Execute the step and it should evaluate to true for the move you made.
3. Get Contact Person
Execute this node to confirm it returns the email and name of the person attached to the deal. Those two values feed the signing request, so check them here before moving on.
4. Firma.dev send step
If the Firma.dev node is not installed in your n8n instance yet, n8n offers to install it, and the n8n integration guide lists the community node package (n8n-nodes-firma) if you prefer to add it from Settings. It takes one click.
The node needs a template ID. Log in to your Firma.dev dashboard, choose your workspace, and open the template you want to send. The template ID sits in the page URL, which makes that the quickest place to copy it from. Paste it into the Template ID field. The signing request title and other fields are optional to change.
When you connect the node you also add an API key. Use your workspace API key rather than the global one. Both work, but a workspace key is scoped to that single workspace, which keeps the credential limited to this one workflow.
Test the whole workflow
Execute the Firma.dev step on its own first. Once it succeeds, run the full workflow with Execute Workflow and move a deal into the target stage again. Every node should reoslve to green, and the signing request goes out to the contact on the deal.
Common gotchas
Stage IDs belong to your pipeline. Read them off the trigger's output after moving a test deal, and update the filter to match.
Test each node individually. n8n's built-in AI assistant resolves most connection errors on its own when a single step fails, so catching the failure at the node level is faster than debugging the whole run.
Use a workspace-scoped API key. It limits what the credential can reach.
Copy the template ID from the URL. It is the most reliable source, since the ID is right there when the template is open.
Where to go from here
The same workflow handles other stages by pointing a copy at a different stage ID and a different template, so "Contract Ready" and "Renewal" can each send their own agreement from one pipeline. To react after the agreement is signed, the Google Drive guide shows a second workflow that listens for the completed signing request and saves the document automatically... and the general n8n integration guide covers the full set of triggers and actions in the Firma.dev node. Firma.dev also supports Customer Workspaces if you want each client's signing activity separated.
Get started with Firma.dev for free, no credit card required.
Artigos relacionados
A nossa plataforma foi projetada para capacitar empresas de todos os tamanhos a trabalhar de forma mais inteligente e alcançar seus objetivos com confiança.
