Menu
Get API Key

eSignature API + n8n Integration

Use eSignature API in your n8n workflows — self-hosted or cloud. Generate documents and collect signatures as part of your existing automation, with full control over your data.

What you can automate with n8n

  • Trigger document generation and signing from any n8n-connected service — databases, webhooks, CRMs, or scheduled runs
  • Build complex multi-branch workflows where different document types are generated and sent for signing based on conditional logic
  • Use n8n's self-hosted option to keep all document data within your own infrastructure, while eSignature API handles the signing layer
  • Catch signing completion webhooks in n8n and trigger downstream actions — update a database, post to an internal tool, or archive the signed PDF
  • Chain document generation, signing, and post-signature processing in a single n8n workflow

How to set it up

1

Add an HTTP Request node

Use n8n's HTTP Request node to call the CraftMyPDF REST API. Set your API key in the Authorization header and configure the request body with your template ID, data, and recipient details.

2

Configure signing parameters

In the request body, set e-signature parameters — signer name, email, role, field positions, signing order, and expiry. The same API call generates the PDF and sends it for signing.

3

Handle the webhook response

Add a Webhook node to your workflow to catch the signing completion event. Use the payload data to update records, trigger notifications, or pass the signed PDF URL to the next node.

Common questions

Does eSignature API work with self-hosted n8n?
Yes. eSignature API is a standard HTTPS REST API. It works with any n8n instance — self-hosted or cloud — as long as the instance can make outbound HTTPS requests to the CraftMyPDF API endpoint.
Is there a native CraftMyPDF node in n8n?
CraftMyPDF has an n8n integration. Check the n8n community nodes or support.craftmypdf.com for the current setup guide and whether a native node is available.
How do I keep signed documents within my infrastructure?
Configure the API to return the signed PDF directly (using export_type: file) rather than storing it on CraftMyPDF's servers. The signed PDF binary is returned in the API response, which you can then store in your own S3 bucket or database from within your n8n workflow.

Back to all integrations

Add e-signatures to your n8n workflows today

Free plan. 50 documents per month. No credit card.

Get API Key Free