Sections10
Reading time8 min
EvidenceWorking integration

/api/webhooks, POST /api/v1/infer

Build an n8n document extraction workflow without moving the automation layer to a hosted platform. An HTTP Request node submits files with a scoped API key. A Webhook node receives the signed extraction.completed event, and your own n8n instance decides where the reviewed data goes next.

What runs on your n8n instance

  • Some teams keep automation inside their own infrastructure for data-residency or policy reasons. A cloud workflow tool is off the table.
  • A connector that only exists as a hosted app cannot be wired into a self-hosted node graph.
  • Data that leaves the network just to be re-routed is a privacy and latency problem no one asked for.
  • Self-hosting only helps when the connected service exposes documented webhooks and API calls that the workflow can use.

How the n8n connection works

Dynamite Docs logoDynamite Docs
The handoff
Source table: Your n8n workflowExpose an n8n Webhook node. Register it as a Dynamite Docs webhook. Build the workflow. Call the API from n8n. Illustrative example, not extracted customer data.A REVIEWED DOCUMENT, CONNECTED TO YOUR WORKSOURCE DOCUMENTSource tableTriggerextraction.completed …Payloadcolumns, rows,…Dynamite Docsn8nDestinationReview before delivery
  1. 01Expose an n8n Webhook node
  2. 02Register it as a Dynamite Docs webhook
  3. 03Build the workflow
  4. 04Call the API from n8n
Route reviewed data through your nodes. Illustrative example.
01

Expose an n8n Webhook node

In your n8n instance, add a Webhook node (POST) and note its public URL. If the instance is not publicly reachable, expose the webhook via a tunnel or reverse proxy.

02

Register it as a Dynamite Docs webhook

Add that URL as a webhook endpoint in Dynamite Docs. The endpoint must pass the public-URL SSRF guard, and payloads arrive signed with HMAC-SHA256.

03

Build the workflow

n8n parses the payload, columns, rows, metadata, and confidence, and you wire the next nodes, a database write or a file move.

04

Call the API from n8n

For the IN direction, an HTTP Request node POSTs a file to /api/v1/infer with a scoped key and the workflow consumes the structured response.

n8n nodes and delivery behavior

Dynamite Docs logoDynamite Docs
Inside the output
Source table: Your n8n workflowTrigger: extraction.completed → Webhook node. Payload: columns, rows, metadata, confidence. Signature: HMAC-SHA256 (X-Dynamite-Signature). Illustrative example, not extracted customer data.Extracted fieldsDOCUMENT SCHEMAtriggerextraction.completed → Webhook…payloadcolumns, rows, metadata,…signatureHMAC-SHA256…Your n8n workflowDESTINATION FIELDSTriggerMap to your destination schemaPayloadMap to your destination schemaSignatureMap to your destination schemaIllustrative mapping. Confirm the field names accepted by your destination.
Trigger
extraction.completed → Webhook node
Payload
columns, rows, metadata, confidence
Signature
HMAC-SHA256 (X-Dynamite-Signature)
Route reviewed data through your nodes. Illustrative example.

The self-hosted workflow uses these inputs and checks:

Triggerextraction.completed → Webhook node
Payloadcolumns, rows, metadata, confidence
SignatureHMAC-SHA256 (X-Dynamite-Signature)
Send documents inPOST /api/v1/infer with a key
Runsinside your n8n instance
Retriesbackoff + jitter, up to 3 attempts

A realistic example

An audit-evidence workflow in self-hosted n8n:

StepNodeWhat happens
TriggerWebhook (POST)Receives extraction.completed from Dynamite Docs
FilterIF nodeKeeps documents above the confidence threshold
StorePostgres insertWrites rows into the internal evidence table
ArchiveFile moveCopies the source file to the archive share

What the n8n connection does and does not

Does

  • Triggers a Webhook node in your n8n instance with a signed extraction.completed payload.
  • Lets n8n POST documents into /api/v1/infer with a scoped key and consume the structured table.
  • Retries transient delivery failures so a temporary n8n outage does not drop an event.

Does not

  • Does not require a private n8n node or n8n-specific credentials. It uses the public webhook and REST API.
  • Does not POST to internal or loopback addresses. Endpoints must be public HTTPS URLs.
  • Does not exempt automation from the same page caps and monthly allowance as interactive use.

Why n8n needs no separate app

n8n uses the same public webhook and REST API as every other connector.

Self-hosted automation keeps the workflow inside your infrastructure while extraction stays a signed, verified input.

The same routes remain signed, retried, subject to plan limits and documented on their own pages.

Setup and delivery questions

Extraction guides

Related integrations

Document workflows it feeds

From the blog

Keep the pipeline in your infrastructure.

Register the webhook, build the workflow in your own n8n, and let signed extraction events drive it.

Can we save optional cookies?

Essential cookies keep you signed in. With your permission, optional analytics cookies and masked session replays help us understand usage and diagnose errors. Privacy policy. Change your choice anytime in Cookie settings.