Back to Nodes

AllSign

Last updated Apr 15, 2026

n8n integration for AllSign β€” Electronic signature, document management, biometric signing. Supports FEA, NOM-151, eIDAS, and WhatsApp delivery.

13 Weekly Downloads
107 Monthly Downloads

Included Nodes

AllSign

Description

n8n-nodes-allsign

!AllSign
!n8n
!License

n8n integration for the AllSign e-signature platform.

Create and send documents for electronic signature directly from your n8n workflows using the AllSign API V2.

✨ Features

πŸ“„ Document β€” Create & Send

Upload a PDF or DOCX (from URL or binary input) and send it for signing in one step, with full control over signature requirements.

πŸ“± Signers: Email & WhatsApp

Signers can be reached via email, WhatsApp, or both. When both channels are provided, the signer verifies their identity through OTP on both channels as part of the signing process.

  • βœ… Email-only signers
  • βœ… WhatsApp-only signers (phone number, no email required)
  • βœ… Both channels β€” dual OTP verification during signing
  • πŸ” 10 Signature Validations

    | Validation | Description |
    | ————————– | ——————————————————————– |
    | AutΓ³grafa | Handwritten digital signature with biometric capture (on by default) |
    | FEA | Advanced Electronic Signature β€” Mexico standard |
    | eIDAS | European Electronic Signature β€” eIDAS compliance |
    | NOM-151 | NOM-151-SCFI certified timestamping (Mexico) |
    | Video Signature | Recorded video of the signer during the signing process |
    | Biometric Selfie | Face comparison against the signer’s government ID |
    | SynthID (AI Detection) | Verifies selfie is from a real person, not AI-generated |
    | ID Scan | Government-issued ID scan (INE, passport, etc.) |
    | Identity Verification | AI-powered ID + selfie verification pipeline |
    | Confirm Name | Signer must type their full name as confirmation |

    πŸ“₯ File Input

  • Binary Input β€” Use a file from a previous node (e.g. Google Drive, HTTP Request, Dropbox)
  • URL β€” Provide a public URL to a PDF or DOCX file (Google Drive and Dropbox links are auto-converted)
  • πŸ“ Signature Field Placement

    Place signature fields precisely on the document:

  • By coordinates β€” X, Y position on a specific page (or all pages)
  • By anchor text β€” Search for text in the PDF and place the field there
  • βš™οΈ Additional Options

    | Option | Description |
    | —————————- | ——————————————————————- |
    | Folder | Organize documents into folders (by name or ID) |
    | Expires At | Set an expiration deadline β€” document auto-expires after this date |
    | Template Variables (DOCX)| Replace {{ variables }} in DOCX templates with dynamic values |
    | Permissions | Set document owner, collaborators, and public read access |
    | Send Invitations | Auto-send or hold for manual sharing |

    πŸš€ Getting Started

    1. Configure Credentials

    1. In n8n, go to Credentials β†’ Add Credential β†’ AllSign API
    2. Enter your API Key β€” get one from dashboard.allsign.io/developers/api-keys
    3. (Optional) Set the Base URL if using a custom environment (default: https://api.allsign.io)
    4. Click Save β€” the connection test validates your key automatically

    2. Use the Node

    1. Add the AllSign node to your workflow
    2. Set the document name and file source (URL or Binary)
    3. Add signers (name + email and/or WhatsApp number)
    4. Toggle the signature validations you need
    5. Execute!

    The signing invitation channel (email or WhatsApp) is auto-detected per signer based on the contact information provided.

    πŸ› οΈ Development

    For contributors and developers who want to modify or extend this node.

    Clone & Install

    git clone https://github.com/AllSign-io/n8n-nodes-allsign.git
    cd n8n-nodes-allsign
    npm install
    

    Scripts

    | Command | Description |
    | ——————— | —————————- |
    | npm run dev | Start n8n with hot reload |
    | npm run build | Compile TypeScript β†’ dist/ |
    | npm run build:watch | Compile in watch mode |
    | npm test | Run unit tests (39 tests) |
    | npm run lint | Check code style |

    Project Structure

    n8n-nodes-allsign/
    β”œβ”€β”€ credentials/
    β”‚   └── AllSignApi.credentials.ts        # API Key + Base URL credential
    β”œβ”€β”€ nodes/
    β”‚   └── Allsign/
    β”‚       β”œβ”€β”€ Allsign.node.ts              # Main node (Create & Send)
    β”‚       β”œβ”€β”€ Allsign.node.json            # Codex metadata & SEO
    β”‚       β”œβ”€β”€ Allsign.node.test.ts         # Unit tests (39 tests)
    β”‚       └── allsign.svg                  # Node icon
    β”œβ”€β”€ examples/
    β”‚   β”œβ”€β”€ NDAAutomationAllSign_Workflow.json  # Example workflow
    β”‚   └── NDATemplateAllSign.docx            # DOCX template with variables
    β”œβ”€β”€ docs/
    β”‚   └── template-portal-description.md   # n8n template portal description
    β”œβ”€β”€ package.json
    β”œβ”€β”€ tsconfig.json
    └── jest.config.js
    

    πŸ› Troubleshooting

    | Problem | Solution |
    | —————————- | —————————————— |
    | Connection test fails | Verify API Key and Base URL in credentials |
    | “Service refused connection” | Check the Base URL matches your backend |
    | TypeScript errors (dev) | Ensure Node.js v22+, run npm install |

    πŸ“š Resources

  • AllSign Platform
  • AllSign API Documentation
  • AllSign API Playground
  • n8n Documentation
  • n8n Community Forum

πŸ“„ License

MIT