When client added in PT Distinction, sync it to PandaDoc.
When a new client is added in PT Distinction, generate a training agreement contract in PandaDoc.
See all PT Distinction + PandaDoc integrations or talk to a human
Google for Startups AcceleratorHow 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.
PandaDoc Explore PandaDoc →
TriggersFires when a document is sent for signature in PandaDoc.
Fires when all parties have signed a document in PandaDoc.
Fires when a signer declines to sign in PandaDoc.
Fires when a pending envelope in PandaDoc is voided.
Sends a document out for signature via PandaDoc.
Voids a pending envelope in PandaDoc.
Checks a document's signing status in PandaDoc.
Creates a reusable signing template in PandaDoc.
Enterprise-grade security
Common questions
Can Knit build “When client added in PT Distinction, sync it to PandaDoc.” between PT Distinction and PandaDoc?
Yes — describe it in the box above and Knit's Integrations Agent researches PT Distinction and PandaDoc'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.