Package Information
Available Nodes
Documentation generating…
Documentation
Inkly for n8n
Automate your eSignature and document signing workflows in n8n.
Website · Sign up · API docs · Pricing
Inkly lets you send, track, and manage documents for eSignature. This package adds two nodes to n8n:
- Inkly sends a document for signature from one of your templates, or prepares a draft for you to check and send.
- Inkly Trigger starts a workflow when a document is sent, when a signer signs, or when everyone has signed. Completed documents come with the signed PDF and the values signers filled in.
Send the contract when a deal is won in your CRM. Save every signed PDF to Google Drive or Dropbox. Post in Slack when an NDA comes back signed. Add a row to a sheet with the values a client filled in.
Installation
Follow the community nodes installation guide and install n8n-nodes-inkly.
Credentials
The nodes connect with an Inkly API key. API keys are available on Inkly's Pro and Teams plans.
- In Inkly, open Account → API and create a key.
- Choose Read and send to send documents or create drafts from n8n.
- Choose Read if you only use the trigger.
- In n8n, create an Inkly API credential and paste the key.
n8n checks the key when you save the credential.
Operations
Inkly
| Operation | What it does |
|---|---|
| Send From Template | Sends a document for signature from a template. Choose the template, then fill in an email (and optionally a name) for each signer and a value for each prefilled field. |
| Create Draft From Template | Prepares the same document without sending it. The output includes a link to review and send it in Inkly. |
Unique ID. Send From Template has an optional Unique ID, such as a deal ID or spreadsheet row ID. If the step runs again with the same value, Inkly returns the first document instead of sending a second one, and the value is saved as the document's External ID. Leave it empty and every run sends a new document.
The node also works as a tool for n8n's AI Agent.
Inkly Trigger
| Event | Starts the workflow when |
|---|---|
| Document Completed | Everyone has signed. The output includes the field values and, by default, the signed PDF as binary data (data), ready for a Google Drive, Dropbox, or email node. |
| Document Sent | A document is sent for signature. |
| Signer Signed | One signer signs, even if others still need to sign. The output names the signer. |
The trigger registers its webhook with Inkly when you activate the workflow, and removes it when you deactivate it. Inkly signs every event and the node checks the signature. The node also re-reads the document with your key before starting the workflow.
The output is the full document: its title, status, recipients and their status, External ID, and timestamps.
Compatibility
Built and tested with n8n 2.x. Requires Node.js 22 or later.
Self-hosted n8n: Inkly delivers events only to public https:// addresses on port 443. If your instance runs on plain HTTP or a bare IP address, set n8n's WEBHOOK_URL to a public HTTPS address before you activate a workflow with the trigger. The action node works anywhere.
Usage notes
- Each send counts toward your workspace's monthly API allowance, the same as any API send.
- Events can arrive more than once and out of order. Use the
event_idfield if a later step must run only once per event. - n8n keeps execution history, which includes recipient names and emails and, for completed documents, the values signers filled in.
Resources
Support
Email hello@inkly.so or open an issue.
