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