When visit: pre-registration in The Receptionist, sync it to Google Forms (Legacy).
When a visit is pre-registered in The Receptionist, sync entry fields to Google Forms (Legacy).
See all The Receptionist + Google Forms (Legacy) 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.
The Receptionist Explore The Receptionist →
TriggersFires when a lock managed by The Receptionist is unlocked.
Fires when The Receptionist grants someone access to a space.
Fires when a visitor or guest checks in via The Receptionist.
Creates a new access code or key via The Receptionist.
Revokes a guest's or employee's access in The Receptionist.
Registers a visitor or guest in The Receptionist.
Google Forms (Legacy) Explore Google Forms (Legacy) →
TriggersFires when a form is submitted in Google Forms (Legacy).
Fires when a respondent finishes a survey in Google Forms (Legacy).
Fires when an existing response is edited in Google Forms (Legacy).
Creates or updates a form or survey in Google Forms (Legacy).
Looks up a specific form response in Google Forms (Legacy).
Adds a respondent or contact to a form in Google Forms (Legacy).
Common questions
Can Knit build “When visit: pre-registration in The Receptionist, sync it to Google Forms (Legacy).” between The Receptionist and Google Forms (Legacy)?
Yes — describe it in the box above and Knit's Integrations Agent researches The Receptionist and Google Forms (Legacy)'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.