Back to Nodes

DocupletionForms

Last updated Aug 6, 2026

n8n community node for DocupletionForms — conditional logic forms with automated PDF document generation

104 Weekly Downloads
1,107 Monthly Downloads

Included Nodes

DocupletionForms
DocupletionForms Trigger

Description

n8n-nodes-docupletionforms

This repo contains DocupletionForms‘ community node for n8n — conditional logic forms with automated PDF document generation.

Installation

Follow the installation guide in the n8n community nodes documentation, and search for DocupletionForms.

Credentials

You need a DocupletionForms account and a user API key to use this node.

1. Log in to your DocupletionForms account and go to Manage Account > API to find (or generate) your access token.
2. Note your Tenant ID — the numeric organization ID shown in the app URL or on the Manage Account page. Every DocupletionForms API call is scoped to a single tenant, so this is required alongside the API key.
3. In n8n, create a new DocupletionForms API credential and fill in:
API Key — your access token from step 1.
Tenant ID — your organization ID from step 2.
Base URL — defaults to https://app.docupletionforms.com/api; only change this if you’re pointed at a different DocupletionForms deployment.
4. Save the credential — n8n tests the connection immediately and confirms it’s working before you can use it in a workflow.

!Add Credentials

Usage

Add a DocupletionForms node to a workflow, pick a resource and operation, then pick a form or document set from the searchable list (or paste an ID directly).

!Node parameters

Picking a form or document set opens a searchable list pulled live from your DocupletionForms account:

!Choose a form

Form Submission

  • Submit Form — submits field values and returns a link the respondent can use to come back and edit their answers later.
  • Generate Prefilled Link — builds a link to the public form with fields pre-populated; nothing is saved until the respondent submits it themselves.
  • List Submissions — lists a form’s submissions, newest first, with an optional simplified output.
  • Merged Document

  • List Document Sets — lists the PDF template groupings configured across your forms.
  • List Merged Documents — lists every submission that has generated a merged PDF for a document set, with a download URL per file.
  • Download Merged Document — downloads one merged PDF as binary data, ready to attach to an email or upload elsewhere.
  • There’s also a DocupletionForms Trigger node, with two events:

  • Form Submitted — fires on every new submission received for a chosen form.
  • Document Merged — fires when a submission is merged into a PDF for a chosen document set (the pre-existing behavior, kept as the default for backward compatibility).
  • The DocupletionForms node itself can be added as an AI Agent tool — n8n does this automatically for any node marked usableAsTool, so the same resources/operations above (submit forms, generate prefill links, look up submissions/documents) are available to an agent without a separate tool-specific node.

    Fill in the field values and hit Execute step to try it:

    !Filled-in node parameters

    !Execution result

    Example workflows

  • Deliver a generated document automatically: List Merged Documents (to find a submission’s templateid) → Download Merged Document (same document set, that templateid + submission_id) → attach the resulting binary to an email/Slack message.
  • Sync new submissions to a spreadsheet or CRM: DocupletionForms Trigger (Form Submitted) → whatever node writes the data out, instead of polling with List Submissions.
  • Trigger downstream work when a document is ready: DocupletionForms Trigger (Document Merged) → process the delivered file URL / submission payload in the next nodes.

API Resources / Operations

This node covers form submission, prefill links, submission listing, and merged-document generation/delivery — the endpoints most workflows need to act on form activity. It doesn’t cover DocupletionForms’ form-building API (creating/editing forms, field mapping, conditional rules) — that side is intentionally MCP/AI-drafting-only on the DocupletionForms backend, with a human always publishing the result in the app.

If there’s an operation you need that isn’t here, please open an issue in this repo.

Related Resources

The full endpoint-by-endpoint reference (paths, request/response shapes, auth details) is in docs/API.md.

DocupletionForms: https://docupletionforms.com

Development

See CONTRIBUTING.md for running this node locally against a DocupletionForms backend and publishing releases.

License

MIT