When non-attending contact archived in Clubworx, sync it to ProspectX.
When a non-attending contact is archived in Clubworx, sync the status change to ProspectX.
See all Clubworx + ProspectX 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.
Clubworx Explore Clubworx →
TriggersFires when a new member, client or user joins in Clubworx.
Fires when someone books a class or session in Clubworx.
Fires when a workout, habit, journal entry or goal is logged in Clubworx.
Creates or updates a member's profile in Clubworx.
Books a class or session for a client in Clubworx.
Logs a workout, habit or data point in Clubworx.
ProspectX Explore ProspectX →
TriggersFires when a new contact or lead is added to ProspectX.
Fires when a field on a contact changes in ProspectX.
Fires when a deal, case or record moves to a new stage in ProspectX.
Fires when a deal is marked won in ProspectX.
Creates or updates a contact in ProspectX.
Creates a new deal in ProspectX.
Moves a deal or record to a new stage in ProspectX.
Logs a call, email, or note against a record in ProspectX.
Common questions
Can Knit build “When non-attending contact archived in Clubworx, sync it to ProspectX.” between Clubworx and ProspectX?
Yes — describe it in the box above and Knit's Integrations Agent researches Clubworx and ProspectX'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.