Resources · Make integration

Crowdin Make integrationAutomate Crowdin with Make.

Can your localization work run itself once a source file changes? The Crowdin Make integration gives you 70 modules, including 9 triggers, to move files, strings, tasks and reports without code. This guide connects your account and walks you through a first scenario.

Try the Crowdin integration on MakeSee the 70 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Crowdin Make integration do?

The Crowdin Make integration links your Crowdin account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, reads or deletes something. Crowdin brings 70 of them, so project events can start work in other apps, and other apps can feed Crowdin.

Tasks that open themselves. Watch File Events reports the file events you selected, and Create a Task hands the work to your translators with the file already named. Nobody has to remember to assign it.

Reviews that reach the right person. Watch String Comment Events fires when someone raises an issue on a string, so a product owner can see the question in the tool they already use, then answer it back with Create a Comment (Issue).

Progress you do not chase. Search Translation Progress reads how far each language has come, and Generate a Report followed by Download a Report (CSV) turns project data into a file you can drop in a shared folder.

The Crowdin doc in Make lists no specific quota; it only reminds you that its text is AI-generated and worth checking with Crowdin. When a listed module stops short, Make an API Call reaches any endpoint of the Crowdin API with the same connection. If you are weighing tools, read n8n vs Make, and the Make pricing guide explains how operations are counted. The team also runs a Make training for people who want to build these flows themselves.

Connect

How do you connect Crowdin to Make?

  1. 01

    Create a personal access token

    In Crowdin, open your account settings, click API, then the New token button. Copy the token right away: it is the key Make will use to act on your account. You need an active Crowdin account for this.

  2. 02

    Add a Crowdin module

    In your Make scenario, click the +, search for Crowdin and pick any module. Click Create a connection. The Connection name field is optional, but a clear name helps when you later link a second Crowdin account.

  3. 03

    Paste the token and save

    Paste the token you copied, or follow the on-screen instructions, and confirm. The connection, meaning your Crowdin account linked to Make once, is then reused by every Crowdin module you add to any scenario.

First scenario

Your first scenario: a task for every new file event

GoalWhen a file event you selected happens in Crowdin, Make creates a task in the project so translators can start.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the large + to add the first module. That first module is the trigger: the event that starts everything.

  2. 02

    Pick Watch File Events

    Search for Crowdin, choose Watch File Events, click Create a webhook, then Create a connection with the token from the previous section.

  3. 03

    Choose what to watch

    Fill the module fields and select the file events that matter to you. Once the connection exists, Make lists the Crowdin items it can read, so you pick from a list instead of typing IDs.

  4. 04

    Add Create a Task

    Click the + on the right of the trigger, add Crowdin Create a Task, and map data from the event into the task, such as the file it concerns.

  5. 05

    Test with Run once

    Click Run once, then cause a matching file event in Crowdin. Open the bubbles above each module to read the bundles, the items each module received, and check the new task.

  6. 06

    Switch it on

    Turn the scenario on. Because the trigger is instant, Crowdin calls Make through the webhook each time a selected file event happens, with no polling to set.

Triggers

What can start a Crowdin scenario?

9 modules start a scenario when something happens in Crowdin. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Crowdin as soon as it happens.

Crowdin1Watch File Events

Watch File Events

Instant trigger

In Make“Triggers when one of the selected file events has occurred.”

Your scenario learns about file activity in Crowdin without anyone refreshing a dashboard. You tick the file events you care about, and each occurrence arrives in Make as a bundle ready for the next module.

How it fires
instant: Crowdin calls Make through a webhook as soon as it happens.
When to use it
a developer pushes a new source file and the localization lead wants a task opened or a message posted in the team chat straight away.
Watch out
the doc asks you to click Create a webhook before Create a connection; follow that order when you first add the module.
Crowdin2Watch New Directory

Watch New Directory

Scheduled trigger

In Make“Triggers when a new directory is created.”

Each folder someone adds inside a Crowdin project becomes a fresh bundle, so you can mirror your project structure elsewhere or prepare the work that goes with it.

How it fires
scheduled: Make checks Crowdin on the scenario's schedule, every 15 minutes by default.
When to use it
your product team creates a directory per feature, and you want a matching card in your planning tool on the next check.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, while paid plans go down to 1 minute, so the new directory shows up in Make on the next check, not the instant it exists.
Crowdin3Watch New Project

