When access expired in Member Kitchens, sync it to Google Forms (Legacy).
When user access expires in Member Kitchens, log the expiration record in Google Forms.
See all Member Kitchens + Google Forms (Legacy) integrations or talk to a human
Opens Claude with Knit filled in: click Continue. Claude web and desktop share one connector list. Or paste this link in Settings > Connectors > Add custom connector.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents claude
Run in your own terminal, then restart Claude Code. Adds the server, the Knit skill and a CLAUDE.md note.
Turn on developer mode, then create a connector named Knit with this link and No Auth.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents codex
Run in your own terminal (not through Codex), then start a new Codex session.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents antigravity
Run in your own terminal, then reload MCP servers (/mcp in the CLI, refresh in the IDE).
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents cursor
Run in your own terminal, restart Cursor, then paste the note it prints into User Rules.
Google for Startups AcceleratorHow 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.
Member Kitchens Explore Member Kitchens →
TriggersFires when a new page or post is published on Member Kitchens.
Fires when a form on Member Kitchens is submitted.
Fires when a CMS item is updated on Member Kitchens.
Publishes or updates a page on Member Kitchens.
Creates a new CMS item on Member Kitchens.
Updates existing content on Member Kitchens.
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).
More Member Kitchens + Google Forms (Legacy) workflows
See all Member Kitchens + Google Forms (Legacy) integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When access expired in Member Kitchens, sync it to Google Forms (Legacy).” between Member Kitchens and Google Forms (Legacy)?
Yes — describe it in the box above and Knit's Integrations Agent researches Member Kitchens 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.
Can survey submissions automatically populate content on my website?
Yes, when a user completes a survey in Google Forms (Legacy), you can automatically create a new CMS item in Member Kitchens to publish testimonial posts or directory entries.
How does website activity update survey participant lists?
When a visitor submits an embedded form on Member Kitchens, you can automatically add them as a respondent in Google Forms (Legacy) for follow-up research.