Skip to main content

Use Doqlo with n8n

Use this page to understand how Doqlo works with n8n today, what you need before you automate Bulk Fill exports, and which starter workflow to import first.

Support scope for this integration

This page provides implementation guidance and starter workflow patterns for using Doqlo with n8n. Doqlo supports its own API behavior, authentication, and documented product functionality. Doqlo does not provide hands-on workflow setup or end-to-end debugging inside your n8n environment. If you suspect a Doqlo API issue or product defect, contact support with the relevant job_id, request_id, and error details.

Current Availability​

Doqlo does not currently provide a native verified n8n node. The supported path today is through standard n8n workflow nodes.

That means you can use Doqlo with n8n now through HTTP Request based workflows, downloadable starter workflow JSON, and the existing Bulk Fill Public API. This page does not announce a native node launch.

What This Integration Is​

n8n is the workflow layer around Doqlo's Bulk Fill export-job API.

Doqlo still handles:

  • template and layout setup
  • field placement and mapping
  • .doqlo package export from the web editor

n8n handles:

  • running the export job
  • checking whether the job is complete
  • downloading the completed export
  • sending the result into your next workflow step

What You Need Before Using It​

Before you use the starter workflows, make sure you have:

  • a Doqlo account with Bulk Fill API access
  • a BF export API key
  • a source PDF
  • a .doqlo package exported from the Doqlo Bulk Fill web editor
  • either row data or a CSV file
  • an n8n account or instance

The starter workflows assume the source PDF and .doqlo package are available through reachable file URLs so you can import and test the workflow quickly. If your files already come from earlier n8n steps, replace the helper download nodes with those upstream binary inputs instead.

What It Can Do Today​

Today the n8n workflows use the same three actions already supported by the Bulk Fill Public API:

  • Create Export Job
  • Get Export Job
  • Download Completed Export

This keeps document authoring in Doqlo and workflow execution in n8n.

Download Starter Workflows​

Import one of these starter workflows into n8n:

Start with row-data-export.json first. It is the canonical walkthrough for this page.

How The Canonical Workflow Works​

The canonical starter workflow centers on these nodes, in this exact order:

  1. Manual Trigger
  2. Set Example Row Data
  3. Create Export Job
  4. Wait Before Poll
  5. Get Export Job
  6. Is Job Completed?
  7. Is Job Failed?
  8. Download Completed Export
  9. Output Ready
  10. Check Later

The imported workflow also includes helper nodes such as Download Source PDF, Download Doqlo Package, Merge Job Inputs, Prepare Poll Attempts, and Loop Over Poll Attempts so the canonical path above can run without manual rewiring.

In practical terms:

  1. Manual Trigger starts a test run from the n8n canvas.
  2. Set Example Row Data stores the placeholder values you replace first: Doqlo API base URL, BF export API key, source PDF URL, .doqlo URL, rows_json, and export options.
  3. Create Export Job sends the PDF, .doqlo package, row data, and export options to Doqlo.
  4. Wait Before Poll pauses for 10 seconds between status checks.
  5. Get Export Job re-reads the current job state by job_id.
  6. Is Job Completed? checks for completed.
  7. Is Job Failed? checks for failed.
  8. Download Completed Export retrieves the ZIP when the job is ready.
  9. Output Ready leaves the downloaded file in the export_file binary field for your next n8n step.
  10. Check Later stops after 12 attempts and gives you a clear handoff if the job is still running.

The default polling pattern is intentionally conservative:

  • poll only after queued or processing
  • wait 10 seconds between checks
  • stop after 12 attempts
  • route to Check Later instead of polling forever

The starter workflows generate example Idempotency-Key values automatically so you can run a quick manual test. In production, replace that pattern with a stable key for one logical create request and reuse it only when retrying that same request.

Starter Workflows​

Row Data Export​

Use row-data-export.json when your workflow already has structured row data and you want the shortest path to a first successful n8n import.

CSV File Export​

Use csv-file-export.json when your workflow should download a CSV file and submit it directly into Doqlo instead of building rows_json.

Failure Handling​

Use failure-handling.json when you want a starter pattern that keeps Doqlo error details visible in n8n. This workflow is designed to preserve response details such as error code, message, and structured error payload instead of dropping them.

To exercise Doqlo's error response rather than a helper download failure, replace invalid_doqlo_url with a reachable but intentionally invalid .doqlo file.

Downstream File Handling​

Use downstream-file-handling.json when you want to pass the downloaded export to a generic downstream HTTP step after Doqlo completes.

Typical Workflow Shapes​

  • structured row data -> Doqlo export -> generic downstream handling
  • form submission -> Doqlo export -> send or store the finished output
  • CSV file -> Doqlo export -> retrieve the completed ZIP
  • Doqlo export -> preserve failure details -> route to manual follow-up

Current Limitations​

  • Doqlo does not currently provide a native verified n8n node.
  • The supported path today is through standard n8n workflow nodes.
  • The starter workflows expect a .doqlo package that already exists.
  • The starter workflows assume reachable file URLs for the source PDF and .doqlo package unless you replace the helper download nodes.
  • You still need to provide row data or a CSV file for execution.
  • Longer-running jobs may need webhook-based handling or a later manual check instead of indefinite polling inside one imported starter workflow.
  • Very large outputs may require extra care in whatever downstream step receives the ZIP.

How To Get Started​

If you are starting fresh, begin with n8n Cloud. It is the preferred starting path for these starter workflows.

Self-hosted n8n is also possible for advanced users, but this page does not treat self-hosting as the default onboarding path.

Recommended order:

  1. Start with n8n Cloud.
  2. Import row-data-export.json.
  3. Replace the placeholder values in Set Example Row Data.
  4. Run one test export.
  5. If you need CSV input, error capture, or downstream delivery, import one of the other starter workflows and adapt from there.