Two genuinely different routes. Picking the wrong one costs an afternoon.
Use the native ExpenseBot app for a normal Zap. Use the Zapier MCP Client only when you want an agentic step that chooses among allowed tools rather than running a fixed sequence.
The native ExpenseBot app
Listed in the Zapier App Directory under Accounting, currently carrying a Beta status badge.
- Shape: fixed steps you wire by hand — triggers, actions, searches, with every field mapped explicitly.
- What you get: New Expense and New Report triggers; Upload Receipt, Create Expense, Add Mileage Entry, Add Income Entry, Start Gmail Receipt Scan and Create Expense Report actions; Find Expense, Find Report, Get Receipt Processing Result and Get Gmail Scan Status searches.
- Why it is the default: the behaviour is the same on every run. A mapped field either works or errors visibly. For anything touching a financial record, that predictability is the point.
How to connect it: Connect ExpenseBot to Zapier.
The agentic route
A separate route that points a Zap at ExpenseBot's broader MCP toolset over a custom MCP connection.
- Shape: a step that can select among the tools the connection exposes, rather than a sequence you fixed in advance.
- When it is worth it: an inbound request whose right handling varies — "look this up, and if it needs a report, make one" — where enumerating every branch as Zapier Paths would be worse than letting a step decide.
- Zapier's MCP Client is in beta. Zapier may change its behaviour or availability. Verify a read-only request before building anything on top of it.
How to connect it: Connect ExpenseBot to Zapier's MCP Client — that entry is the walkthrough for this route.
Choosing
| If you want to… | Use |
|---|---|
| Turn Gmail attachments into expense rows | Native app |
| Run a scheduled Gmail scan and alert on Action Needed | Native app |
| Build a monthly client report and email the link | Native app |
| Create expenses from a form with explicit field mapping | Native app |
| Let a step pick among allowed tools for a varied request | MCP Client (beta) |
| Use ExpenseBot from a chat assistant rather than a Zap | Neither — see the connection chooser |
You can run both. They are separate connections and do not conflict.
What is the same either way
ExpenseBot remains responsible for extraction, duplicate detection, review, financial validation, and Google Sheets writes. Zapier coordinates triggers, delays, paths, and notifications. Retries are idempotent on both routes when the trigger's stable unique ID is mapped into Source Event ID. Your expense records stay in a Google Sheet in your own Drive. Neither route is unattended approval, and neither does bookkeeping, reconciliation, or tax filing.