Turn survey bug reports into developer tickets

When a user completes a bug report survey in Tally, automatically create a detailed issue in DeepL for your engineering team to investigate.

Try:

See all DeepL + Tally 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.

DeepL Explore DeepL →

Triggers

Translation completed

Fires when a translation or localization task finishes in DeepL.

Key added or updated

Fires when a translation key or string changes in DeepL.

Comment added

Fires when a translator leaves a comment or issue in DeepL.

Actions

Create project

Creates a translation project in DeepL.

Upload file

Uploads a source file or content for translation to DeepL.

Download translated file

Downloads the translated file from DeepL.

Tally Explore Tally →

Triggers

New form response

Fires when a form is submitted in Tally.

Survey completed

Fires when a respondent finishes a survey in Tally.

Response updated

Fires when an existing response is edited in Tally.

Actions

Create or update form

Creates or updates a form or survey in Tally.

Retrieve a response

Looks up a specific form response in Tally.

Add a respondent

Adds a respondent or contact to a form in Tally.

Log resolved issue details back to user response records When an issue is resolved in DeepL, automatically update the corresponding respondent entry in Tally to keep customer feedback loops closed. See details

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

See all DeepL + Tally integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Turn survey bug reports into developer tickets” between DeepL and Tally?

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