When new expense in Splitwise, sync it to Buffer.
When a new expense is recorded in Splitwise, queue an informational post in Buffer.
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.
Buffer Explore Buffer →
TriggersFires when a post goes live from Buffer.
Fires when your brand is mentioned or a post gets a comment in Buffer.
Fires when Buffer finds a new post, mention or creator matching what you track.
Creates a post in Buffer or adds it to the schedule.
Posts a reply to a comment in Buffer.
Adds a creator, account or post to a list or campaign in Buffer.
Common questions
Can Knit build “When new expense in Splitwise, sync it to Buffer.” between Splitwise and Buffer?
Yes — describe it in the box above and Knit's Integrations Agent researches Splitwise and Buffer'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.