Turn form submissions into project tasks
When a new form submission is received in Google Forms (Legacy), automatically create a follow-up task in beSlick so your team can act on it immediately.
See all beSlick + 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.
beSlick Explore beSlick →
TriggersFires when a new post or update is shared in beSlick.
Fires when someone comments on or reviews an item in beSlick.
Fires when a task is assigned to someone in beSlick.
Posts an update or announcement in beSlick.
Creates a new task in beSlick.
Creates a new project or workspace in beSlick.
Shares a file or folder in beSlick.
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 beSlick + Google Forms (Legacy) workflows
See all beSlick + Google Forms (Legacy) integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Turn form submissions into project tasks” between beSlick and Google Forms (Legacy)?
Yes — describe it in the box above and Knit's Integrations Agent researches beSlick 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.
How does integrating Google Forms (Legacy) with beSlick streamline team workflows?
Submissions collected in Google Forms (Legacy) automatically create tasks or posts in beSlick, giving team members immediate visibility and clear follow-up items without manually copying data.
Can updates in beSlick affect respondent lists in Google Forms (Legacy)?
Yes, when work is assigned or updated in beSlick, you can automatically add respondents to Google Forms (Legacy) to follow up or gather further input.