Assign priority developer tasks from feature request forms
When a new form submission is received in forms.app, automatically create and assign an issue to a developer in Crowdin based on the request category.
See all Crowdin + forms.app 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.
Crowdin Explore Crowdin →
TriggersFires when a translation or localization task finishes in Crowdin.
Fires when a translation key or string changes in Crowdin.
Fires when a translator leaves a comment or issue in Crowdin.
Creates a translation project in Crowdin.
Uploads a source file or content for translation to Crowdin.
Downloads the translated file from Crowdin.
forms.app Explore forms.app →
TriggersFires when a form is submitted in forms.app.
Fires when a respondent finishes a survey in forms.app.
Fires when an existing response is edited in forms.app.
Creates or updates a form or survey in forms.app.
Looks up a specific form response in forms.app.
Adds a respondent or contact to a form in forms.app.
More Crowdin + forms.app workflows
See all Crowdin + forms.app integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Assign priority developer tasks from feature request forms” between Crowdin and forms.app?
Yes — describe it in the box above and Knit's Integrations Agent researches Crowdin and forms.app'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 can customer feedback forms feed into engineering tasks?
When users submit a bug report or survey in forms.app, a structured issue is automatically created in Crowdin for developers to triage.
Can survey tools gather follow-up details based on issue updates?
Yes, when an issue status changes or is resolved in Crowdin, you can update form records or add respondents in forms.app for follow-up testing.