All integrations
Zapier automation
IN + OUT — /api/webhooks, POST /api/extract/infer
Zapier is how non-technical teams automate their stacks, and Dynamite Docs plugs in with the exact two primitives it exposes: outbound webhooks that fire on extraction.completed, and the REST API with scoped tokens any Zap can call. Set up a Zap once and a finished extraction routes itself to your CRM or your spreadsheet, with signature verification so the automation only ever acts on genuine events.
Try it free or read the API & webhooks docs.
The last mile of extraction is distribution
- Extraction produces a table, but the table is only useful once it lands where the team works, and that usually means several different places.
- Without automation, distributing rows means exporting a file and re-importing it everywhere, by hand, every time.
- Most of the people who need this are not engineers; the tooling to wire a pipeline should not assume a developer is around.
- Automation is only safe when it can tell a genuine event from a spoofed one. An unsigned webhook is a fake-data risk.
How the Zapier connection works
01 — Create a Zapier webhook trigger
In Zapier, choose the Webhooks app, create a Catch Hook trigger, and copy its public endpoint URL.
02 — Register it as a Dynamite Docs webhook
Add that URL as a webhook endpoint in Dynamite Docs. Endpoints must be public HTTPS URLs, and payloads are signed with HMAC-SHA256.
03 — Map the fields in the Zap
Zapier shows the received columns, rows, metadata, and confidence. Map them into the action app, a spreadsheet row or a CRM contact.
04 — Send documents in via the API
For the IN direction, a Zapier Webhooks action POSTs a file to /api/extract/infer with a scoped token and consumes the structured response.
The Zapier surface
The same primitives, exposed to Zapier as a first-class trigger and action:
- Trigger — extraction.completed → Catch Hook
- Payload — columns, rows, metadata, confidence
- Signature — HMAC-SHA256 (X-Dynamite-Signature)
- Send documents in — POST /api/extract/infer with a token
- Destinations — 6,000+ apps via Zapier
- Retries — backoff + jitter, up to 3 attempts
A realistic example
A vendor-onboarding Zap assembled in minutes:
| Step | Module | What happens |
|---|
| Trigger | Catch Hook | Receives extraction.completed from Dynamite Docs |
| Check | Filter | Keeps only W-9 documents with confidence above 0.9 |
| Create | HubSpot contact | Writes vendor name and tax ID to the CRM |
| Store | Google Sheets row | Appends the row to the vendor register |
Zapier turns one extraction into many side effects
Zapier integrations work best when the tool being connected exposes clean, verifiable primitives rather than a custom app. Dynamite Docs does exactly that: an outbound webhook fires the moment an extraction completes, carrying columns, rows, metadata, docType, and average confidence to the Catch Hook trigger. The Zap then fans out to whatever the workflow needs, a CRM update or a spreadsheet append. Because the payload is signed with HMAC-SHA256 over the raw body, the Zap can verify the event before acting, which closes the spoofing hole that plagues unsigned webhooks.
The IN direction keeps Zapier useful as an entry point. A Zap that starts with a Gmail attachment or a form submission can POST the document to /api/extract/infer using a scoped API token. The response carries the structured table, which the Zap can then route onwards. Tokens are revocable per user, and automated requests respect the same per-document page caps and monthly allowance as interactive use. Automation is not a way around the quota model.
Delivery reliability is built in at the webhook layer. Network errors, 429s, and 5xx retry with exponential backoff and jitter, up to three attempts, so a transient Zapier issue does not silently drop an extraction event. Zapier’s own retry behavior then takes over if a Zap step fails, which gives the pipeline two honest layers of retry instead of one.
The limits are the same as any webhook consumer. Events carry extracted data, not original file bytes, and the endpoint must be a public HTTPS URL. For teams already on Zapier, the setup is short: create the trigger, register the URL, map the fields, and turn the Zap on. For teams that prefer a DIY pipeline, the underlying webhooks and REST API are documented on their own pages.
What the Zapier connection does and does not
Does
- Triggers Zaps with a signed extraction.completed webhook the moment an extraction finishes.
- Lets Zaps POST documents into /api/extract/infer with a scoped token and consume the structured table.
- Retries transient delivery failures so a Zapier outage does not silently drop an event.
Does not
- Does not require Zapier-specific credentials or a private Dynamite Docs Zapier app.
- Does not send original file bytes in webhook events. The payload carries extracted data.
- Does not exempt automation from the same page caps and monthly allowance as interactive use.
Why Zapier needs no separate app
Zapier works because it rides the public webhook and REST API surfaces. Nothing extra to install.
A no-code trigger puts extraction data in the hands of the teams that need it, not just the engineering team.
Signed, retried, quota-governed primitives keep the automation honest from trigger to destination.
Questions, answered
How do I connect Zapier to Dynamite Docs?
Create a Catch Hook trigger in Zapier, copy its public URL, and register it as a webhook endpoint in Dynamite Docs. Zapier verifies the HMAC-SHA256 signature before the Zap runs.
Can a Zap send documents into Dynamite Docs?
Yes. A Webhooks action POSTs the file to /api/extract/infer with a scoped API token and reads the structured rows from the response.
Is there a native Dynamite Docs Zapier app?
No. The connection uses the public webhook and REST API surfaces that work without Zapier, so it never depends on a private app.
Does automation count against my allowance?
Automated requests respect the same per-document page caps and monthly allowance as interactive use. Automation is not a quota workaround.
Document workflows it feeds
Open app, no payment details.