When new card payment in bunq, sync it to Strava.
When a new card payment occurs in bunq, sync the activity details to Strava.
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.
Strava Explore Strava →
TriggersFires when a new member, client or user joins in Strava.
Fires when someone books a class or session in Strava.
Fires when a workout, habit, journal entry or goal is logged in Strava.
Creates or updates a member's profile in Strava.
Books a class or session for a client in Strava.
Logs a workout, habit or data point in Strava.
bunq Explore bunq →
TriggersFires when a new invoice is created in bunq.
Fires when a payment is recorded in bunq.
Fires when an invoice in bunq passes its due date unpaid.
Fires when a new expense is recorded in bunq.
Creates a new invoice in bunq.
Records a payment against an invoice in bunq.
Creates a new expense entry in bunq.
Syncs a customer's billing record in bunq.
Common questions
Can Knit build “When new card payment in bunq, sync it to Strava.” between Strava and bunq?
Yes — describe it in the box above and Knit's Integrations Agent researches Strava and bunq'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.