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