Splitwise
FinanceConnect AI agents to Splitwise, the shared-expense tracker. Agents log expenses with equal splits, manage groups and friends, read running balances, and clean up mistaken entries as part of reconciliation flows.
What This Integration Enables
Splitwise is the ledger for money between people, not money inside an account, and that is exactly the ledger most automation ignores. Team meals, shared subscriptions, trip costs, and small supplier invoices split across partners all live here, and keeping it current is the kind of low-stakes, high-frequency chore that agents should own. FlowRunner agents read the authenticated account, resolve groups and friends, list and retrieve expenses with filters by group, friend, and date range, log new equal-split costs, and remove mistaken entries as part of correction flows. - Log shared costs from receipts, forms, or chat messages into the right group automatically - Sync group balances and simplified debts into [Google Sheets](/integrations/google-sheets) for monthly reconciliation - Notify members in [Slack](/integrations/slack) when a new expense lands or a balance crosses a threshold - Stand up new groups for trips, projects, or shared houses and circulate the invite link - Reverse mistaken entries through a reviewed correction flow instead of a quiet delete One design detail matters more here than on most connectors: Splitwise returns HTTP 200 even when a write fails. FlowRunner flows check the response body, not the status code, so a Create Expense call with a non-empty errors object is treated as the failure it is rather than a phantom success.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The team meal that logs itself
A [Typeform](/integrations/typeform) submission reports a shared cost: who ordered, what it was, what it cost. The agent calls Get Current User for the payer's id, List Groups to resolve the team's group, and List Expenses to confirm the same amount was not already logged today. Then Create Expense (Equal Split) records it, dividing the cost across every member, and [Gmail](/integrations/gmail) sends each affected member a note with their share. Nobody chases anybody at the end of the month.
Reconciliation without the scroll
On the first of the month, a scheduled flow calls List Groups for every group's simplified debts, then List Expenses filtered to the previous month for each. The results append to a [Google Sheets](/integrations/google-sheets) reconciliation tab: one row per expense, one summary row per group. A digest posts to [Slack](/integrations/slack) with the outstanding balances called out. The person who used to build this sheet by scrolling the app now just reads it.
The correction flow with a paper trail
A member flags a duplicate entry in chat. The agent calls Get Expense to pull the full record: cost, payers, per-user owed shares, and the audit fields showing who created it. It posts that context to the group owner with a simple question: delete this entry? Only on approval does Delete Expense run, and because Splitwise soft-deletes, the flow's confirmation message includes the note that the entry can still be restored from the Splitwise UI if the call was wrong. The correction happens in minutes, and everyone whose balance moved knows why.
Human-in-Loop Highlight
Create Expense (Equal Split) moves real money between real people: the moment it runs, every member of the group owes the payer their share, and Splitwise starts showing that debt on their phones. An agent that misreads a receipt does not create a data quality problem, it creates an awkward conversation. So FlowRunner flows put the gate before the write: the agent does the parsing, the group matching, and the duplicate check, then presents the proposed entry, "Dinner at Franklin's, $184.00, split 6 ways across Field Team, $30.67 each", and waits. The group owner confirms or corrects, and only then does the balance move. Delete Expense gets the same treatment in correction flows, not because the delete is unrecoverable, but because a balance that silently changes twice erodes the trust the ledger exists to hold.
Agent Capabilities
9 actionsAccount
1- Get Current User Returns the profile of the Splitwise user whose API key is configured, including id, name, email, default currency, and locale. The first call in most flows, because expense shares are built around the current user's id.
Groups
3- List Groups Lists all groups the current user belongs to, including members, balances, simplified debts, and type. Expenses not associated with any group appear under a group with id 0.
- Get Group Retrieves the full details of a single group by id, including members with individual balances, original and simplified debts, and the group invite link.
- Create Group Creates a new group with the given name and type. The authenticated user is added automatically; the returned invite link brings in everyone else. Used to stand up ledgers for new trips, projects, or houses.
Friends
1- List Friends Lists the current user's friends with id, name, email, shared groups, and the outstanding balance per currency. The lookup behind filtering expenses by person and building non-group shares.
Expenses
4- List Expenses Lists expenses visible to the current user, newest first, with pagination and filters by group, friend, and date range. The read behind reconciliation reports and duplicate checks.
- Get Expense Retrieves a single expense in full: cost, currency, category, receipt, per-user paid and owed shares, and audit fields showing who created, updated, or deleted it. The context-gathering step before any correction.
- Create Expense (Equal Split) Creates an expense split equally among all members of a group, with the current user recorded as the sole payer. The write that changes what people owe each other, and the reason this connector's flows carry a human gate.
- Delete Expense Deletes an expense by id. Splitwise soft-deletes, so the entry can be restored from the UI, but FlowRunner flows still route deletes through review because a balance that changes without explanation is a trust problem even when it is reversible.
Frequently Asked Questions
What can FlowRunner do with Splitwise?
FlowRunner agents can run Get Current User, List Groups, and Get Group in Splitwise, plus 6 more actions.
Does connecting Splitwise to FlowRunner require OAuth?
No. Splitwise connects to FlowRunner with an API key, no OAuth flow required.
Can Splitwise trigger a FlowRunner workflow automatically?
Splitwise doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Splitwise
$100 in credits. No card required. Connect in minutes.