Skip to main content
BounceBox ships a first-party Zapier integration, listed in the Zapier app directory. It connects your workspace to Zapier over OAuth — connection management happens on zapier.com, not in the dashboard.

Connect your account

1

Create a Zap

Open BounceBox on Zapier and start a Zap from there, or search for BounceBox as the trigger or action app in the Zap editor.
2

Sign in and allow

Choose Sign in / Connect account. A browser window opens on bouncebox.app — log in with your normal dashboard account. Check the workspace and the list of what Zapier will be able to do, then click Allow. Cancel returns to Zapier without connecting.
3

Done

The window closes and Zapier confirms the connection. Tokens refresh automatically — you never re-authenticate unless you disconnect. Reconnect or remove the connection under Zapier → Connections.

Triggers

Both triggers are instant (REST hooks) and support an optional Mailbox filter — pick one mailbox or leave it empty to fire for all mailboxes in the workspace.

New Mail

Fires the moment an email lands in a mailbox — before any processing. Useful for “email arrived” notifications or kicking off downstream lookups while extraction runs. Key fields: id, email_id, mailbox_id, mailbox_address, mailbox_label, schema_template, from, to, subject, received_at, status ("received"), attachments (filename, contentType, size — no download URL yet).

Processed Mail

Fires when extraction finishes — both when the email lands in review (status: "awaiting_review") and when delivery completes (status: "completed"). This is the trigger to use when a Zap needs the extracted data. Key fields: id, email_id, result_id, result_revision, mailbox_id, mailbox_address, mailbox_label, schema_template, from, to, subject, received_at, status, attachments (with signed url, valid 7 days), data.
data is the extracted result — the same object shown in the inbox’s extracted-result panel. Its shape follows the mailbox’s extraction template (invoice, order, or custom). See Extraction templates.

Actions

Send Email

Injects an email into a mailbox and runs it through the full pipeline — triage, extraction, review or auto-delivery. Map the email_id it returns into other steps, and use the Processed Mail trigger to receive the extracted result back in Zapier.

Approve Email

Approves an email sitting in review and delivers its result — equivalent to Approve & send in the inbox. Map email_id from a Processed Mail trigger; result_id is optional and defaults to the latest result.

Reprocess Email

Re-runs extraction from the stored raw email. Use it after changing the extraction template or when a result looks wrong. Note: reprocessing abandons any prior approval.

Skip Email

Removes an email from the work queue (spam, noise, confirmations). Skipped emails keep their source and can be reprocessed later.
  • Zapier API — REST API reference for the endpoints the integration calls.
  • Webhooks — for a fixed per-mailbox endpoint instead of Zapier, configure the mailbox’s webhook output directly.