Watch New Project

Scheduled trigger

In Make“Triggers when a new project is created.”

A brand new Crowdin project is often the start of paperwork: a kickoff note, a budget line, a folder for vendors. This trigger hands you each new project so that paperwork starts by itself.

How it fires
scheduled: Make checks Crowdin on the scenario's schedule, with a clock badge on the module.
When to use it
an agency manager opens a project for each client and wants the client record updated in the CRM as soon as the scenario next runs.
Watch out
because the check is scheduled, a project created just after a run waits for the next one; switch to Watch Project Events if you need an instant reaction to project activity.
Crowdin4Watch Project Events

Watch Project Events

Instant trigger

In Make“Triggers when one of the project events has occurred.”

Think of it as a doorbell on the whole project. You choose among the project events, and Crowdin rings Make each time one of them happens, handing over the details as a bundle.

How it fires
instant: Crowdin calls Make through a webhook as soon as it happens.
When to use it
you want one scenario that reacts to project-level changes, rather than several narrower triggers on files or strings.
Watch out
a wide selection of events means more runs, and each module run on a bundle is an operation counted on your Make plan; tick only the events you will act on.
Crowdin5Watch String Comment Events

Watch String Comment Events

Instant trigger

In Make“Triggers when one of the string comment events has occurred.”

Questions from translators stop getting lost. Whenever a comment or issue event you selected occurs on a string, the full comment reaches Make and can go wherever the answer lives.

How it fires
instant: Crowdin calls Make through a webhook as soon as it happens.
When to use it
a translator flags an unclear source string and the product owner, who never logs into Crowdin, needs to see it in their own inbox or ticket tool.
Watch out
if the same scenario writes comments back with Create a Comment (Issue), it can trigger itself again; filter out the comments Make wrote.
Crowdin6Watch String Events

Watch String Events

Instant trigger

In Make“Triggers when one of the string events has occurred.”

Source text changes are where localization bugs start. This trigger sends Make every string event you selected, so edits to the text you translate never go unnoticed.

How it fires
instant: Crowdin calls Make through a webhook as soon as it happens.
When to use it
a copywriter rewrites a button label and the QA lead wants a note in the release checklist so screenshots get checked again.
Watch out
when many strings change together, each event is a separate bundle, so plan your operations and test with Run once on a small project first.
Crowdin7Watch Suggestion Events

Watch Suggestion Events

Instant trigger

In Make“Triggers when one of the suggestion events has occurred.”

Every suggestion a translator proposes can now reach a reviewer outside Crowdin. Pick the suggestion events to follow, and each one lands in Make as a bundle you can route to a reviewer.

How it fires
instant: Crowdin calls Make through a webhook as soon as it happens.
When to use it
your community helps translate the app and you want proofreaders alerted when new proposals come in, instead of reviewing them in batches.
Watch out
like every instant Crowdin module, it needs Create a webhook before Create a connection, and each suggestion that reaches Make uses operations on your plan.
Crowdin8Watch Task Events

Watch Task Events

Instant trigger

In Make“Triggers when one of the task events has occurred.”

Crowdin tasks drive who translates and who proofreads what. With this trigger, the task events you select reach Make and can update the tools your project managers already follow.

How it fires
instant: Crowdin calls Make through a webhook as soon as it happens.
When to use it
a vendor finishes a translation task and the account manager wants the invoice step opened in the billing tool without being told.
Watch out
pair it carefully with Update a Task; a scenario that updates the very task it listens to can start itself again.
Crowdin9Watch Translation Events

Watch Translation Events

Instant trigger

In Make“Triggers when one of the translation events has occurred.”

This is the trigger closest to the finished product: it tells Make when a translation event you picked happens, so the result can move toward your app or website.

How it fires
instant: Crowdin calls Make through a webhook as soon as it happens.
When to use it
a language reaches the point your team treats as ready, and you want a translated file fetched or a deploy request filed right away.
Watch out
it reports events, not overall readiness; add Search Translation Progress after it if your next step depends on how complete a language is.
Modules

What can Make do in Crowdin?

Crowdin gives you 61 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Crowdin1

Add a Screenshot

Action

