Track document rejections directly in your database
When a signer declines an envelope in DocuSign, immediately update the status field in Stackby so your operations team can follow up.
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.
Stackby Explore Stackby →
TriggersFires when a new row is added to a table in Stackby.
Fires when an existing row changes in Stackby.
Fires when a scheduled query in Stackby finishes running.
Runs a SQL query against Stackby and returns the result.
Writes a new or updated row to Stackby.
Syncs a table in Stackby with data from another source.
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 Stackby + DocuSign workflows
Send signature requests automatically from new database records
When a new client record is added in Stackby, automatically generate and send a contract envelope for signature using DocuSign.
See details
Update customer records when documents are signed
As soon as an envelope is fully signed in DocuSign, automatically update the corresponding row in Stackby to mark the agreement as executed.
See details
See all Stackby + DocuSign integrations → · Browse the full workflow library →
Common questions
Can Knit build “Track document rejections directly in your database” between Stackby and DocuSign?
Yes — describe it in the box above and Knit's Integrations Agent researches Stackby 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.
What's the most common Databases & Warehouses + E-Sign automation?
Writing each completed signature event from DocuSign — signer, timestamp, template — into a table in Stackby as it happens.
Does this only capture completed signatures, or every stage?
The Agent can track every stage DocuSign exposes — sent, viewed, signed, declined — not just the final completion event.