When candidate status changed in DevSkiller, sync it to Firma.dev.
When candidate status updates in DevSkiller, sync assessment scores to Firma.dev.
See all Firma.dev + DevSkiller 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.
Firma.dev Explore Firma.dev →
TriggersFires when a document is sent for signature in Firma.dev.
Fires when all parties have signed a document in Firma.dev.
Fires when a signer declines to sign in Firma.dev.
Fires when a pending envelope in Firma.dev is voided.
Sends a document out for signature via Firma.dev.
Voids a pending envelope in Firma.dev.
Checks a document's signing status in Firma.dev.
Creates a reusable signing template in Firma.dev.
DevSkiller Explore DevSkiller →
TriggersFires when a candidate completes an assessment in DevSkiller.
Fires when a candidate receives a new score or grade in DevSkiller.
Fires when a candidate is marked hired in DevSkiller.
Fires when a new candidate is added to DevSkiller.
Sends a test or assessment invitation to a candidate via DevSkiller.
Re-sends an assessment invitation to a candidate in DevSkiller.
Common questions
Can Knit build “When candidate status changed in DevSkiller, sync it to Firma.dev.” between Firma.dev and DevSkiller?
Yes — describe it in the box above and Knit's Integrations Agent researches Firma.dev and DevSkiller'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.