TurboDocxInstall

Summary

Send a signature request for a document via TurboSign by specifying the document source, recipients, and signature fields.

Inputs

• fileInputMethod — Method to provide the document: upload binary file, URL to hosted file, existing TurboDocx deliverable, or TurboDocx template.
• pdfFile — Binary field name containing the document file (PDF, DOCX, PPTX) to upload; required if fileInputMethod is upload.
• fileLink — URL of a hosted document file; required if fileInputMethod is url.
• deliverableId — UUID of existing TurboDocx deliverable to use; required if fileInputMethod is deliverable.
• templateId — UUID of TurboDocx template to convert and use; required if fileInputMethod is template.
• recipients (required) — JSON array specifying recipients with properties like name, email, signing order, and optional metadata (e.g., colors).
• fields (required) — JSON array defining signature or other form fields linked to recipients, including template anchors, placement, size, and optional conditional logic metadata.
• additionalFields.ccEmails — JSON array of emails to be CC'd on the completed document (maximum 10).
• additionalFields.documentDescription — Description text for the signature document.
• additionalFields.documentName — Name for the signature document.
• additionalFields.senderEmail (required) — Sender email address shown as reply-to in emails and used in audit trail; must be provided.
• additionalFields.senderName — Sender name displayed in emails and audit trail; defaults to API key name if omitted.

Output shape

a single JSON object representing the created TurboSign signature request, including details about the sent document and recipients.

The operation requires a valid sender email and complete recipient and fields definitions to succeed. Input document must be provided according to the chosen file input method. The response includes references to the signature transaction for tracking or further workflow actions.

Links

• n8n community nodes installation guide