Expensify Make integrationAutomate Expensify with Make.
Stop retyping spending data into Expensify. The Expensify Make integration gives you 12 modules: 10 actions and 2 searches. This guide is for finance and ops people who already know Expensify and walks you from connection to a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Expensify Make integration automate?
The Expensify Make integration links your Expensify account to Make so other tools can create expenses, file reports, manage policies and update employees for you. A scenario (the automation you build in Make, a chain of bricks called modules) carries the data from one app to the next, with no code to write.
Expenses that log themselves. A purchase recorded in a spreadsheet or a form becomes an Expensify line through Create a Single Expense, and Create an Expense Report can group a trip or project into one report ready for approval.
Approvals that follow your other tools. When a manager signs off somewhere else, Update a Report Status moves the report along in Expensify, and Export a Report hands the finished data to the next step, such as your archive or your accountant's folder.
Policies kept in line with your org chart. List Policies and Get a Policy read what exists, Create a Policy and Update a Policy change it, and the two rule modules set what each employee may spend on a given policy.
Know the limits before you start. Expensify has no trigger in Make, so nothing inside Expensify can start a scenario by itself, and there is no Make an API Call module to reach beyond these 12. If you are new to the editor, the Make training covers the basics, and Make troubleshooting helps when a run fails. Weighing another tool? Read n8n vs Make.
How do you connect Expensify to Make?
- 01
Copy your partner credentials
In Expensify, open Tools > Integrations. Copy the Partner User ID and the Partner User Secret shown on that screen. Make needs both, and they only exist on an active Expensify account.
- 02
Add an Expensify module
In your Make scenario, add any Expensify module and click Create a connection. A connection is your Expensify account linked to Make once, then reused by every Expensify module. The Connection name field is optional, but a clear name helps later.
- 03
Paste and save
Paste the two values you copied into the connection window, or follow the on-screen instructions, then save. The module fields become available, and you can start filling them.
Build your first scenario with Expensify
GoalWhen a purchase is logged in another app, Make creates the matching expense in Expensify.
- 01
Create the scenario
On the Scenarios page, create a new scenario and click the + to add the first module. Since Expensify has no trigger, this first module comes from the app where purchases are recorded, such as a sheet or a form.
- 02
Set up the source module
Search that app by name, pick the module that reads new entries, and connect its account. Each entry it returns becomes a bundle, one item that flows from module to module.
- 03
Add Create a Single Expense
Click the + on the right of the first module, search Expensify and choose Create a Single Expense. Connect your account, then map the purchase data from the previous module into the fields.
- 04
Test with Run once
Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received. Check in Expensify that the expense landed as expected.
- 05
Schedule and switch on
Open the clock on the first module (Scheduling). A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Pick your interval and switch the scenario on.
What each Expensify module does in Make
Expensify gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create an Expense Report
ActionIn Make“Creates an expense report.”
Get a ready-to-approve report in Expensify without assembling it by hand. The module files a new expense report from data your scenario already carries, so the container exists before anyone opens the app.
Create a Policy
ActionIn Make“Creates a policy.”
A new team or entity can have its own Expensify policy the moment it exists elsewhere. This action creates the policy from your scenario, so nobody has to rebuild it through the admin screens.
Create a Single Expense
ActionIn Make“Creates a single expense item.”
One purchase in, one Expensify expense out. This is the smallest building block of the app: it adds a single expense item, which makes it a natural pick for a first scenario.
Create Expense Rules
ActionIn Make“Creates expense rules for a given employee on a given policy.”
Give a new employee the right spending rules on day one. The module sets expense rules for one employee on one policy, so their setup does not wait for an admin to find a free moment.
Export a Report
ActionIn Make“Exports expense or report data and downloads it.”
Pull expense or report data out of Expensify as a downloaded file your scenario can pass on. That turns an approved report into something you can store, share or send to your accountant.
Get a Policy
ActionIn Make“Returns information about the selected policy.”
Read the details of one policy so the next module can reuse them. Nothing changes in Expensify: this action only returns information about the policy you select.
Update an Employee
ActionIn Make“Updates the selected employee.”
Keep employee records in Expensify aligned with the system your company treats as the reference. The action updates the employee you select, so a change made once in HR shows up in expenses too.
Update a Policy
ActionIn Make“Updates the selected policy.”
Change an existing policy from a scenario rather than clicking through settings. It edits the policy you select and leaves the others alone.
Update a Report Status
ActionIn Make“Updates the selected report status.”
Move a report forward in Expensify when the decision happens somewhere else. The module sets a new status on the report you select, so approvers can keep working where they already are.
Update Expense Rules
ActionIn Make“Updates a preexisting expense rule for a given employee on a given policy.”
Adjust the rules already attached to an employee on a policy, without deleting and recreating them. It keeps the person's setup in place and only changes what you map.
List Domain Credit Cards
SearchIn Make“Lists all domain credit cards.”
See every credit card attached to your Expensify domain in one pass. This search returns all of them, each as its own bundle, which makes it easy to copy the list into a sheet for a finance review.
List Policies
SearchIn Make“Lists all policies.”
Get the full list of your Expensify policies so a scenario can work through them. The search returns each policy as a separate bundle you can filter or pass on.
Need help automating Expensify with Make?
A person reads every message.
