Wrapped the SignDocs Brasil API in an n8n community node.
Install: n8n-nodes-signdocs-brasil (available via Settings → Community Nodes).
The node wraps the maintained @signdocs-brasil/api SDK, so auth (OAuth2 client_credentials, optional ES256 private-key JWT), token caching, retries,
webhook HMAC verification, and rate-limit handling come for free.
What’s in v0.1:
- Action node with Signing Session, Envelope (multi-signer), Document, Evidence, Webhook resources — 15 operations total
- Trigger node for TRANSACTION.COMPLETED / STEP.FAILED / etc., with HMAC-SHA256 signature verification and automatic register-on-activate / delete-on-deactivate lifecycle
- Credential test exercises the real
/oauth2/token flow on save, so bad credentials fail loud instead of silent
One convenience worth calling out: the Signing Session Create output includes a derived signingUrl field that already combines the session URL with the?cs=<clientSecret> query param, since the raw url field isn’t usable standalone. Saves a Set node in every workflow.
Code: GitHub - signdocsbrasil/n8n-nodes-signdocs-brasil: Community n8n node for SignDocs Brasil — biometric, OTP, clickwrap, and ICP-Brasil A1/A3 electronic signatures (MP 2.200-2 compliant) · GitHub (MIT)
Happy to hear bug reports, especially from anyone running BR-specific signature flows (CPF/CNPJ, ICP-Brasil certs). Planning to add a Verification resource.
1 curtida
Wow, this is a huge win for the Brazilian community! A dedicated node for digital signatures is a game changer for local compliance. I’m stoked about the news, even though I don’t have a specific use case for it right now. Definitely going to dig around at work to find an excuse to test this out!
@tamy.santos — thanks for the kind words! Perfect timing, because we just shipped two
things that make it a lot easier to find that excuse to test it 
Two updates since launch 
- Starter templates. You no longer have to wire a workflow from scratch — there
are 3 importable templates covering the most common BR flows:
- Contract from a spreadsheet — Google Sheets row → Google Docs → PDF → signing
session → emailed link. Drop-in for HR/legal contract generation.
- Signing link over WhatsApp / Telegram / Email — one webhook, a Switch node routes
the signingUrl to whichever channel you pass. A3 ICP-Brasil certs work here too,
since the signer opens the link on the desktop where the token is plugged in.
- Real-estate pipeline — lead webhook → CRM row → auto-generated proposal → signing
session → delivery, with an optional TRANSACTION.COMPLETED trigger to flip the lead
status when it’s signed. (One thing worth clarifying: SignDocs doesn’t send any
messages itself — our node just creates the session and outputs the signingUrl. The
final delivery step is a regular n8n node. This template defaults to the WhatsApp
Business node because that’s where agents talk to clients, but you can swap it for the
Telegram, Gmail, Twilio SMS, etc. node without touching anything upstream — template #2
above does exactly that, routing the same link to all three by channel.)
Import via Workflows → Import from File. Each one ships with credential placeholders
and your choice of policy profile (CLICK_ONLY, OTP, BIOMETRIC, DIGITAL_CERT, …).
Gallery + direct JSON downloads: Templates n8n para Assinatura Digital — SignDocs Brasil | Workflows Prontos
- Self-service HML (sandbox) credentials. You can now provision your own test
credentials — no more emailing us to get started. Create a free company (PJ / CNPJ)
account, run the plan wizard, open the API Dashboard, and click Ativar credenciais HML
to get your clientId / clientSecret for api-hml.signdocs.com.br. Takes about 3 minutes.
Step-by-step in the quickstart (§1.3): Guia de Início Rápido — SignDocs Brasil API
As always, bug reports on BR-specific flows (CPF/CNPJ, ICP-Brasil certs) are very welcome.
1 curtida
@signdocsbrasil
Is it already taking alphanumeric CNPJs into account?