In Make“Adds a new screenshot.”

Translators get the visual context they keep asking for: this action adds a new screenshot to your Crowdin project, taken from a file an earlier module passed along.

When to use it
your design tool exports a new mockup and you want it in Crowdin before translators touch the strings on that screen.
Watch out
on the Free plan Make handles files up to 5 MB, so large high-resolution captures may need a paid plan.
Crowdin2

Assign a Label to the String

Action

In Make“Assigns a label to the string.”

Tagging strings by hand is slow; this action puts a label on a string for you, so filters in Crowdin show the right batch to the right translator.

When to use it
strings from a new release should carry that release label as soon as they are created, so reviewers can find them together.
Watch out
the label must exist first; run Create a Label earlier in the scenario if it may be missing.
Crowdin3

Create a Comment (Issue)

Action

In Make“Creates a new comment or issue.”

Answers and warnings reach translators where they work: this module posts a new comment, or raises an issue, on a string in Crowdin.

When to use it
a product owner replies to a question in your ticket tool, and you want that reply to appear under the string the translator asked about.
Watch out
combined with Watch String Comment Events in the same scenario, a new comment can fire the trigger again, so add a filter to stop the loop.
Crowdin4

Create a Directory

Action

In Make“Creates a new directory.”

Keep your Crowdin project organized the same way as your codebase or content library. This action adds a new directory, ready to receive files.

When to use it
a new product area appears in your repository and you want a matching folder in Crowdin before its first source file is uploaded.
Watch out
run Search Directories first if the scenario may run twice, so you do not end up with two folders carrying the same name.
Crowdin5

Create a Label

Action

In Make“Creates a new label.”

Labels are how Crowdin groups strings across files. This module creates a new one, so later steps in the scenario can attach it to the strings that need it.

When to use it
each marketing campaign gets its own label, and the scenario creates it when the campaign is added to your planning sheet.
Watch out
check with Search Labels before creating, because a scenario that runs again would otherwise add a duplicate label.
Crowdin6

Create a Project

Action

In Make“Creates a new project.”

New client or new product, same setup every time: this action opens a fresh Crowdin project from data another app provides, without anyone filling the form by hand.

When to use it
a deal marked as won in your CRM should give the localization team a ready project straight away.
Watch out
projects are central objects; test with Run once on a single record before switching the scenario on, to avoid a burst of empty projects.
Crowdin7

Create a Storage

Action

In Make“Uploads a new file to storage.”

This is the first half of getting a file into Crowdin: it uploads the file to Crowdin storage, a holding area, and returns a storage reference you can pass to the next module.

When to use it
you want to add a source file to a project through Upload a File from Storage, which expects the file to be in storage already.
Watch out
a stored file is not yet in any project; the scenario needs the second module to finish the job.
Crowdin8

Create a String

Action

In Make“Creates a new source string.”

Short texts that never live in a file, like an email subject or a push notification, can still get translated: this action adds a new source string to a project.

When to use it
your marketing team writes notification copy in a spreadsheet, and each new row should become a Crowdin string for translators.
Watch out
if the row can be edited later, use Update a String on the next pass instead of creating a second copy.
Crowdin9

Create a String Translation

Action

In Make“Creates a new string translation.”

Translations produced outside Crowdin come back in without copy-paste. The module adds a translation to an existing string, in the language you choose.

When to use it
a partner translator delivers text through a form, and you want each answer stored against the right string and language.
Watch out
you need the string first; pair it with Search Strings or Get a String earlier in the flow to find the right one.
Crowdin10

Create a Task

Action

In Make“Creates a new task.”

Work lands in a translator's queue the moment it exists. This action creates a new Crowdin task, so assignment no longer depends on someone remembering to do it.

When to use it
right after Watch File Events reports a new source file, open a translation task for the languages that file needs.
Watch out
a trigger that fires on several events can create several tasks; filter the events before this module so each change opens one task.
Crowdin11

Delete a Comment (Issue)

Action

In Make“Deletes an existing string comment or issue.”

Clears a comment or issue off a string, which keeps the discussion under each string readable once a question is settled.

When to use it
an automated warning your scenario posted earlier is no longer true, for example after the source text was fixed, and you want it gone.
Watch out
deletion cannot be undone from Make; make sure the scenario targets only the comments it created, not those written by people.
Crowdin12

