Send forms for new records
When a record is created in Glide, send the matching form link from Feathery.
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.
Glide Explore Glide →
TriggersFires when a new record is added to an app built in Glide.
Fires when a record changes in an Glide app.
Fires when a record is deleted in an Glide app.
Adds a new record to an app built in Glide.
Updates an existing record in an Glide app.
Removes a record from an Glide app.
Feathery Explore Feathery →
TriggersFires when a form is submitted in Feathery.
Fires when a respondent finishes a survey in Feathery.
Fires when an existing response is edited in Feathery.
Creates or updates a form or survey in Feathery.
Looks up a specific form response in Feathery.
Adds a respondent or contact to a form in Feathery.
More Glide + Feathery workflows
See all Glide + Feathery integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Send forms for new records” between Glide and Feathery?
Yes — describe it in the box above and Knit's Integrations Agent researches Glide and Feathery'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 form responses create records?
Yes. Each new submission in Feathery can create a record in Glide with every answer mapped to a field.
Can a record update from a follow-up form?
Later responses in Feathery can look up and update the existing record in Glide.