Configuration
Placeholders
Use these in the subject and body templates — click the + button next to a template field to insert one at the cursor:{{mailbox}}— the mailbox address the email was sent to{{received_at}}— when the email arrived{{email_id}}— the email’s identifier{{from}}— the original sender{{subject}}— the original subject{{attachments}}— the attachment list{{data}}— the extracted JSON{{data.<field>}}— a single extracted field, e.g.{{data.invoice_number}}
File attachments (CSV / Excel)
With Format set toCSV or Excel, the reply attaches the extracted data as a file. The data is flattened deterministically:
- Top-level scalar fields become key/value rows.
- Top-level arrays of objects become tables — one sheet per array in Excel; CSV uses the first table.
- Nested objects and arrays of scalars are JSON-encoded into the key/value rows.
Daily and weekly digests
With Schedule set toDaily digest or Weekly digest, processed results are held instead of replied to immediately. A daily digest goes out every day at 17:00 UTC; a weekly digest goes out every Sunday at 17:00 UTC. Each digest is one email per mailbox containing every pending result — each with its subject, sender and received time, plus the extracted JSON. With a CSV or Excel format, each result is attached as its own file (up to 25 attachments; the remainder is listed in the body).
Spend summary for invoice mailboxes
Mailboxes using the Invoice template get a spend summary at the top of every digest, daily or weekly. Weekly invoice digests arrive with the subjectBounceBox weekly spend report. The summary shows:
- The number of invoices, plus how many had no readable total.
- Total spend and total tax per currency. Amounts in different currencies are never added together.
- The top 5 suppliers by spend in each currency. Supplier names that differ only in capitalization or spacing are combined.
(no currency), and invoices without a supplier name under (unknown supplier).
If you switch a mailbox from a digest schedule to Every email, results that were already held go out with the next daily digest.
A failed digest send keeps the results pending and retries on the next run of the same schedule. Digests follow the same loop protection as regular replies — a mailbox whose reply address points back at BounceBox has its pending results cleared without sending.
Loop protection
A reply email that triggers another reply can spiral into a loop — two automated systems answering each other. BounceBox suppresses replies that would bounce back into BounceBox addresses or into known automated senders (auto-submitted and bulk mail), and caps reply storms, so configuring a reply output can’t create an email loop.Suppressed replies complete without a delivery-log entry — they count as the safe outcome, not a failure. Check the email’s status and details in the inbox if a reply you expected never arrived.
Retries
Reply delivery is retried up to 3 attempts with growing backoff, same as webhooks. Each attempt appears in the delivery log. Digest sends appear in the delivery log asdigest entries.