Delete a Directory

Action

In Make“Deletes an existing directory.”

Removing a directory keeps Crowdin in step with a product area you retired, so translators stop seeing folders nobody ships anymore.

When to use it
a feature is removed from your repository and its folder in Crowdin should disappear with it.
Watch out
treat it as permanent. Run Get a Directory first and check the name in the bundle during a Run once test before you switch the scenario on.
Crowdin13

Delete a File

Action

In Make“Deletes an existing file.”

When a source file is gone from your product, this action takes it out of the Crowdin project too, so nobody translates text that will never ship.

When to use it
your content team archives a help article, and its file in Crowdin should be removed in the same move.
Watch out
a deleted file cannot be brought back from Make; if you may need its translations later, add Download a Translated File before this step.
Crowdin14

Delete a Label

Action

In Make“Deletes an existing label.”

Old labels clutter every filter menu. This module removes a label from the project entirely, not just from one string.

When to use it
a campaign has ended and its label no longer helps anyone sort the work.
Watch out
to take a label off a single string while keeping it for others, use Remove a Label from the String instead; this module is the wider cleanup.
Crowdin15

Delete a Project

Action

In Make“Deletes an existing project.”

The heaviest action in the list: it removes a whole Crowdin project. Useful for test projects or ones a client has formally closed.

When to use it
a scenario that spins up sandbox projects for demos can also tear them down once the demo record is marked done.
Watch out
nothing brings the project back from Make. Add a filter on the project name and test with Run once before activating.
Crowdin16

Delete a Screenshot

Action

In Make“Deletes an existing screenshot.”

Outdated screenshots mislead translators more than no screenshot at all. This action removes one from the project so only the current design stays in view.

When to use it
your design tool replaces a mockup, and the scenario first adds the new image with Add a Screenshot, then deletes the old one.
Watch out
fetch the right one with Search Screenshots first; the delete itself cannot be reversed.
Crowdin17

Delete a Storage

Action

In Make“Deletes an existing file from storage.”

Tidies up after a file upload: this module removes a file from Crowdin storage once it has served its purpose.

When to use it
at the end of a flow built on Create a Storage and Upload a File from Storage, to leave no leftover files in the holding area.
Watch out
place it after the upload to the project, never before, or the next module will point to a file that no longer exists.
Crowdin18

Delete a String

Action

In Make“Deletes an existing string.”

Text removed from your product should stop costing translation time. This action deletes a source string from the project.

When to use it
a row is deleted from the spreadsheet where your team keeps notification copy, and its Crowdin string should follow.
Watch out
Make cannot restore a deleted string; check the string ID in a Run once test before going live.
Crowdin19

Delete a String Translation

Action

In Make“Deletes an existing translated string.”

Withdraws one translation from a string while leaving the source text in place, so the language can be translated again.

When to use it
a reviewer rejects a translation in your QA tool, and you want Crowdin to show that string as untranslated in that language.
Watch out
other translations of the same string are untouched; this targets one translation at a time, so find it first with Search String Translations.
Crowdin20

Delete a Task

Action

In Make“Deletes an existing task.”

Cancelled work should leave the translators' queue at once. This module deletes a Crowdin task so nobody spends time on it.

When to use it
a release is dropped in your project tracker, and the tasks opened for it in Crowdin should vanish too.
Watch out
if you only want to change the assignee or status, Update a Task keeps the history; deletion is for work that truly no longer exists.
Crowdin21

Download a Report (CSV)

Action

In Make“Downloads a report in CSV format.”

Gives you a report as a CSV file, the format any spreadsheet opens, so figures from Crowdin can land in a finance or ops sheet without manual export.

When to use it
once Generate a Report has prepared a report, fetch it here and save it to your shared drive for the finance team.
Watch out
this module downloads an existing report; it does not build one, so Generate a Report must come first in the flow.
Crowdin22

Download a Report (JSON)

Action

In Make“Downloads a report in JSON format.”

Retrieves a report in JSON, the structured format other tools read field by field, which suits scenarios that push the numbers into a database or a dashboard.

When to use it
your BI tool accepts JSON and you want Crowdin report data to feed it after Generate a Report has run.
Watch out
pick the CSV variant instead if a human will open the file; JSON is meant for machines.
Crowdin23

