Log resolved issue details back to user response records

When an issue is resolved in Freshservice, automatically update the corresponding respondent entry in Retently to keep customer feedback loops closed.

Try:

See all Retently + Freshservice integrations or talk to a human

Trusted by teams already building on Knit·

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.

Retently Explore Retently →

Triggers

New form response

Fires when a form is submitted in Retently.

Survey completed

Fires when a respondent finishes a survey in Retently.

Response updated

Fires when an existing response is edited in Retently.

Actions

Create or update form

Creates or updates a form or survey in Retently.

Retrieve a response

Looks up a specific form response in Retently.

Add a respondent

Adds a respondent or contact to a form in Retently.

Freshservice Explore Freshservice →

Triggers

New ticket

Fires when a new ticket or incident is logged in Freshservice.

Ticket updated

Fires when a ticket or incident is updated in Freshservice.

New record

Fires when a new user, client or device record is added in Freshservice.

Actions

Create ticket

Creates a ticket or incident in Freshservice.

Update ticket

Updates an existing ticket or incident in Freshservice.

Add note

Adds a note to a ticket in Freshservice.

Turn survey bug reports into developer tickets When a user completes a bug report survey in Retently, automatically create a detailed issue in Freshservice for your engineering team to investigate. See details

Assign priority developer tasks from feature request forms When a new form submission is received in Retently, automatically create and assign an issue to a developer in Freshservice based on the request category. See details

See all Retently + Freshservice integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Log resolved issue details back to user response records” between Retently and Freshservice?

Yes — describe it in the box above and Knit's Integrations Agent researches Retently and Freshservice'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 Retently, a structured issue is automatically created in Freshservice 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 Freshservice, you can update form records or add respondents in Retently for follow-up testing.