eSignatures in your n8n workflows.

Send a contract the moment a deal closes, and file the signed PDF the moment the last person signs. Inkly's verified n8n node does both, from the templates you already use.

  • Verified node on n8n
  • Sends from your Inkly templates
  • Signed PDF ready for your next step

Send from any workflow. Start one the moment it's signed.

Send a document from any workflow.

Pick a template and its fields are already placed. Map each signer's email and any prefilled values from earlier steps.

  • A Unique ID sends once, even if a run repeats
  • Automatic Reminders on days 3, 6, and 10
  • Or Create Draft From Template to check it first
See how templates work
The Inkly node set to Send From Template with the Consulting agreement template. The client's email, name, and project fee come from the CRM step before it, the deal ID is the Unique ID, and automatic reminders are on.

Start a workflow the moment it's signed.

Document Sent, Signer Signed, and Document Completed each carry the document's status, signers, and your Unique ID.

  • The signed PDF, attached as a file
  • Every value signers filled in
  • Ready for a sheet, CRM, or Drive step
Read the setup guide
The Inkly Trigger's output for Document Completed: the document's status, external ID, signers, and the values they filled in, with the signed PDF attached as a file named data.

Connect Inkly to n8n in three quick steps.

  1. 1Create an API key in Inkly, under Account, API. Read and send lets the node send.

  2. 2Search for Inkly in n8n's nodes panel. On self-hosted n8n, install n8n-nodes-inkly first.

  3. 3Paste the key into a new Inkly API credential. n8n checks it when you save.

The step-by-step guide walks through a first workflow, and Inkly's listing on n8n has the node's details.

Questions about n8n and Inkly.

Plans, hosting, duplicates, and what n8n keeps.

See the full plan breakdown →

Send your first document
from n8n.

Create an API key, add the Inkly node, and send from a template you already use.