Yes — install the native ExpenseBot app for Make (formerly Integromat), connect your ExpenseBot account, and build scenarios with receipt files, expenses, mileage, income, Gmail scans, and reports.
What the Make app does
Available modules:
- Upload receipts through ExpenseBot's signed pipeline and retrieve the exact processing result:
added,duplicate, or an Action Needed state - Search expenses with structured constraints (category, merchant, dates, amounts, tags)
- Create an expense (cash), add mileage, and add income from other steps in your scenario
- Start a Gmail receipt scan and check its status until it reports a terminal result
- Create an expense report after your upstream checks pass
- A guarded ExpenseBot API call for advanced scenarios — restricted to ExpenseBot's own endpoints, with protection against external URLs and malformed paths
- Category and group dropdowns populated live from your own account
The receipt pipeline requests a signed upload, sends the image or PDF, submits the uploaded reference for processing, and retrieves the exact result. Keep the submission ID and poll that exact job rather than resubmitting a pending file.
Authentication uses a revocable ExpenseBot AI Assistant Token stored in Make's credential vault, and credentials are sanitized from Make's logs. Writes are retry-safe: replaying the same action creates exactly one spreadsheet row — verified in live QA.
Example scenarios:
- Gmail, Drive, or Slack receipt capture — watch for a file, upload it, poll its exact result, and route success separately from Action Needed.
- Client/project expense entry — create an expense from a form or Slack message and assign an existing ExpenseBot client, project, or trip group.
- Mileage or income entry — send reviewed values from another scenario step with a stable Source Event ID.
- Gmail scan monitoring — start a bounded scan, poll until terminal, then route the result.
- Report handoff — create an ExpenseBot report and notify the requester with its report URL. Downstream accounting systems remain the accounting source of truth.
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. Make orchestrates ExpenseBot; it does not duplicate ExpenseBot's accounting rules, and your accounting platform remains the final books.
Get started
In Make, add the ExpenseBot app to a scenario and create a connection with a revocable ExpenseBot AI Assistant Token. Start with a read-only search or one controlled receipt before enabling a schedule. For Zapier, use the native ExpenseBot integration or Zapier's MCP Client.
The boundary
- Configured write modules run when the scenario reaches them, and a submitted receipt can add a row after processing. Review mappings, use a stable Source Event ID, test one controlled record, and route unclear outcomes to Review Expenses before enabling a schedule.
- Writes are retry-safe: replaying the same Source Event ID creates one financial record, not a duplicate.
- Your expense records live in a Google Sheet in your own Drive; revoke the AI Assistant Token at any time to end access.
Related
- What an MCP connector is — the category explainer.
- Connect ExpenseBot to Zapier's MCP Client — the equivalent on Zapier, usable today in beta.