When new document received in SignRequest, sync it to ABC Trainerize.
When a document is received in SignRequest, attach the signed agreement to the client profile in ABC Trainerize.
See all SignRequest + ABC Trainerize 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.
SignRequest Explore SignRequest →
TriggersFires when a document is sent for signature in SignRequest.
Fires when all parties have signed a document in SignRequest.
Fires when a signer declines to sign in SignRequest.
Fires when a pending envelope in SignRequest is voided.
Sends a document out for signature via SignRequest.
Voids a pending envelope in SignRequest.
Checks a document's signing status in SignRequest.
Creates a reusable signing template in SignRequest.
ABC Trainerize Explore ABC Trainerize →
TriggersFires when a new member, client or user joins in ABC Trainerize.
Fires when someone books a class or session in ABC Trainerize.
Fires when a workout, habit, journal entry or goal is logged in ABC Trainerize.
Creates or updates a member's profile in ABC Trainerize.
Books a class or session for a client in ABC Trainerize.
Logs a workout, habit or data point in ABC Trainerize.
Common questions
Can Knit build “When new document received in SignRequest, sync it to ABC Trainerize.” between SignRequest and ABC Trainerize?
Yes — describe it in the box above and Knit's Integrations Agent researches SignRequest and ABC Trainerize'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.