Description

@turbodocx/n8n-nodes-turbodocx

Automate TurboDocx API and TurboSign digital signatures in your n8n workflows. Send signature requests, track document status, and download signed PDFs—all without writing code.

n8n is a fair-code licensed workflow automation platform.

Why This Node?

🚀 Zero-Code Signature Automation – Build complete document signing workflows with drag-and-drop simplicity. No API knowledge required.

✍️ Full TurboSign Integration – Access all TurboSign capabilities: prepare documents for review, send signature requests, track status, download signed PDFs, void requests, and resend emails.

⚡ Lightning Fast – Pure TypeScript implementation with zero runtime dependencies. Built for n8n Cloud compatibility and instant deployment.

🔄 Production Ready – Built with n8n's best practices, comprehensive error handling, and full TypeScript support for reliable automation.

🛠️ Developer Friendly – Clean API design, comprehensive documentation, and detailed examples to get you automating in minutes.

Installation

n8n Cloud (Pending Community Node Verification)

1. In your n8n instance, go to Settings → Community Nodes
2. Click Install and enter: @turbodocx/n8n-nodes-turbodocx
3. Click Install to add the node to your instance

Self-Hosted n8n

Follow the installation guide in the n8n community nodes documentation.

# From your n8n installation directory
npm install @turbodocx/n8n-nodes-turbodocx
# Restart n8n

Credentials Setup

Getting Your API Key

1. Sign up for a TurboDocx account at https://turbodocx.com
2. Log in to your TurboDocx dashboard
3. Navigate to your account settings or API section
4. Generate an API key
5. Copy the API key

Adding to n8n

1. In n8n, create a new TurboDocx API credential
2. Paste your API key
3. Set the Base URL: https://api.turbodocx.com (default)
4. Save the credential

Operations

TurboSign

Supported File Types: PDF, DOCX, PPTX, or URLs to hosted files (S3, Google Drive, etc.)

Usage Examples

Simple Contract Signing Workflow

[Webhook Trigger] → [HTTP Request: Get Document] → [TurboDocx: Prepare for Signing] → [Slack: Notify Team]

Step-by-step:

1. Add a Webhook node to receive contract data
2. Add HTTP Request node to download document from your storage (supports PDF, DOCX, PPTX)
3. Add TurboDocx node with operation TurboSign: Prepare for Signing
   • File: Select binary data from previous node (or provide URL to hosted file)
   • Recipients:

     [
       {"name":"{{$json.customerName}}","email":"{{$json.customerEmail}}","order":1},
       {"name":"Company Rep","email":"legal@company.com","order":2}
     ]
     

   • Fields:

     [
       {"type":"signature","page":1,"x":100,"y":500,"width":200,"height":50,"recipientOrder":1},
       {"type":"date","page":1,"x":320,"y":500,"width":100,"height":30,"recipientOrder":1},
       {"type":"signature","page":1,"x":100,"y":600,"width":200,"height":50,"recipientOrder":2},
       {"type":"date","page":1,"x":320,"y":600,"width":100,"height":30,"recipientOrder":2}
     ]
     

4. Add Slack node to notify team when sent

Auto-Download Completed Contracts

[Schedule Trigger] → [TurboDocx: Get Status] → [IF: Status=Completed] → [TurboDocx: Download] → [Google Drive: Upload]

Step-by-step:

1. Schedule: Run every hour
2. TurboDocx: Get Status: Check document {{$json.documentId}}
3. IF: Only continue if status is "completed"
4. TurboDocx: Download: Get signed PDF
5. Google Drive: Upload to contracts folder

Reminder System for Pending Signatures

[Schedule Trigger] → [TurboDocx: Get Status] → [IF: Pending > 3 Days] → [TurboDocx: Resend Email]

Document Generation + Signature Flow

[Webhook] → [TurboDocx: Generate Document] → [TurboSign: Prepare for Signing] → [Email: Notify Sender]

Step-by-step:

1. Webhook: Receive customer data and contract details
2. TurboDocx: Generate Document: Create personalized contract from template
   • Returns deliverableId in output
3. TurboSign: Prepare for Signing:
   • File Input Method: Select "Deliverable"
   • Deliverable ID: {{$json.deliverableId}} (from previous TurboDocx node)
   • Recipients:

     [
       {"name":"{{$json.customerName}}","email":"{{$json.customerEmail}}","order":1},
       {"name":"Sales Rep","email":"sales@company.com","order":2}
     ]
     

   • Fields: Use template anchors or coordinates
4. Email: Notify sender that signature request was sent

Why use this workflow: Seamlessly generate personalized documents and send them for signature in one automation. The deliverable ID links the generated document directly to the signature request.

Field Placement Methods

TurboSign supports two methods for placing signature fields on documents:

Method 1: Coordinate-Based (Absolute Positioning)

Example:

{
  "type": "signature",
  "page": 1,
  "x": 100,
  "y": 500,
  "width": 200,
  "height": 50,
  "recipientOrder": 1
}

Best for: Documents with consistent layouts where you know exact field positions.

Method 2: Template Anchor-Based (Dynamic Positioning)

Placement Options:

Example:

{
  "type": "signature",
  "recipientOrder": 1,
  "template": {
    "anchor": "{client_sig}",
    "placement": "replace",
    "width": 180,
    "height": 50
  }
}

Complete Template Anchor Example:

Document with anchors:

Client Signature: {client_sig}    Date: {client_date}
Company Rep: {company_sig}        Date: {company_date}

Fields configuration:

[
  {"type": "signature", "recipientOrder": 1, "template": {"anchor": "{client_sig}", "placement": "replace", "width": 180, "height": 50}},
  {"type": "date", "recipientOrder": 1, "template": {"anchor": "{client_date}", "placement": "replace", "width": 100, "height": 30}},
  {"type": "signature", "recipientOrder": 2, "template": {"anchor": "{company_sig}", "placement": "replace", "width": 180, "height": 50}},
  {"type": "date", "recipientOrder": 2, "template": {"anchor": "{company_date}", "placement": "replace", "width": 100, "height": 30}}
]

Best for: Document templates with variable content where exact positions may shift.

Field Types Reference

Recipients Reference

[
  {
    "name": "John Doe",
    "email": "john@example.com",
    "order": 1
  },
  {
    "name": "Jane Smith",
    "email": "jane@example.com",
    "order": 2
  }
]

Signing Order:

• Recipients sign in order (order 1, then order 2, etc.)
• Use the same order number for parallel signing (both can sign at the same time)

File Input Methods

TurboSign supports 4 different ways to provide documents for signature requests:

Supported File Formats

Common Workflow Patterns

Generate + Sign:

[TurboDocx: Generate] → [TurboSign: Prepare for Signing with Deliverable ID]

Download + Sign:

[HTTP Request: Get File] → [TurboSign: Prepare for Signing with Binary Upload]

Cloud Storage + Sign:

[TurboSign: Prepare for Signing with File URL from S3/Drive/Dropbox]

Compatibility

• n8n 1.60.0 or later
• Compatible with n8n Cloud (zero runtime dependencies)
• Works with self-hosted n8n instances

Resources

• n8n community nodes documentation
• TurboDocx Website
• TurboDocx Documentation

Contributing

Pull requests are welcome! For major changes, please open an issue first to discuss what you would like to change.

Support

Proudly Built by TurboDocx

For issues or questions:

• GitHub Issues: https://github.com/turbodocx/n8n-nodes-turbodocx/issues
• Discord: Join our community

Related Packages

License

MIT