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