Download a Translated File

Action

In Make“Generates a URL to download a file. The link has an expiration time.”

Hands you a download link for a translated file, so the finished text can travel to your website, your app build or a client folder.

When to use it
after Watch Translation Events, grab the translated file and send it to the storage your developers pull from.
Watch out
the link expires after a while, so download the file in the next module of the same scenario rather than storing the link for later.
Crowdin24

Generate a Report

Action

In Make“Generates a report.”

Asks Crowdin to build a report for a project, which is the step that makes the two download modules useful.

When to use it
when a project closes in your tracker, generate its report so the costs or progress can be archived with the client file.
Watch out
generating and downloading are separate modules; chain Download a Report (CSV) or Download a Report (JSON) after this one to get the actual file.
Crowdin25

Get a Comment (Issue)

Action

In Make“Retrieves an existing string comment or issue.”

Reads one comment or issue in full when you already know which one you need, so a later step can quote it or route it.

When to use it
a trigger gives you only the comment reference and you need its complete text before sending it to a product owner.
Watch out
it returns exactly one item; to look through several comments on a string, use Search String Comments (Issues) instead.
Crowdin26

Get a Directory

Action

In Make“Retrieves an existing directory.”

Fetches the details of one directory, handy when a previous module gave you only its ID and the next step needs more to work with.

When to use it
before deleting or renaming a folder, read it to confirm it is the one your scenario means to change.
Watch out
you need the directory ID; if you only know the name, start with Search Directories.
Crowdin27

Get a File

Action

In Make“Retrieves an existing file.”

Looks up one file in a Crowdin project and returns its details, so the rest of the scenario can decide what to do with it.

When to use it
a file event arrives and you want the file's details before choosing which team gets the task.
Watch out
this reads information about the file; to obtain translated content, use Download a Translated File.
Crowdin28

Get a Label

Action

In Make“Retrieves an existing label.”

Returns a single label with its details, useful when another module handed you only an ID and you need the readable name for a message or a sheet.

When to use it
the status message your scenario posts to the team groups strings by label, and the scenario needs the label title rather than a number.
Watch out
to find a label by its name, go through Search Labels; this module expects the ID.
Crowdin29

Get a Project

Action

In Make“Retrieves an existing project.”

Reads one Crowdin project and makes its details available to the next modules, so they can quote or route it.

When to use it
a project event arrives and you want the project name in the Slack message or CRM note the scenario writes.
Watch out
it reads a single project by its ID; when you need to browse several projects, Search Projects returns them as separate bundles.
Crowdin30

Get a Screenshot

Action

In Make“Retrieves an existing screenshot.”

Brings back one screenshot and its details, so you can reuse the image or check which strings it covers.

When to use it
a reviewer comments on a string and you want to attach the related screenshot to the ticket the scenario opens.
Watch out
it needs the screenshot ID; use Search Screenshots when you only know the project.
Crowdin31

Get a Storage

Action

In Make“Retrieves an existing file from storage.”

Checks one file sitting in Crowdin storage, the holding area files pass through before joining a project.

When to use it
a scenario uploaded a file earlier and you want to confirm it is still there before running Upload a File from Storage.
Watch out
storage is not the project itself; a file found here may not be visible to translators yet.
Crowdin32

Get a String

Action

In Make“Retrieves an existing string.”

Reads one source string so the scenario knows its text and details, for example to quote it in an alert.

When to use it
a string event arrives and the product owner should receive the exact wording before approving a change.
Watch out
one ID, one string; to find strings by their text or file, use Search Strings.
Crowdin33

Get a String Translation

Action

In Make“Retrieves an existing translation string.”

Returns one translation of a string, which lets a scenario show a reviewer exactly what was written in a given language.

When to use it
a suggestion is approved and your QA sheet should log the final translated text next to the source.
Watch out
you need the translation ID; listing every translation of a string is the job of Search String Translations.
Crowdin34

Get a Task

Action

In Make“Retrieves an existing task.”

Fetches the details of one Crowdin task, so your scenario can react to where the work stands and pass it on to your other tools.

