Resources · Make integration

Splitwise Make integrationAutomate Splitwise with Make.

Tired of typing every shared cost into Splitwise by hand? The Splitwise Make integration gives you 7 modules: 1 trigger, 5 actions and 1 search. This guide shows what each one does, how to link your account and how to build a first scenario that logs expenses for you.

Try the Splitwise integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Splitwise Make integration do for you?

The Splitwise Make integration links your Splitwise account to Make, a visual tool where you chain steps into a scenario (the automation you build). Each step is a module: one brick that watches, creates, reads or deletes expenses. You drag, map and test, without writing code.

Expenses that log themselves. A flatshare collects receipts through a form. Each new answer can feed Create an Expense, so the cost lands in the right Splitwise group without anyone retyping it.

A record of every new cost. A small team that splits travel costs can let Watch Expenses spot each new entry, then copy it to a spreadsheet or a message for whoever keeps the books. Search Expenses does the same for past entries when you need a batch to review.

Corrections in one place. When an amount changes at the source, Update an Expense fixes the Splitwise entry, and Delete an Expense removes a line that should never have been logged.

What Make does not cover: the trigger only reacts to new expenses, and the module list stops at expenses. For anything else the Splitwise API offers, Make an API Call reuses the same connection. Splitwise also exists in n8n; the n8n vs Make comparison sets both tools side by side, and our Make review covers the editor in depth. Stuck on an error? See Make troubleshooting.

Connect

How do you connect Splitwise to Make?

  1. 01

    Add a Splitwise module

    Log in to Make, open your scenario and add any Splitwise module. In its settings, click Create a connection. A connection is your Splitwise account linked to Make once, then reused by every Splitwise module you add later.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label helps when several people share the workspace. Something like the account owner and the group purpose is enough to tell connections apart later.

  3. 03

    Enter your credentials

    You need an active Splitwise account plus an API Key or an OAuth access token. Paste the credentials copied from Splitwise, or follow the on-screen prompts, and Make saves the connection so the module can list your data.

First scenario

Build your first scenario with Splitwise

GoalWhen a new cost comes in from another app, such as a form answer or a spreadsheet row, Make logs it in Splitwise as an expense.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where the cost first appears, such as the form your housemates fill in, and choose its trigger.

  2. 02

    Add Create an Expense

    Click the + on the right of that first module, search for Splitwise and pick Create an Expense. Click Create a connection if your account is not linked yet.

  3. 03

    Map the cost

    Fill the fields Make shows for the new expense by mapping values from the first module. Once the connection exists, Make lists what it can read from your Splitwise account, so you pick instead of typing.

  4. 04

    Test with Run once

    Click Run once, then add a test cost at the source. Open the bubbles to read the bundles (each item passed between modules) and check that the new expense shows up in Splitwise.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Set the schedule, then switch the scenario on.

Triggers

What starts a Splitwise scenario

1 module starts a scenario when something happens in Splitwise. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Splitwise as soon as it happens.

Splitwise1Watch Expenses

Watch Expenses

Scheduled trigger

In Make“Triggers when the new expense is created.”

Watch Expenses spots each expense added in Splitwise and hands it to the next module as a bundle, so the rest of your scenario can copy, notify or archive it.

How it fires
it is a scheduled trigger. Make checks Splitwise on the scenario's schedule, every 15 minutes by default, so a new expense reaches you on the next check rather than the second it is saved.
When to use it
a shared trip or household where someone else keeps the accounts and wants each new cost mirrored in a sheet or a chat.
Watch out
it reacts to new expenses only, so edits to an existing one will not start the scenario.
Modules

Every Splitwise module in Make

Splitwise gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Splitwise1

Create an Expense

Action

In Make“Creates a new expense.”

Create an Expense writes a new cost into Splitwise from data another module passes along, so nobody has to open the app and type it again.

When to use it
receipts arrive through a form, an email or a spreadsheet, and each one should become a shared expense.
Watch out
run it with Run once on a single test cost first, since a wrong mapping creates a real entry your group will see.
Splitwise2

Delete an Expense

Action

In Make“Deletes an expense.”

Delete an Expense removes one expense from Splitwise, which keeps balances clean when a cost was logged by mistake or cancelled at the source.

When to use it
a booking gets refunded and the matching entry has to disappear from the group.
Watch out
treat the removal as final and check in a Run once test that the scenario targets the right expense before switching it on.
Splitwise3

Get an Expense

Action

In Make“Returns an expense.”

Get an Expense fetches one expense you already point to and returns its details, ready to map into the next module.

When to use it
another step gives you a single expense reference and you need everything about it, for a report line or before deciding to update it.
Watch out
it reads one item only; to pull a batch of entries, reach for Search Expenses instead.
Splitwise4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you call any endpoint of the Splitwise API from your scenario, using the connection you already set up, so you are not limited to the expense modules.

When to use it
you need something the listed modules skip, such as data beyond expenses.
Watch out
you write the request yourself, so keep the Splitwise API documentation open and test the call with Run once.
Splitwise5

Update an Expense

Action

In Make“Updates an expense.”

Update an Expense changes an existing entry in place, so the group sees the corrected figure without a duplicate line appearing next to the old one.

When to use it
the final invoice differs from the estimate you logged, and the Splitwise amount should follow.
Watch out
Watch Expenses does not react to edits, so an update will not restart a scenario built on that trigger.
Splitwise6

Search Expenses

Search

In Make“Returns a list of expenses.”

Search Expenses returns a list of expenses, each as its own bundle, which gives you a set of past entries to review, copy or tidy up in one pass.

When to use it
closing a trip or a project, when you want every related cost pushed to a spreadsheet.
Watch out
the result can hold zero, one or many bundles, and every module after it runs once per bundle, which counts operations on your plan.
Need help

Need help automating Splitwise with Make?

A person reads every message.

FAQ

Splitwise and Make: common questions

01Is the Splitwise Make integration free?
Yes, Splitwise is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in credits, meaning operations, each month. Your Splitwise subscription is a separate matter handled on the Splitwise side.
02What do you need to connect Splitwise to Make?
You need an active Splitwise account and either an API Key or an OAuth access token. In Make, add a Splitwise module, click Create a connection, optionally name it, then paste your credentials or follow the prompts. If you prefer your own OAuth app, register it in the Splitwise developer portal with the Make callback URI and copy the Client ID and Client secret it shows. The connection is then reused by every Splitwise module in your scenarios.
03Does the Splitwise trigger in Make work in real time?
No. Watch Expenses is a scheduled trigger: Make asks Splitwise for new expenses on the scenario's schedule instead of being notified the moment one is saved. A new scenario checks every 15 minutes by default. On a paid plan the interval can drop to 1 minute, while the Free plan stays at 15 minutes minimum. The trigger also reacts only to new expenses, so edits to an existing entry will not start the scenario on their own.
04What if a Splitwise module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Splitwise API with the connection you already created, which covers everything beyond the six expense modules. You build the request yourself, so test it with Run once and read the bundle it returns before mapping it further. Note that the official Make documentation for this app is marked as AI-generated from Splitwise documentation, so confirm important details with Splitwise directly.
05Should you automate Splitwise with Make or n8n?
It depends on the tool your team already uses. Make gives Splitwise a scheduled trigger, five actions, one search and a generic API call, all built visually with one shared connection. Splitwise often has an n8n node too, so the same kind of flow can live there. Compare what each tool offers for the exact expenses you want to move, and pick the one where you already build and maintain your other automations.
Same platform

Other docs you might need on this stack.

Browse all integrations