When class attendee removed in TeamUp, sync it to PT Distinction.
Update client status in PT Distinction when an attendee is removed from a class in TeamUp.
See all PT Distinction + TeamUp 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.
PT Distinction Explore PT Distinction →
TriggersFires when a new member, client or user joins in PT Distinction.
Fires when someone books a class or session in PT Distinction.
Fires when a workout, habit, journal entry or goal is logged in PT Distinction.
Creates or updates a member's profile in PT Distinction.
Books a class or session for a client in PT Distinction.
Logs a workout, habit or data point in PT Distinction.
TeamUp Explore TeamUp →
TriggersFires when a new member, client or user joins in TeamUp.
Fires when someone books a class or session in TeamUp.
Fires when a workout, habit, journal entry or goal is logged in TeamUp.
Creates or updates a member's profile in TeamUp.
Books a class or session for a client in TeamUp.
Logs a workout, habit or data point in TeamUp.
Common questions
Can Knit build “When class attendee removed in TeamUp, sync it to PT Distinction.” between PT Distinction and TeamUp?
Yes — describe it in the box above and Knit's Integrations Agent researches PT Distinction and TeamUp'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.