When new key created in Homeit, sync it to Docusign.
When a new key is created in Homeit, attach key access details to completed Docusign envelopes.
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.
Homeit Explore Homeit →
TriggersFires when a lock managed by Homeit is unlocked.
Fires when Homeit grants someone access to a space.
Fires when a visitor or guest checks in via Homeit.
Creates a new access code or key via Homeit.
Revokes a guest's or employee's access in Homeit.
Registers a visitor or guest in Homeit.
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.
Common questions
Can Knit build “When new key created in Homeit, sync it to Docusign.” between Homeit and DocuSign?
Yes — describe it in the box above and Knit's Integrations Agent researches Homeit 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.