Attach survey updates as comments on open tickets
When a customer updates an existing survey response in Google Forms, automatically post the new feedback as a comment on their ticket in NeetoDesk.
See all NeetoDesk + Google Forms 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.
NeetoDesk Explore NeetoDesk →
TriggersFires when a new support ticket or chat conversation starts in NeetoDesk.
Fires when a ticket's status changes in NeetoDesk.
Fires when a ticket in NeetoDesk is assigned to an agent.
Fires when a ticket in NeetoDesk breaches its response SLA.
Creates a new ticket in NeetoDesk.
Updates a ticket's status in NeetoDesk.
Assigns a ticket in NeetoDesk to an agent.
Posts a reply or internal note on a ticket or conversation in NeetoDesk.
Google Forms Explore Google Forms →
TriggersFires when a form is submitted in Google Forms.
Fires when a respondent finishes a survey in Google Forms.
Fires when an existing response is edited in Google Forms.
Creates or updates a form or survey in Google Forms.
Looks up a specific form response in Google Forms.
Adds a respondent or contact to a form in Google Forms.
More NeetoDesk + Google Forms workflows
Generate support tickets from form responses
When a customer submits a web form in Google Forms, automatically create a detailed support ticket in NeetoDesk for team review.
See details
Add respondents to follow-up surveys when tickets close
When a ticket status is updated to resolved in NeetoDesk, add the customer as a respondent in Google Forms to send a satisfaction survey.
See details
See all NeetoDesk + Google Forms integrations → · Browse the full workflow library →
Common questions
Can Knit build “Attach survey updates as comments on open tickets” between NeetoDesk and Google Forms?
Yes — describe it in the box above and Knit's Integrations Agent researches NeetoDesk and Google Forms'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 are survey responses transferred into support tickets?
Submitting a completed survey in Google Forms automatically creates a new ticket in NeetoDesk containing all the respondent's answers.
Can ticket updates prompt custom survey distributions?
When a ticket status changes in NeetoDesk, you can automatically add the customer as a respondent in Google Forms to collect feedback.