Make.com automation
IN + OUT: /api/webhooks, POST /api/v1/infer
Content reviewed .
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.
Open this integration in the app or read the public API and webhook guide.
The row still has somewhere to go
- 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
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
A Make scenario needs these inputs and checks:
- Trigger: extraction.completed → Make webhook
- Payload: columns, rows, metadata, confidence
- Signature: HMAC-SHA256 (X-Dynamite-Signature)
- Send documents in: POST /api/v1/infer with a key
- Destinations: apps available through Make modules
- Retries: backoff + jitter, up to 3 attempts
A realistic example
A receivable automation assembled in Make:
| Step | Module | What happens |
|---|---|---|
| Trigger | Webhooks (instant) | Receives extraction.completed from Dynamite Docs |
| Parse | Router | Splits by docType, invoice vs. receipt |
| Transform | Google Sheets row | Maps columns to the receivable ledger |
| Notify | Slack message | Posts a summary to the team channel |
What to validate before relying on it
Verify the Dynamite Docs webhook signature before the Make scenario trusts the payload, then test every mapped destination field with a sample extraction.
Make.com turns extraction into a node in a bigger graph
Make.com can use the public webhook and REST API directly, so the workflow does not depend on a private Make app. An Instant webhook receives completed extractions. HTTP modules submit files through the API. The same documented routes also work outside Make, which keeps the scenario replaceable and easier to debug.
The webhook direction is the reliable trigger. When an extraction completes, Dynamite Docs POSTs columns, rows, metadata, docType, and average confidence to the registered Make URL, signed with HMAC-SHA256 over the raw body. Add a verification step before the scenario trusts the payload. Delivery retries with exponential backoff on network errors, 429s, and 5xx, so a transient Make outage does not silently drop an event.
The API direction lets Make submit documents. A scenario that starts from a form or schedule can POST a document to /api/v1/infer with a scoped key and read the structured table from the JSON response. Keys are revocable, and automated requests use the same per-document page caps and monthly processing allowance as interactive use.
The honest limits are the connector’s own: webhook events carry extracted data, not the original file bytes, and the SSRF guard means the Make endpoint must be a public HTTPS URL. For teams already on Make, the integration is a fifteen-minute setup: create the webhook, register it, build the scenario, and test with a real extraction. For teams that want the same result without Make, the underlying webhooks and REST API are the documented building blocks.
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.
Questions, answered
How do I connect Make.com to Dynamite Docs?
Add an Instant webhook trigger in Make.com, copy its public URL, and register it in Dynamite Docs. Verify the HMAC-SHA256 signature before the scenario trusts extraction.completed.
Can Make.com send documents into Dynamite Docs?
Yes. A Make HTTP module POSTs the file to /api/v1/infer with a scoped key and reads the structured rows from the response.
Is this a native Make.com app?
No. It uses the same public webhook and REST API that work without Make, so the integration never depends on a private app.
What about retries?
Webhook delivery retries on network errors, 429s, and 5xx with exponential backoff and jitter, up to three attempts.
Related integrations
Document workflows it feeds
Related integration articles
Open the integrations workspace, no payment details.