Sections10
Reading time8 min
EvidenceWorking integration

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

Build Make.com document extraction automation with two parts that already ship: a signed webhook for completed extractions and a scoped REST API for incoming files. A Make HTTP module can submit the PDF. When extraction finishes, the scenario maps the reviewed rows into the app you chose.

What to configure in your Make scenario

  • A document is rarely the end of the process. The data usually has to travel on to a ledger or a colleague. Manual hand-off makes each hop a re-keying session.
  • Building bespoke glue code for every destination is expensive and brittle; the first vendor change breaks the pipeline.
  • Teams without an engineering bench still have real automations to run, but the tooling to run them assumes a developer is available.
  • The hard part is knowing when extraction actually finished and getting the data in a shape the next app can consume.

How the Make.com connection works

Dynamite Docs logoDynamite Docs
The handoff
Supplier invoice: A Make scenarioCreate a Make.com webhook. Register it as a Dynamite Docs webhook. Build the scenario. Send documents in via the API. Illustrative example, not extracted customer data.A REVIEWED DOCUMENT, CONNECTED TO YOUR WORKSOURCE DOCUMENTSupplier invoiceTriggerextraction.completed …Payloadcolumns, rows,…Dynamite DocsMakeDestinationReview before delivery
  1. 01Create a Make.com webhook
  2. 02Register it as a Dynamite Docs webhook
  3. 03Build the scenario
  4. 04Send documents in via the API
Connect the steps in your scenario. Illustrative example.
01

Create a Make.com webhook

In Make.com, add a Webhooks module with an Instant trigger and copy its public endpoint URL. That URL is where Dynamite Docs will POST the extraction.completed event.

02

Register it as a Dynamite Docs webhook

In the Dynamite Docs workspace, create a webhook pointing at the Make URL. The endpoint is SSRF-guarded to public hosts and signed with HMAC-SHA256 so Make can verify the event.

03

Build the scenario

Make receives the payload, columns, rows, metadata, and confidence, and routes it through the scenario: map the fields into a Sheets row or a HubSpot contact.

04

Send documents in via the API

The IN direction uses the public API. A Make HTTP module POSTs a file to /api/v1/infer with a scoped key, and the extracted table comes back in the response for the scenario to use.

Make.com trigger and API calls

Dynamite Docs logoDynamite Docs
Inside the output
Supplier invoice: A Make scenarioTrigger: extraction.completed → Make webhook. Payload: columns, rows, metadata, confidence. Signature: HMAC-SHA256 (X-Dynamite-Signature). Illustrative example, not extracted customer data.Extracted fieldsDOCUMENT SCHEMAtriggerextraction.completed → Make…payloadcolumns, rows, metadata,…signatureHMAC-SHA256…A Make scenarioDESTINATION 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 → Make webhook
Payload
columns, rows, metadata, confidence
Signature
HMAC-SHA256 (X-Dynamite-Signature)
Connect the steps in your scenario. Illustrative example.

A Make scenario needs these inputs and checks:

Triggerextraction.completed → Make webhook
Payloadcolumns, rows, metadata, confidence
SignatureHMAC-SHA256 (X-Dynamite-Signature)
Send documents inPOST /api/v1/infer with a key
Destinationsapps available through Make modules
Retriesbackoff + jitter, up to 3 attempts

A realistic example

A receivable automation assembled in Make:

StepModuleWhat happens
TriggerWebhooks (instant)Receives extraction.completed from Dynamite Docs
ParseRouterSplits by docType, invoice vs. receipt
TransformGoogle Sheets rowMaps columns to the receivable ledger
NotifySlack messagePosts a summary to the team channel

What the Make.com connection does and does not

Does

  • Triggers Make.com scenarios with a signed extraction.completed webhook the moment an extraction finishes.
  • Lets Make POST documents into /api/v1/infer with a scoped key and receive the structured table.
  • Retries transient delivery failures so a Make outage does not silently drop an event.

Does not

  • Does not require a private Make app or Make-specific credentials. It uses the public webhook and REST API.
  • Does not send original file bytes in webhook events. The payload carries the extracted data.
  • Does not let automation exceed the same page caps and monthly allowance as interactive use.

Why Make.com needs no separate app

Make.com runs on the public webhook and REST API. Nothing extra to install.

One trigger can feed any destination available in the Make scenario you configure.

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

Make extraction the trigger, not the endpoint.

Register the webhook, add an HTTP module to a scenario, and send each completed extraction to the destination you configure.

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.