When event rescheduled in TimeRex, sync it to DottedSign.
When an event is rescheduled in TimeRex, update agreement signature timelines in DottedSign.
See all TimeRex + DottedSign 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.
TimeRex Explore TimeRex →
TriggersFires when a new event is created in TimeRex.
Fires when an event's time or details change in TimeRex.
Fires when an event in TimeRex is canceled.
Fires shortly before a scheduled event in TimeRex starts.
Creates a new event in TimeRex.
Updates an existing event in TimeRex.
Cancels an event in TimeRex.
Finds an open time slot on a calendar in TimeRex.
DottedSign Explore DottedSign →
TriggersFires when a document is sent for signature in DottedSign.
Fires when all parties have signed a document in DottedSign.
Fires when a signer declines to sign in DottedSign.
Fires when a pending envelope in DottedSign is voided.
Sends a document out for signature via DottedSign.
Voids a pending envelope in DottedSign.
Checks a document's signing status in DottedSign.
Creates a reusable signing template in DottedSign.
Common questions
Can Knit build “When event rescheduled in TimeRex, sync it to DottedSign.” between TimeRex and DottedSign?
Yes — describe it in the box above and Knit's Integrations Agent researches TimeRex and DottedSign'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.