/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- 01Create a Make.com webhook
- 02Register it as a Dynamite Docs webhook
- 03Build the scenario
- 04Send documents in via the API
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.
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.
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.
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- Trigger
- extraction.completed → Make webhook
- Payload
- columns, rows, metadata, confidence
- Signature
- HMAC-SHA256 (X-Dynamite-Signature)
A Make scenario needs these inputs and checks:
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 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
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.
Yes. A Make HTTP module POSTs the file to /api/v1/infer with a scoped key and reads the structured rows from the response.
No. It uses the same public webhook and REST API that work without Make, so the integration never depends on a private app.
Webhook delivery retries on network errors, 429s, and 5xx with exponential backoff and jitter, up to three attempts.
Extraction guides
Related integrations
Send AI extraction completion events through signed webhooks
Receive signed AI extraction completion events from Dynamite Docs. Verify HMAC signatures on raw bodies and handle retries before acting on delivered data.
POST /api/webhooks, POST /api/webhooks/:id/test
Read the integrationExtract document data using LLMs through a REST API
Extract document data using LLMs through the Dynamite Docs REST API. Submit files, retrieve structured rows, and manage scoped keys within plan limits.
/api/v1/extractions, /api/v1/infer, /api/tokens
Read the integrationPush reviewed AI-extracted tables to Google Sheets
Export reviewed AI tables from Dynamite Docs to Google Sheets. Connect once, push rows to a fresh spreadsheet tab, and keep document fields separate.
POST /api/sheets/export
Read the integrationExport reviewed AI extraction results to CSV, JSON, and Excel
Export reviewed AI data from Dynamite Docs to CSV, JSON, and Excel. Choose table downloads or Word and PDF exports from the reviewed document state.
Export API (?format=csv|json|xlsx)
Read the integrationDocument workflows it feeds
Extract invoice line items for AI accounting
Extract invoice line items for AI accounting in Dynamite Docs. Check descriptions, quantities, prices and tax against the source before entry.
Prepare invoice data with AI for accounts payable teams
Prepare supplier invoice data with AI in Dynamite Docs for accounts payable. Review fields, line items, and tax before sending checked rows to your system.
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.