When document declined in BoldSign, sync it to Uniqode.
When a document is declined in BoldSign, update dynamic link tracking in Uniqode.
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.
BoldSign Explore BoldSign →
TriggersFires when a document is sent for signature in BoldSign.
Fires when all parties have signed a document in BoldSign.
Fires when a signer declines to sign in BoldSign.
Fires when a pending envelope in BoldSign is voided.
Sends a document out for signature via BoldSign.
Voids a pending envelope in BoldSign.
Checks a document's signing status in BoldSign.
Creates a reusable signing template in BoldSign.
Uniqode Explore Uniqode →
TriggersFires when a shortened link created in Uniqode is clicked.
Fires when a new shortened link is created in Uniqode.
Creates a new shortened link in Uniqode.
Tags a link's record in Uniqode for tracking.
Retrieves click analytics for a link in Uniqode.
Common questions
Can Knit build “When document declined in BoldSign, sync it to Uniqode.” between BoldSign and Uniqode?
Yes — describe it in the box above and Knit's Integrations Agent researches BoldSign and Uniqode'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.