When new document submitted in Samsara, sync it to SignRequest.
When a document is submitted in Samsara, send signature requests through SignRequest.
See all SignRequest + Samsara 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.
SignRequest Explore SignRequest →
TriggersFires when a document is sent for signature in SignRequest.
Fires when all parties have signed a document in SignRequest.
Fires when a signer declines to sign in SignRequest.
Fires when a pending envelope in SignRequest is voided.
Sends a document out for signature via SignRequest.
Voids a pending envelope in SignRequest.
Checks a document's signing status in SignRequest.
Creates a reusable signing template in SignRequest.
Samsara Explore Samsara →
TriggersFires when a device connected to Samsara comes online.
Fires when a device connected to Samsara goes offline.
Fires when a reading from a device in Samsara crosses a set threshold.
Sends a control command to a device via Samsara.
Adds a new device to Samsara.
Records a sensor reading or event from Samsara.
Common questions
Can Knit build “When new document submitted in Samsara, sync it to SignRequest.” between SignRequest and Samsara?
Yes — describe it in the box above and Knit's Integrations Agent researches SignRequest and Samsara'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.