When non-attending contact archived in Clubworx, sync it to Customer.io.
Update subscriber status in Customer.io when a non-attending contact is archived in Clubworx.
See all Customer.io + Clubworx 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.
Customer.io Explore Customer.io →
TriggersFires when a new lead or contact is captured in Customer.io.
Fires when a contact enters an automation in Customer.io.
Fires when a field on a contact changes in Customer.io.
Fires when a contact unsubscribes in Customer.io.
Creates or updates a contact in Customer.io.
Adds a contact to a workflow or campaign in Customer.io.
Sends an email or message to a contact via Customer.io.
Changes a contact's tags in Customer.io.
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.
Common questions
Can Knit build “When non-attending contact archived in Clubworx, sync it to Customer.io.” between Customer.io and Clubworx?
Yes — describe it in the box above and Knit's Integrations Agent researches Customer.io and Clubworx'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.