When canceled subscription in Pushpress, sync it to Brevo.
When a subscription is canceled in Pushpress, add the user to a win-back email list in Brevo.
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.
Pushpress Explore Pushpress →
TriggersFires when a new member, client or user joins in Pushpress.
Fires when someone books a class or session in Pushpress.
Fires when a workout, habit, journal entry or goal is logged in Pushpress.
Creates or updates a member's profile in Pushpress.
Books a class or session for a client in Pushpress.
Logs a workout, habit or data point in Pushpress.
Brevo Explore Brevo →
TriggersFires when a new subscriber is added in Brevo.
Fires when a contact unsubscribes in Brevo.
Fires when a subscriber opens or clicks a campaign in Brevo.
Creates or updates a subscriber in Brevo.
Unsubscribes a contact in Brevo.
Adds a subscriber to a list or segment in Brevo.
Sends a one-off transactional email via Brevo.
Common questions
Can Knit build “When canceled subscription in Pushpress, sync it to Brevo.” between Pushpress and Brevo?
Yes — describe it in the box above and Knit's Integrations Agent researches Pushpress and Brevo'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.