SignDocs Brasil Community Node — ICP-Brasil A1/A3, biometric, OTP, and clickwrap signatures (MP 2.200-2)

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 Like

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!