Create a ClickUp task when a comment is added in Localazy

Each time someone adds a comment in Localazy, this workflow creates a task in ClickUp from it, so translators’ questions and reviewers’ notes reach the list where your team plans its work.

Localazy

ClickUp

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 3.0k sites Productivity Free to import

The Create a ClickUp task when a comment is added in Localazy workflow on the FlowMattic canvas, with 2 steps across Localazy, ClickUp — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Comments in a localization project are often questions: what does this string mean, is this term right, can the source text change. If nobody outside Localazy sees them, they wait. This workflow turns each new Localazy comment into a ClickUp task so it is visible next to the rest of your work.

The Localazy trigger fires when a new comment is added, and FlowMattic receives the comment data Localazy sends. The ClickUp step then runs Create Task in the list you choose. Map the comment text into the task description and give the task a name that points to the string or project it concerns, when Localazy includes those details.

Every comment Localazy reports creates its own task. If your translators comment often, expect your ClickUp list to fill quickly; the tips explain how to narrow it. Each run, with the comment it carried, appears in Task History.

Translator questions for developers

A translator asks what a placeholder means. The comment becomes a ClickUp task in the developers' list, where someone answers and closes it.

Review notes for a product launch

Reviewers flag wording problems in Localazy before a release. Each note is a ClickUp task the localization lead tracks to done.

Source text changes for copywriters

When a translator points out an unclear English string, the copywriting team sees it as a task in their own ClickUp space.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Localazy Comment Added
Fires when a new comment is added in Localazy. The comment text and the details Localazy sends with it become available to map into ClickUp.
Step 2Action
ClickUp Create Task
Opens a new ClickUp task in whichever list you select. Map the comment into the task name and description, and check a test run to see which Localazy fields you can include.

What you need

FlowMatticCore
Localazy AccountAccount
ClickUp AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Add a Filter after the trigger that continues only when the comment contains a word your team agrees on, such as question, so routine replies don't each become a task.
Put a link or reference to the Localazy project in the task description, if the trigger data carries one, so whoever picks up the task can jump straight to the string.
Post a comment in a test Localazy project after import so FlowMattic captures the comment fields before you finish the ClickUp mapping.

Questions about this workflow

Does every Localazy comment create a ClickUp task?

Yes, as imported. There is no Filter, so each comment that fires the trigger becomes a separate task.

Will closing the ClickUp task resolve the Localazy comment?

No. Data flows from Localazy to ClickUp and never back. Changes in ClickUp aren't sent back to Localazy.

Can I assign the ClickUp task to a specific person?

The template doesn't show the step's options. Open the Create Task step after import to see what you can set beyond the list, name and description.

Which ClickUp list do Localazy comments go to?

The list you select when you set up the Create Task step. Use a Router with conditions on distinct project values to send different projects to different lists.