When to use it
a task event comes in and you need the full task to update the matching line in your project tracker.
Watch out
to review all open tasks at once, Search Tasks is the better fit; this module reads one task.
Crowdin35

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Your way out when none of the 70 modules covers a need: it calls any endpoint of the Crowdin API with the connection you already set up.

When to use it
you need a Crowdin feature that has no dedicated module, and you are comfortable reading the Crowdin API reference to build the request.
Watch out
you write the path and body yourself, so test with Run once and read the response bundle before going live.
Crowdin36

Remove a Label from the String

Action

In Make“Deletes an existing label from a string.”

Takes a label off one string while the label itself stays in the project for the others, which keeps your filters accurate.

When to use it
a string was tagged for a release and then moved to the next one; remove the old label, then assign the new one.
Watch out
this is not a cleanup of the label; to delete the label everywhere, use Delete a Label.
Crowdin37

Translate via Machine Translation

Action

In Make“Auto detect source language and translate with selected MT engine.”

Gets a first draft in another language without waiting for a translator: Crowdin detects the source language and translates the text with the machine translation engine you select.

When to use it
support tickets arrive in several languages and your team wants a quick readable version before answering.
Watch out
the quality depends on the engine you pick; keep human review for anything customers will read in your product.
Crowdin38

Update a Comment (Issue)

Action

In Make“Updates an existing string comment or issue.”

Edits an existing comment or issue, so a thread can reflect new information without piling up duplicate messages.

When to use it
your scenario posted an automated status on a string and should refresh that same comment when the status changes.
Watch out
if Watch String Comment Events listens to the same project, an update can fire it; filter out changes made by Make.
Crowdin39

Update a Directory

Action

In Make“Updates an existing directory.”

Changes an existing directory in a Crowdin project, so the structure translators see follows the reorganization of your own files.

When to use it
your developers rename a product area in the repository and translators should see the same folder name.
Watch out
the module works on a directory ID; get it with Search Directories if the previous step only knows the old name.
Crowdin40

Update a File

Action

In Make“Updates an existing file.”

Replaces or edits a file already in a project, so the project keeps working on the same file instead of receiving a second copy next to the first.

When to use it
a new version of a source file is exported from your CMS and should refresh the Crowdin copy in place.
Watch out
on the Free plan Make handles files up to 5 MB; check the size of large exports before relying on this step.
Crowdin41

Update a Label

Action

In Make“Updates an existing label.”

Renames or corrects a label that already exists in your Crowdin project, so every string tagged with it follows the new wording without being touched one by one.

When to use it
your team changes its tagging convention and the old label name no longer matches how translators filter their work.
Watch out
the module edits the label itself, not its link to strings; to move a string to another label, pair Assign a Label to the String with Remove a Label from the String.
Crowdin42

Update a Project

Action

In Make“Updates an existing project.”

Changes the settings of an existing Crowdin project from inside a scenario, which keeps project details aligned with the tool where your product team plans releases.

When to use it
a release record changes in another app and the matching Crowdin project should reflect it without anyone opening Crowdin.
Watch out
pick the project from the list Make shows once the connection exists, or map its ID from an earlier module; a wrong mapping edits the wrong project.
Crowdin43

Update a String

Action

In Make“Updates an existing source string.”

Rewrites an existing source string in Crowdin, so the text translators work on stays identical to what developers ship in the product.

When to use it
a copywriter fixes a sentence in your content tool and you want Crowdin to receive the corrected source rather than a second, duplicate string.
Watch out
this edits the source, not a translation; for translated text, use Create a String Translation or Delete a String Translation instead. Find the string first with Search Strings.
Crowdin44

Update a Task

Action

In Make“Updates an existing task.”

Edits a task already created in Crowdin, keeping the assignment board honest when plans shift elsewhere.

When to use it
a deadline or an owner changes in your project management tool and the Crowdin task must follow, with no manual copy between the two apps.
Watch out
the module needs the task to exist; if your scenario may run before it is created, add Search Tasks upstream and only update when the search returns a bundle.
Crowdin45

Upload a File

Action

In Make“Uploads a file into Crowdin project.”

Sends a file straight into a Crowdin project, which puts new source content in front of translators as soon as it is produced somewhere else.

When to use it
a document or resource file lands in your cloud drive or repository tool and should become translatable without a person downloading and re-uploading it.
Watch out
on the Make Free plan, files are capped at 5 MB. To reuse a file already placed in storage, Upload a File from Storage is the better fit.
Crowdin46

Upload a File from Storage

Action

In Make“Uploads a new file from storage.”

Adds a file to a project from Crowdin's storage area, turning a file you parked earlier with Create a Storage into real project content.

When to use it
your scenario first stores the file, then decides which project or directory receives it, so both steps stay separate and easy to debug.
Watch out
map the storage reference returned by Create a Storage; without it the module has nothing to attach. Clean up leftovers afterwards with Delete a Storage.
Crowdin47

Search Directories

Search

In Make“Searches for directories or lists them all.”

Returns the folders of a Crowdin project, either filtered or all of them, so later modules know exactly where files belong.

When to use it
before uploading or moving content, you need to check whether a target directory already exists instead of creating a duplicate with Create a Directory.
Watch out
a search can return zero, one or several bundles (one item each). Every bundle runs the next modules once, and each run counts as an operation on your Make plan.
Crowdin48

Search Files

Search

In Make“Searches for files or lists them all.”

Lists the source files of a project, with or without a filter, giving you the file references that Get a File, Update a File or Download a Translated File expect.

When to use it
a scenario must act on a file whose name you know but whose Crowdin reference you do not.
Watch out
an empty result stops the chain for that run; plan that case before activating the scenario, for example by checking the result with Run once, the editor button that tests the scenario one time.
Crowdin49

Search Labels

Search

In Make“Searches for labels or lists them all.”

Pulls the labels defined in a project so your scenario can tag strings with the right one instead of guessing its identifier.

When to use it
you plan to run Assign a Label to the String and need the label reference first, or want to confirm a label exists before calling Create a Label.
Watch out
listing every label without a filter sends each one as a separate bundle downstream, which multiplies operations for nothing when only one is needed.
Crowdin50

Search Languages

Search

In Make“Searches for languages or lists them all.”

Brings back the languages Crowdin knows, which gives a scenario the codes it needs to target a translation, a progress check or a machine translation.

When to use it
a later module asks for a target language and you would rather map a value found by search than type a code by hand.
Watch out
run it with a filter; an unfiltered call can return a long list and trigger the following modules once per language.
Crowdin51

Search Project Builds

Search

In Make“Searches for project builds or lists them all.”

Finds the builds of a project, so you can track what was produced and hand it on.

When to use it
a release process needs to know whether a recent build exists before notifying the team or fetching translated files.
Watch out
despite the similar wording, it does not return translated text; for that, Search String Translations reads each translated string.
Crowdin52

Search Project Members

Search

In Make“Searches for projects members or lists them all.”

Lists who works on a Crowdin project, which lets a scenario reach the right translator or manager instead of a hardcoded person.

When to use it
you assign work with Create a Task or Update a Task and need a member reference taken from the project itself.
Watch out
each member found becomes a bundle, so a search without a filter runs the next module once per person on the project.
Crowdin53

Search Project Progress

Search

In Make“Searches for project progress or lists them all.”

Reports how far a project's translation has advanced, which turns Crowdin status into data you can post, store or act upon.

When to use it
a stakeholder wants the overall progress in a spreadsheet or chat channel, and nobody should have to open Crowdin to read it.
Watch out
Search Translation Progress sounds almost the same. Run both once on your project and keep the one whose bundles answer your question.
Crowdin54

Search Projects

Search

In Make“Searches for projects or lists them all.”

Retrieves the Crowdin projects your account can access, filtered or complete, which is often the first lookup of a scenario that works across several products.

When to use it
a scenario starts from a product name in another app and must find the matching Crowdin project before anything else happens.
Watch out
each project found becomes its own bundle, so a broad search runs everything downstream once per project; filter before you connect costly modules.
Crowdin55

Search Screenshots

Search

In Make“Searches for screenshots or lists them all.”

Gets the screenshots attached to a project, the visual context that helps translators see where a string appears on screen.

When to use it
you want to check whether a screenshot is already there before Add a Screenshot creates a duplicate, or tidy old ones with Delete a Screenshot.
Watch out
the search returns screenshot records, not image files ready for another app; use Get a Screenshot for the detail of one item.
Crowdin56

Search Storages

Search

