All integrations
Inbound email capture (Resend)
IN — POST /api/email/inbound
Most business documents arrive in email first. The receipt from the supplier and the statement from the bank sit in an inbox until someone downloads them and drags them into a tool. Dynamite Docs gives you a private forwarding address. Send the email there and the attachment lands in your workspace, extracted, without the download-and-drop step at all.
Try it free or read the API & webhooks docs.
The inbox is where documents actually arrive
- Receipts and statements show up as email attachments long before they show up in any tool, and the download-and-drop step is a standing chore.
- Supplier and customer email formats vary endlessly: plain attachments, scanned PDFs, links to portals, images inline in the body.
- An inbox is a shared, noisy channel. The document you need is buried under replies and automated notices.
- Manually routing email attachments into a workflow is exactly the repetitive work that gets deferred, and deferred receipts become missed reimbursements.
How inbound email capture works
01 — Get your private address
On PRO and ULTRA, the email capture panel shows a private forwarding address, unique per user, so attachments never mix across accounts.
02 — Forward the email
Send the message with its attachment to the alias from any mail client, Gmail, or your phone. Inbound email is handled by Resend.
03 — It lands, extracted
The attachment is captured into your dashboard and extracted automatically through the normal pipeline, ready to review like any upload.
04 — Route onward
From the workspace the extracted rows export, push to Sheets, or fire a webhook, the same connectors every other document uses.
What inbound email captures
The inbound endpoint turns a forwarded email into a document the normal extraction pipeline understands:
- Per-user aliases — unique forwarding address per account
- Attachment extraction — PDF, image, and document attachments
- Automatic extraction — analyzed on arrival like any upload
- Provider — Resend inbound webhook
- Anonymous reads — creator-only via x-anon-token, never public
A realistic example
The loop a bookkeeper runs every morning:
| Source | Action | Result |
|---|
| Vendor emails an invoice PDF | Forward to your alias | Attachment captured and extracted into the workspace |
| Employee sends a photo receipt | Forward from the phone | Vision model reads the scan, rows land for review |
| Bank emails a statement | Forward as-is | Statement parsed, transactions ready to reconcile |
Email is the integration most teams already have
Every accounting and finance team already runs on email. The documents come to them there. Inbound capture removes the two worst steps in the manual flow: remembering to save the attachment somewhere, and remembering to import it later. With a per-user alias, forwarding becomes the entire workflow. The vendor sends the invoice, you forward it (or set a filter to auto-forward), and the extracted rows are waiting when you open the dashboard.
A private address per user matters more than it sounds. A shared inbox address turns into a shared, messy document stream; a per-user alias keeps each person’s forwarded documents attributable and isolated. Combined with folders, a bookkeeper can forward each client’s bills to the alias and have them land grouped and searchable. The routing that used to happen in a mailbox now happens in the workspace.
The privacy model stays the same as uploads. Attachments are captured under the recipient’s ownership, extracted rows stay confidence-scored and reviewable, and the data never trains foundation models. Anonymous-style reads are gated behind the creator’s token, so forwarded mail is not discoverable just by knowing the address.
Inbound email is one of the three ways a document enters Dynamite Docs without a browser (alongside the REST API and Drive import). It reuses the same extraction queue, so a forwarded 200-page contract is subject to the same per-document page cap and provider routing as a dragged-in file.
What inbound email does and does not
Does
- Captures attachments from emails forwarded to your private per-user alias and extracts them automatically.
- Attributes captured documents to your account and keeps them reviewable like any upload.
- Uses the same extraction pipeline, page caps, and provider routing as browser uploads.
Does not
- Does not read or store the rest of your mailbox, only the attachments sent to the alias.
- Does not accept mail from an unauthenticated source as a public document.
- Does not parse the email body beyond the attachment it carries.
Why email capture changes the document pipeline
The documents already live in email; capture removes the manual transfer that turns a forwarded invoice into a re-keyed one.
Per-user aliases keep forwarded documents isolated and attributable, no shared-mailbox mixing, no cross-client confusion for a bookkeeper.
Inbound mail rides the same queue as uploads and Drive, so extraction stays on one pipeline with one set of rules and one provider policy.
Questions, answered
Who can use inbound email?
The email capture panel is available on PRO and ULTRA. FREE and HOBBY plans continue to bring documents in via upload, the REST API, or Drive import.
What gets captured from the email?
The attachment. The message body is not parsed as a document; only the file the email carries is captured and extracted.
Is my private address shared?
No. Each account gets its own alias, so forwarded documents land under your ownership and are never visible to another user.
Can I set up auto-forwarding?
Yes. Most mail clients support filters or rules. Create one that forwards mail from specific senders (or with a subject keyword) straight to your alias, and the loop becomes fully automatic.
Document workflows it feeds
Open app, no payment details.