Resources · Make integration

RWS Language Cloud Make integrationAutomate RWS Language Cloud with Make.

What if a new translation request could open its own project? The RWS Language Cloud Make integration gives you 10 modules: 9 actions and 1 search. This page shows localization teams how to link their account and build a first scenario.

Try the RWS Language Cloud integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the RWS Language Cloud Make integration do?

The RWS Language Cloud Make integration lets a Make scenario (the automation you build, a chain of modules) open translation projects, send files, fetch deliverables and read project status in your Trados Cloud account. A module is one brick of that chain. You pick them in a visual editor, without writing code.

Requests that turn into projects. A form, a ticket or a row in another app starts the scenario. Create a Project opens the job, then Upload a File sends the source document, so nobody retypes the order by hand.

Deliverables that come back on their own. Once work is done, Download Translated File or Download Project Zip hands the output to the next module, which can store it or send it to the person who asked.

A project list someone actually reads. List Projects returns your projects as bundles (one item per project) and Get a Project reads one in detail, which is handy for a status report in another tool.

Keep the limits in mind. This app has no trigger, so RWS Language Cloud cannot wake Make up when a project changes: the scenario runs on the schedule you set, or starts from another app. The Make documentation for this app is also AI-generated and asks readers to check important details with RWS directly. Before you start, the Make review covers the editor and Make pricing explains how operations are counted. The same kind of app often has an n8n node as well; n8n vs Make lays out the criteria.

Connect

How do you connect RWS Language Cloud to Make?

  1. 01

    Prepare an application in RWS Language Cloud

    You need an active account on a supported Trados Cloud product with access to the Public API. In the account menu, open Integrations, then the Applications tab, click New Application, name it and choose a Service User.

  2. 02

    Copy the two credentials

    Tick your new application, click Edit and go to API Access. Copy the Client ID and the Client secret. If a callback URI is requested, paste https://www.integromat.com/oauth/cb/rws-language-cloud.

  3. 03

    Create the connection in Make

    Add any RWS Language Cloud module to your scenario and click Create a connection. A connection is your account linked to Make once, then reused by every module of the app. Name it if you like, paste the credentials and confirm.

First scenario

Your first scenario with RWS Language Cloud

GoalWhen a translation request lands in another app, Make opens a project in RWS Language Cloud and sends it the source file.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Start with the app where requests arrive, such as your form or ticketing tool, since RWS Language Cloud has no trigger.

  2. 02

    Add Create a Project

    Click the + to the right of the first module, search for RWS Language Cloud and pick Create a Project. Click Create a connection if you have not linked the account yet.

  3. 03

    Map the request data

    Fill the fields Make shows, using the data of the request from the first module. Once the connection exists, Make lists what it can read in your account, so you pick values instead of typing them.

  4. 04

    Send the file with Upload a File

    Add Upload a File after the project module and map the document received with the request. Use the project returned by the previous module wherever the fields ask for it.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Check in RWS Language Cloud that the project and its file are there before going further.

  6. 06

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that interval. Then switch the scenario on.

Modules

What can the RWS Language Cloud modules do?

RWS Language Cloud gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

RWS Language Cloud1

Add a Reference File

ActionIn the docs only

Attaches a reference document to a project, meaning material that accompanies the work rather than the text to translate. It keeps supporting documents in the same place as the job.

When to use it
a client sends a style guide alongside the order and you want it filed with that exact project.
Watch out
the documentation lists no fields for this module, so open it in the editor and see what Make asks for.
RWS Language Cloud2

Cancel Or Complete a Project

ActionIn the docs only

Closes a project from your scenario, either by cancelling it or by marking it complete. Your project list stays tidy without anyone clicking through the Trados Cloud interface.

When to use it
the request was withdrawn in your ticketing tool, or the deliverable has been accepted downstream.
Watch out
treat cancellation as final and test it on a dummy project with Run once first.
RWS Language Cloud3

Create a Project

ActionIn the docs only

Opens a new translation project in RWS Language Cloud from data coming out of another module. This is usually the heart of an intake scenario, since every other module works on a project.

When to use it
an order form, an email or a CRM record should become a job without retyping.
Watch out
run Project Creation Options beforehand if you are unsure which settings your account offers.
RWS Language Cloud4