In Make“Searches for storages or lists them all.”

Shows the files currently sitting in Crowdin storage, the holding area used before a file is attached to a project.

When to use it
a cleanup scenario needs to spot stored files that were never used, then pass them to Delete a Storage.
Watch out
storage is not project content; a file found here is not yet translatable until Upload a File from Storage places it in a project.
Crowdin57

Search String Comments (Issues)

Search

In Make“Searches for string comments and issues or lists them all.”

Collects comments and issues raised on strings, so questions from translators surface outside Crowdin where developers actually read them.

When to use it
you want a digest of open issues on a project sent to your ticketing tool, while Watch String Comment Events handles the new ones as they happen.
Watch out
comments and issues come back together, so read the bundles in Run once before mapping them to another app.
Crowdin58

Search Strings

Search

In Make“Searches for strings or lists them all.”

Looks up source strings in a project, returning each match as a bundle, which is the usual way to find the string you want to update, label or delete.

When to use it
another app gives you a text or key and your scenario needs the matching Crowdin string before calling Update a String.
Watch out
projects hold many strings; an unfiltered search floods the rest of the scenario and burns operations fast.
Crowdin59

Search String Translations

Search

In Make“Searches for string translations or lists them all.”

Fetches the translations recorded for strings, which lets you read, compare or export translated text without going through a file build.

When to use it
a scenario checks whether a string already has a translation in a language before calling Translate via Machine Translation or Create a String Translation.
Watch out
this is different from Search Project Builds, which deals with builds, not individual translations.
Crowdin60

Search Tasks

Search

In Make“Searches for tasks or lists them all.”

Returns the tasks of a project, giving your scenario the list of open or finished assignments to report on or update.

When to use it
you want to find the task linked to a job before Update a Task or Delete a Task, or to mirror tasks in a planning tool.
Watch out
for changes that should react at once, Watch Task Events is the instant trigger; a search only sees tasks when the scenario runs.
Crowdin61

Search Translation Progress

Search

In Make“Searches for translation progress or lists them all.”

Returns translation progress as data your scenario can compare, so a lagging part of the work stops hiding inside Crowdin.

When to use it
a release gate should only move forward when a given language is complete, and your scenario needs that figure to decide.
Watch out
progress comes back as several bundles when there are several items; aggregate them before sending a single summary message.
Need help

Need help automating Crowdin with Make?

A person reads every message.

FAQ

Crowdin and Make: common questions

01Is the Crowdin Make integration free?
Yes, Crowdin is a standard app, so its modules work from the Make Free plan. That plan limits you to 2 active scenarios, 15 minutes minimum between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. You still need an active Crowdin account on your side.
02What do you need to connect Crowdin to Make?
An active Crowdin account and a personal access token. In Crowdin, open your account settings, click API, then New token, and copy the token shown on screen. In Make, add any Crowdin module, click Create a connection, give it a name if you like, and paste the token. For modules marked instant, click Create a webhook first, then Create a connection. The same connection is reused by every Crowdin module afterwards.
03Do Crowdin triggers in Make fire in real time?
It depends on the trigger. Seven of the nine are instant: Watch File Events, Watch Project Events, Watch String Comment Events, Watch String Events, Watch Suggestion Events, Watch Task Events and Watch Translation Events, where Crowdin calls Make through a webhook as soon as something happens. The other two, Watch New Directory and Watch New Project, are scheduled: Make checks Crowdin on the scenario schedule, every 15 minutes by default, and down to 1 minute on paid plans.
04What if a Crowdin module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Crowdin API with the connection you already created, so a feature without a dedicated module is still within reach. You build the request yourself from the Crowdin API reference, then test it with Run once. The Crowdin page in the Make docs does not list specific quotas; it notes that its content is AI-generated and should be checked against Crowdin's own documentation.
05Should you use Make or n8n for Crowdin?
It depends on which tool your team already works in. On Make, Crowdin offers 70 modules, with 9 triggers, 46 actions and 15 searches, plus Make an API Call for the rest, all set up without code. Apps like Crowdin often have an n8n node as well, so check what that node covers against the modules you need. The n8n vs Make comparison linked above lays out criteria side by side without picking a winner for you.
Same platform

Other docs you might need on this stack.

Browse all integrations