Mark records signed
When an envelope is completed in DocuSign, update the matching record in Noloco to signed.
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.
Noloco Explore Noloco →
TriggersFires when a new record is added to an app built in Noloco.
Fires when a record changes in an Noloco app.
Fires when a record is deleted in an Noloco app.
Adds a new record to an app built in Noloco.
Updates an existing record in an Noloco app.
Removes a record from an Noloco app.
DocuSign Explore DocuSign →
TriggersFires when a document is sent for signature in DocuSign.
Fires when all parties have signed a document in DocuSign.
Fires when a signer declines to sign in DocuSign.
Fires when a pending envelope in DocuSign is voided.
Sends a document out for signature via DocuSign.
Voids a pending envelope in DocuSign.
Checks a document's signing status in DocuSign.
Creates a reusable signing template in DocuSign.
More Noloco + DocuSign workflows
See all Noloco + DocuSign integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Mark records signed” between Noloco and DocuSign?
Yes — describe it in the box above and Knit's Integrations Agent researches Noloco and DocuSign'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.
Can a record send a document for signature?
Yes. When a record reaches a set stage in Noloco, DocuSign can send the matching agreement for signature.
Do signed documents update the record?
When the document is signed or declined in DocuSign, the record in Noloco can be updated with the status and signed copy.