The point of a capture automation is that nobody has to check whether it worked. This recipe closes that loop: when a receipt reaches a good terminal state, tell the person who submitted it, once, with the outcome and a link.
The workflow shape
This is the success branch of any capture recipe — Gmail, Drive, or Slack.
- Get Receipt Processing Result returns the terminal outcome for the exact submission ID you uploaded.
- Filter or path on the outcome being
addedorduplicate. - Notify — Slack message, email, or whatever your platform speaks. Include: what the outcome was, the merchant and amount if you captured them, and a link to Review expenses.
Everything else — skipped, errored, unknown, or a failed per-file outcome —
belongs on the other branch:
Action Needed routing.
Why duplicate counts as success
duplicate means ExpenseBot recognised the receipt it already has and did not
create a second row. That is the duplicate detection doing its job, and the
submitter should hear it as "already covered", not as an error. Splitting
duplicate onto the failure branch is the most common way this recipe gets
built wrong: it trains people to ignore the alerts.
Keep it to one message
Writes are retry-safe — replaying the same action creates exactly one spreadsheet row, verified in live QA — but your notifications are not deduplicated by ExpenseBot. If your scenario has retries, notify from the terminal result step only, never from an intermediate one, or people will get the same confirmation twice.
The division of labour
ExpenseBot supplies structured expense data and Gmail receipt capture to Make workflows — extraction, duplicate detection, review, and the spreadsheet record. Make handles external triggers, routing, reminders, and notifications.
The boundary
A notification says a record exists; it is not a review. Amounts, categories and business/personal treatment are still yours to confirm in ExpenseBot, and your accounting platform remains the accounting source of truth.
Where to build it
- Choose the right connection for your AI
- Connect ExpenseBot to Zapier's MCP Client — beta, usable today
- Does ExpenseBot work with Make.com? — native app submitted and in review