When new completed form in InputKit, sync it to Human in the Loop.
When a form is completed in InputKit, route the submission to Human in the Loop for review.
See all InputKit + Human in the Loop 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.
InputKit Explore InputKit →
TriggersFires when a form is submitted in InputKit.
Fires when a respondent finishes a survey in InputKit.
Fires when an existing response is edited in InputKit.
Creates or updates a form or survey in InputKit.
Looks up a specific form response in InputKit.
Adds a respondent or contact to a form in InputKit.
Human in the Loop Explore Human in the Loop →
TriggersFires when an Human in the Loop agent finishes a task or run.
Fires when an Human in the Loop agent finishes a call or conversation.
Fires when an Human in the Loop agent marks a lead qualified.
Triggers an Human in the Loop agent or tool with a set of inputs.
Has an Human in the Loop agent place an outbound call.
Adds a lead to an outreach campaign in Human in the Loop.
Common questions
Can Knit build “When new completed form in InputKit, sync it to Human in the Loop.” between InputKit and Human in the Loop?
Yes — describe it in the box above and Knit's Integrations Agent researches InputKit and Human in the Loop'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.