Log resolved issue details back to user response records

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

Try:

See all Action1 + 97Display 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.

Action1 Explore Action1 →

Triggers

New issue captured

Fires when a new error or issue is captured in Action1.

Issue status changed

Fires when an issue's status changes in Action1.

Deployment tracked

Fires when a new deployment is tracked in Action1.

Actions

Create issue

Creates or updates an issue in Action1.

Assign issue

Assigns an issue in Action1 to a teammate.

Resolve issue

Resolves or mutes an issue in Action1.

97Display Explore 97Display →

Triggers

New form response

Fires when a form is submitted in 97Display.

Survey completed

Fires when a respondent finishes a survey in 97Display.

Response updated

Fires when an existing response is edited in 97Display.

Actions

Create or update form

Creates or updates a form or survey in 97Display.

Retrieve a response

Looks up a specific form response in 97Display.

Add a respondent

Adds a respondent or contact to a form in 97Display.

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

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

See all Action1 + 97Display 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 Action1 and 97Display?

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