Google Drive import & export
IN + OUT: /api/drive/*
Import documents from Google Drive for extraction and export reviewed results back as XLSX files, with CSV and JSON available for download.
Content reviewed .
Documents already arrive somewhere, and the extracted data already has somewhere to go. Bring files in from Google Drive or the document extraction API. Review them in one workspace, then send the rows to Google Sheets, Drive, a download, a signed webhook or your own software.
You can also choose how inference runs. Use hosted document AI, bring your own provider key, connect an OpenAI-compatible endpoint or keep supported work local with Ollama. The review screen and export shape stay the same.
Every integration listed here is available now. Open a guide for the exact route, plan requirement, payload, limits and checks. If you need to remove copy-paste from one handoff, start with the app that holds the source or receives the result.
IN + OUT: /api/drive/*
Import documents from Google Drive for extraction and export reviewed results back as XLSX files, with CSV and JSON available for download.
IN + OUT: /api/v1/extractions, /api/v1/infer, /api/tokens
Submit PDFs and invoices through the document extraction API, receive structured rows and manage access with scoped tokens and clear usage limits.
AI: /api/ai/*, /api/local/*
Connect Google Gemini, Groq, Mistral, OpenAI, Anthropic, or local Ollama. Extract invoices, receipts, and PDFs at raw token rates with zero markup.
OUT: POST /api/sheets/export
Connect Google Sheets once, then push reviewed extraction rows to a fresh spreadsheet tab with document fields kept on a separate tab.
OUT: Export API (?format=csv|json|xlsx)
Download reviewed extraction tables as CSV, JSON, or XLSX, or create Word and PDF documents from the current reviewed document state.
OUT: POST /api/webhooks, POST /api/webhooks/:id/test
Register HMAC-signed webhook endpoints for extraction.completed events, verify the raw request body, and handle automatic transient retries.
IN + OUT: /api/integrations/slack/*
Import files and images shared in a chosen Slack channel, then request CSV, JSON, Excel, or source-file exports from channel messages.
IN + OUT: /api/webhooks, POST /api/v1/infer
Connect hosted Make.com scenarios to signed Dynamite Docs webhooks and scoped API calls, then map reviewed extraction rows to each destination.
IN + OUT: /api/webhooks, POST /api/v1/infer
Connect Zapier catch-hook triggers to signed extraction events, map reviewed fields into actions, and call the API with a scoped credential.
IN + OUT: /api/webhooks, POST /api/v1/infer
Connect self-hosted n8n workflows to signed Dynamite Docs webhooks and scoped API calls, with explicit verification and error branches.
Each guide names the route, plan requirement and operating limit behind the connector. That includes details such as webhook retries, endpoint count and upload limits, plus the checks your team still owns.
All connectors use the same extraction pipeline. A file that arrives through Google Drive or the API gets the same review controls and leaves through the same export builders. CSV, JSON and XLSX do not quietly change shape because the delivery method changed.
No roadmap placeholders. If a connector has a page here, you can use it.
Two ways: Google Drive import or the REST API. Both feed the same extraction pipeline.
Download as CSV, JSON, XLSX, or Word; push to Google Sheets; export to Drive; or receive extraction.completed events via outbound webhooks. The API serves the same formats to scripts.
No. Every plan can bring its own key for a provider in the registry or connect an OpenAI-compatible endpoint. BYOK on Free and Starter uses monthly PE; BYOK on Pro and Scale is unlimited. Starter, Pro, and Scale can also run the local Ollama companion. Hosted routing is the no-key option.
Yes. This page only lists functional integrations you can use right now.
Extract a document and test a connector or read the public API and webhook guide.