Download Project Zip

ActionIn the docs only

Retrieves a whole project as one zip archive and passes it to the next module as a file. Handy when a job contains several documents and the recipient wants them all together.

When to use it
you archive finished projects in a shared drive or send a single package to the client.
Watch out
on the Free plan, files are capped at 5 MB, and an archive grows fast.
RWS Language Cloud5

Download Translated File

ActionIn the docs only

Fetches one translated document so another module can store it, email it or attach it to a record. You get the file itself, not a link to open by hand.

When to use it
each request produces one document and the requester only needs that one back.
Watch out
without a trigger, Make does not know when the translation is ready; check the project with Get a Project first.
RWS Language Cloud6

Get a Project

ActionIn the docs only

Reads the details of a single project you already know, and returns them as one bundle for the following modules to use in filters or messages.

When to use it
a scheduled scenario checks where a given job stands before downloading anything.
Watch out
it needs the project reference, so keep it from the module that created the project or from List Projects.
RWS Language Cloud7

List Projects

SearchIn the docs only

This is the only search module of the app: it returns your projects, one bundle each, so later modules run once per project. It fits reports and checks across the whole account.

When to use it
you copy every open project into a sheet your managers read.
Watch out
each bundle counts as operations in the modules after it, so filter early.
RWS Language Cloud8

Make an API Call

ActionIn the docs only

Calls any endpoint of the RWS Language Cloud API with the connection you already set up. It covers what the nine other modules leave out, without a separate login.

When to use it
you need an operation of the Public API that no listed module offers.
Watch out
you write the request yourself, so keep the RWS API reference open while you configure it.
RWS Language Cloud9

Project Creation Options

ActionIn the docs only

Judging by its name, it shows the choices your account offers when a project is created, so you know them before filling Create a Project. Treat it as a scouting step for your setup.

When to use it
you set up an intake scenario for the first time and want to know which values are valid.
Watch out
run it with Run once and read the bundle; the documentation does not describe the output.
RWS Language Cloud10

Upload a File

ActionIn the docs only

Sends a document from your scenario to RWS Language Cloud, taking the file from a previous module such as an email attachment or a form upload.

When to use it
the source text arrives as a file and must reach the translation team without someone downloading and re-uploading it.
Watch out
the Free plan limits files to 5 MB, which a large layout file can exceed.
Need help

Need help automating RWS Language Cloud with Make?

A person reads every message.

FAQ

RWS Language Cloud and Make: common questions

01Is the RWS Language Cloud Make integration free?
Yes, on the Make side. RWS Language Cloud is a standard app, available from the Free plan. That plan allows 2 active scenarios, 15 minutes minimum between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and count usage in credits each month. Your RWS subscription is a separate matter, handled with RWS.
02What do you need to connect RWS Language Cloud to Make?
An active account on a supported Trados Cloud product with access to the Public API. In that account you create an application under Integrations, then Applications, pick a service user, and copy the Client ID and the Client secret from the API Access page. In Make, you click Create a connection on any module of the app and enter those credentials. The connection is then shared by all modules of the app.
03Does the RWS Language Cloud integration react in real time?
No, because the app has no trigger module in Make. RWS Language Cloud cannot notify Make when a project changes. You have two options: start the scenario from another app that has a trigger, such as the tool where requests arrive, or let Make run it on a schedule, every 15 minutes by default. In the second case, List Projects or Get a Project reads the current state at each run.
04What if an RWS Language Cloud module is missing in Make?
Use Make an API Call. It reaches any endpoint of the RWS Language Cloud API with the connection you already have, so an operation not covered by the other nine modules is still within reach. You write the request yourself from the RWS API reference. Also note that the Make documentation for this app is AI-generated and asks readers to verify important details with RWS, so check behavior on a test project with Run once.
05Should you use Make or n8n for RWS Language Cloud?
It depends on the tool your team already runs. On Make, the integration offers 10 modules, including Make an API Call, a visual editor and a Free plan to test. Apps like this one often have an n8n node too, so compare the actions each tool exposes for your use case rather than the brand. When a step you need is missing from the list, Make an API Call reaches the rest of the RWS API with the same connection. The n8n vs Make comparison linked above details the other criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations