Create expenses in Splitwise from new rows in Microsoft Excel.
When a new row is added to a Microsoft Excel spreadsheet, create a corresponding expense in Splitwise.
See all Splitwise + Microsoft Excel integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Splitwise Explore Splitwise →
TriggersFires when an employee submits a new expense in Splitwise.
Fires when an expense in Splitwise is approved.
Fires when an expense in Splitwise is rejected.
Fires when a receipt is attached to an expense in Splitwise.
Creates a new expense report in Splitwise.
Approves a pending expense in Splitwise.
Rejects a pending expense in Splitwise.
Syncs an approved expense in Splitwise to the general ledger.
Microsoft Excel Explore Microsoft Excel →
TriggersFires when a row is added to a sheet in Microsoft Excel.
Fires when a row or column changes in Microsoft Excel.
Fires when a new spreadsheet or worksheet is created in Microsoft Excel.
Adds a new row to a sheet in Microsoft Excel.
Updates the values in an existing row in Microsoft Excel.
Finds a row by a column value in Microsoft Excel.
Common questions
Can Knit build “Create expenses in Splitwise from new rows in Microsoft Excel.” between Splitwise and Microsoft Excel?
Yes — describe it in the box above and Knit's Integrations Agent researches Splitwise and Microsoft Excel's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.