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.

🚀 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.

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

Follow the installation guide in the n8n community nodes documentation.

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

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

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

Reminder & Expiration Schedule: Prepare for Signing and Prepare for Review both accept an optional Reminder & Expiration Schedule — the automatic reminder cadence (delay, interval, and cap) and document expiration (expire-after plus warning cadence), set per document at send time. Leave any field out to inherit your organization's defaults. Matches the schedule options in the TurboDocx SDK.

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

Generate documents from TurboDocx templates with variable substitution, then list, fetch, update, delete, or download them (PDF or original DOCX/PPTX source).

Full CPQ surface, modelled as several resources for an intuitive UX:

Reminder & Expiration Schedule (quote Send / Send With Deliverable / Create and Send): these send operations accept an optional Reminder & Expiration Schedule — the automatic reminder cadence (delay, interval, cap) plus per-quote expiration and its warning cadence. Leave any field out to inherit your organization's defaults. Quote constraint: expiry is pinned to the quote's Valid Until (so Expire After is ignored while expiration is on), and the reminder/warning cadence must fit inside Valid Until or the send is rejected.

Provision and manage customer organizations from a partner account — including each tenant's TurboSign display preferences, so signature appearance can be set per org without logging into its settings UI. Requires the separate "TurboDocx Partner API" credential (a TDXP- partner key + partner ID).

Credentials: TurboSign, Deliverable, TurboQuote, and Webhook resources use the TurboDocx API credential (API key + Organization ID). The TurboPartner resources use the TurboDocx Partner API credential. The node shows the right credential automatically based on the selected resource.

[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

[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

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

[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.

TurboSign supports two methods for placing signature fields on documents:

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.

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.

Any field may carry an optional defaultValue to pre-fill it (max 600 characters). It is a pure passthrough — forwarded verbatim to the backend, which owns validation.

• Date fields fill with the signing date by default. To pin a specific date instead, set defaultValue to that date in MM/DD/YYYY (e.g. "12/31/2026"); omit it (or send "") to keep the signing-date behaviour. The value must be a real calendar date — a non-existent date such as "02/31/2026" is rejected.
• signature and initial fields cannot carry a defaultValue, and a date field cannot be isReadonly.

[
  {"recipientEmail": "client@example.com", "type": "date", "template": {"anchor": "{effective_date}", "placement": "replace", "width": 120, "height": 20}, "defaultValue": "12/31/2026"}
]

Any field may carry an optional metadata object that turns a checkbox into a controller for one or more dependent fields. When the checkbox's state matches the rule, the dependent field is shown (or unlocked) to the signer. This is a pure passthrough — the metadata object is forwarded verbatim to the backend, which owns the behaviour.

On the controlling checkbox — give it a stable fieldKey so dependents can reference it:

The controlling field must be type: "checkbox".

On a dependent field — add a conditional rule that points at the checkbox's fieldKey:

Notes:

• The node validates the shape of each rule (operator, action, and a non-empty controllingFieldKey) and fails fast with a clear error before sending — matching the backend's 400. A controllingFieldKey that names no existing checkbox (a dangling reference) is allowed: the backend fails open by design and simply ignores the rule.
• metadata is entirely optional. Fields without it behave exactly as before.

Worked example — a checkbox controls a text field (is_checked → show):

The "Other reason" text field stays hidden until the signer checks the "I have a different reason" box.

[
  {
    "recipientEmail": "client@example.com",
    "type": "checkbox",
    "template": {
      "anchor": "{OtherReasonToggle}",
      "placement": "replace",
      "size": { "width": 20, "height": 20 }
    },
    "metadata": { "fieldKey": "other_reason_toggle" }
  },
  {
    "recipientEmail": "client@example.com",
    "type": "text",
    "template": {
      "anchor": "{OtherReason}",
      "placement": "replace",
      "size": { "width": 240, "height": 30 }
    },
    "metadata": {
      "conditional": {
        "controllingFieldKey": "other_reason_toggle",
        "operator": "is_checked",
        "action": "show"
      }
    }
  }
]

Full IF/THEN workflow (Prepare for Signing):

{
  "nodes": [
    {
      "parameters": {
        "resource": "turboSign",
        "operation": "prepareForSigning",
        "fileInputMethod": "url",
        "fileLink": "https://my-bucket.s3.amazonaws.com/agreement.pdf",
        "recipients": "[{\"name\":\"Client Name\",\"email\":\"client@example.com\",\"signingOrder\":1}]",
        "fields": "[{\"recipientEmail\":\"client@example.com\",\"type\":\"checkbox\",\"template\":{\"anchor\":\"{OtherReasonToggle}\",\"placement\":\"replace\",\"size\":{\"width\":20,\"height\":20}},\"metadata\":{\"fieldKey\":\"other_reason_toggle\"}},{\"recipientEmail\":\"client@example.com\",\"type\":\"text\",\"template\":{\"anchor\":\"{OtherReason}\",\"placement\":\"replace\",\"size\":{\"width\":240,\"height\":30}},\"metadata\":{\"conditional\":{\"controllingFieldKey\":\"other_reason_toggle\",\"operator\":\"is_checked\",\"action\":\"show\"}}}]",
        "additionalFields": {
          "senderEmail": "sales@yourcompany.com",
          "documentName": "Service Agreement"
        }
      },
      "name": "TurboSign: Send Signature",
      "type": "n8n-nodes-turbodocx.turboDocx",
      "typeVersion": 1,
      "position": [640, 300]
    }
  ]
}

[
  {
    "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)

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

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]

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

• n8n community nodes documentation
• TurboDocx Website
• TurboDocx Documentation

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

Proudly Built by TurboDocx

For issues or questions:

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

MIT