Resources · Make integration

Language Weaver Make integrationAutomate Language Weaver with Make.

Can Make send your texts and files to Language Weaver without anyone copying and pasting? Yes: the Language Weaver Make integration gives you 21 action modules for translation, language detection and content insights. This guide shows how to connect your account and build a first working scenario.

Try the Language Weaver integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Language Weaver Make integration do?

The Language Weaver Make integration lets a Make scenario (the automation you build, a chain of modules) hand content to Language Weaver and bring the output back into your other tools. Each module is one brick of that chain; here all 21 are actions, which means they run when something earlier in the scenario feeds them.

Translated product copy, ready for the next tool. Picture a store that writes descriptions in English. A new description lands in another app, Translate Text sends it to Language Weaver, and Retrieve Translated Text brings the result back so the following module can store it.

Contracts routed by language. A legal team receives files from many countries. Identify the Language of a File starts the detection, Retrieve Language Identification Result collects the answer, and a filter in Make sends each file to the right reviewer. For short snippets, Synchronously Identify the Language of Text is the quicker option its name points to.

A usage check for the finance side. Get Translation Usage Report pulls consumption figures that a spreadsheet or chat module can then share with whoever tracks the budget.

What Make does not give you here: triggers. Language Weaver has no module that starts a scenario on its own, so another app or the schedule opens the flow. Make also warns that its documentation for this app is limited, so the fields shown in the editor are your reference. To weigh platforms, read our n8n vs Make comparison, the Make review, or the Make training if you prefer a guided start.

Connect

How do you connect Language Weaver to Make?

  1. 01

    Add a Language Weaver module

    In your scenario, search for Language Weaver, pick any of its modules, then click Create a connection. A connection is your Language Weaver account linked to Make once and reused by every module of the app.

  2. 02

    Name the connection

    Giving it a name is optional, but it helps once you run several accounts, for example a test workspace next to the production one. Pick something your colleagues will recognize in the list later.

  3. 03

    Authorize and save

    Either approve Make on the Language Weaver page that opens, or paste the key Language Weaver gives you, depending on what the window asks. Then click Save and the module is ready to fill.

First scenario

Your first scenario with Language Weaver

GoalWhen a new text shows up in another app, Make sends it to Language Weaver with Translate Text.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Language Weaver has no trigger, this first module comes from the app where your texts live.

  2. 02

    Choose the starting app

    Search that app, pick the module that catches new items and connect your account. Make lists what it can read once the connection exists, so you point it at the right place without typing paths.

  3. 03

    Add Translate Text

    Click the + on the right of the first module, search Language Weaver and select Translate Text. Map the text coming from the previous module, a bundle being one item passed along the chain.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles each module received, so you can read exactly what Language Weaver sent back before going further.

  5. 05

    Schedule and switch on

    Set the clock on the first module, which checks every 15 minutes by default, then switch the scenario on. Each module execution counts as one operation on your Make plan.

Modules

Everything the Language Weaver modules can do

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

Language Weaver1

Cancel Translation

ActionIn the docs only

Stops a translation you already sent to Language Weaver, so the service does not keep working on content that no longer matters.

When to use it
a client withdraws a document after your scenario passed it to Translate a File, and a branch of the flow needs to call the job off.
Watch out
open the module and check which identifier it wants; map it from the module that started the translation.
Language Weaver2

Check Content Insights Status

ActionIn the docs only

Tells you where a content insights request stands, which saves your scenario from asking for a result that is not ready yet.

When to use it
right after one of the Create Content Insights modules, before Get Content Insights Result, so a router or filter can wait for the right moment.
Watch out
each check is one operation, so avoid loops that ask again and again.
Language Weaver3

Check Language Identification Status

ActionIn the docs only

Returns the progress of a language detection you launched, so the next step only runs once Language Weaver has an answer to give.

When to use it
after Identify the Language of a File or Identify the Language of Text, when a large document may take a while before the result can be read.
Watch out
map the identifier from the module that started the detection, not from the source app.
Language Weaver4

Check Translation Status

ActionIn the docs only

Gives you the current state of a translation job, the signal your scenario needs before fetching anything from Language Weaver.

When to use it
between Translate a File and Retrieve Translated File, especially for long documents, so the retrieval does not fire too early.
Watch out
Make documents little about the possible statuses here; run the scenario once and read the bundle to see the values before you filter on them.
Language Weaver5

Create Content Insights for a File

ActionIn the docs only

Asks Language Weaver to analyze a file you pass in, a way to learn something about a document before deciding what to do with it.

When to use it
a file arrives from cloud storage or email and you want its insights attached to the record before any translation is ordered.
Watch out
on the Free plan, Make handles files up to 5 MB, so larger documents need a paid plan.
Language Weaver6

Create Content Insights for an Existing Translation

ActionIn the docs only

Runs the same analysis on a translation that already exists in Language Weaver, so you review what came out instead of the source.

When to use it
after Check Translation Status reports a finished job, to give a reviewer extra context on the translated version before it goes out.
Watch out
it works from a translation, so map the reference returned by the module that created that job.
Language Weaver7

Create Feedback

ActionIn the docs only

Sends your remarks on a translation back to Language Weaver, turning a reviewer's correction into something the service receives instead of a note lost in a chat.

When to use it
a proofreader flags a sentence in a form or a ticket, and the scenario forwards that comment automatically.
Watch out
Make gives no detail on what the feedback changes on the Language Weaver side, so treat it as a report, not a fix.
Language Weaver8

Get Active Language Pairs

ActionIn the docs only

Lists the source and target language combinations available on your account, which spares you a failed request toward a pair you do not have.

When to use it
at the start of a scenario that picks the target language dynamically, so a filter can stop before Translate Text if the pair is missing.
Watch out
the list depends on your account, so a colleague's connection may return something different.
Language Weaver9

Get Content Insights Result

ActionIn the docs only

Fetches the finished analysis so later modules can store it, share it or use it to route the document.

When to use it
once Check Content Insights Status says the work is done, to write the insights into a spreadsheet row or a project card.
Watch out
calling it before the analysis ends is likely to return nothing useful, so keep the status check in front.
Language Weaver10

Get Self for API Credentials

ActionIn the docs only

Returns information about the credentials your connection uses, handy to confirm which access Make is actually running with.

When to use it
when several teams share scenarios and you want a quick control step that proves the right credentials are plugged in before a batch of translations.
Watch out
the output may describe your access, so avoid sending it to a public channel.
Language Weaver11

Get Translation Usage Report

ActionIn the docs only

Pulls a usage report from Language Weaver, the data a manager needs to see how much translation the team consumes.

When to use it
feed a budget spreadsheet or a message to the finance lead whenever a new project closes, without anyone logging in to export figures.
Watch out
read the fields proposed in the module to set the period; Make documents none of them for this app.
Language Weaver12

Get User Self

ActionIn the docs only

Retrieves the profile of the user behind the connection, a simple way to know whose account a scenario acts for.

When to use it
as the first test after creating a connection, since it reads the account behind the connection, a Run once on it quickly shows whether the link to Language Weaver works.
Watch out
it differs from Get Self for API Credentials, which describes the credentials rather than the person.
Language Weaver13

Identify the Language of Text

ActionIn the docs only

Starts a language detection on a piece of text, useful when messages reach you in languages you cannot predict.

When to use it
support tickets arrive from several countries and each one has to land with the agent who speaks the language.
Watch out
this version seems to work as a request followed by a separate retrieval, so pair it with Retrieve Language Identification Result or use the synchronous module for short texts.
Language Weaver14

Identify the Language of a File

ActionIn the docs only

Detects the language of a whole document, so you can sort files without opening them.

When to use it
a shared folder fills with contracts or manuals in mixed languages and each file must reach the right reviewer or translation queue.
Watch out
follow it with Check Language Identification Status and then Retrieve Language Identification Result, and remember the 5 MB file limit of the Free plan.
Language Weaver15

Make an API Call

ActionIn the docs only

Opens the whole Language Weaver API to your scenario, with the connection you already set up, so any endpoint becomes reachable even without a dedicated module.

When to use it
the 21 listed modules do not cover an operation your process needs, and you have the Language Weaver API reference at hand.
Watch out
you write the request yourself, path and body included, so test it with Run once before relying on it.
Language Weaver16

Retrieve Language Identification Result

ActionIn the docs only

Collects the detected language once the identification is finished, the piece you need to route or tag the content.

When to use it
after Identify the Language of a File or of Text, to write the language into a CRM field or choose the next branch of a router.
Watch out
place Check Language Identification Status before it so the scenario does not ask too early.
Language Weaver17

Retrieve Translated File

ActionIn the docs only

Downloads the translated document so the next module can save it, email it or attach it to a record.

When to use it
the last Language Weaver step of a document flow, just before a storage module files the translation next to the original.
Watch out
the file travels through Make, so its size counts toward your plan's data transfer, 512 MB on the Free plan.
Language Weaver18

Retrieve Translated Text

ActionIn the docs only

Brings back the translated text so you can map it into any other app, whether that is a CMS field, a reply or a sheet cell.

When to use it
after Translate Text, whenever the scenario needs the translation itself to publish or store it somewhere else.
Watch out
run the scenario once and look at the bundle to find which item holds the translation before mapping it.
Language Weaver19

Synchronously Identify the Language of Text

ActionIn the docs only

Returns the language of a text in the same step, so no status check or second module is needed afterward.

When to use it
short inputs like chat messages, form answers or email subjects, where a direct answer keeps the scenario shorter and cheaper in operations.
Watch out
for full documents, the file module and its retrieval chain remain the route to take.
Language Weaver20

Translate Text

ActionIn the docs only

Sends a piece of text to Language Weaver for translation, the everyday building block of this integration.

When to use it
a product description, a review or a ticket enters Make from another app and has to exist in a second language.
Watch out
check the pair with Get Active Language Pairs if the target varies, and read the Run once output to see whether the translation comes back directly or through Retrieve Translated Text.
Language Weaver21

Translate a File

ActionIn the docs only

Submits a complete document for translation, keeping the workflow inside Make from the moment a file appears.

When to use it
a manual, a contract or a presentation lands in cloud storage and the translated version must follow without anyone uploading it by hand.
Watch out
the translated file is collected separately with Retrieve Translated File, and Free plan scenarios stop after 5 minutes of execution.
Need help

Need help automating Language Weaver with Make?

A person reads every message.

FAQ

Language Weaver and Make: common questions

01Is the Language Weaver Make integration free?
Yes, on the Make side. Language Weaver is a standard app, available from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Your Language Weaver subscription is a separate matter that Make does not cover.
02What do you need to connect Language Weaver to Make?
An active Language Weaver account and a Make account. Make's documentation lists no special prerequisite for this app. You add any Language Weaver module, click Create a connection, optionally name it, then either authorize Make on the Language Weaver page or paste the key your account provides, and save. The connection is created once and every Language Weaver module in your scenarios reuses it. Because Make describes its own documentation for this app as limited, rely on the hints shown in the connection window.
03Does Language Weaver trigger a Make scenario in real time?
No, because Language Weaver has no trigger in Make: all 21 modules are actions. A scenario therefore starts elsewhere. Either another app's trigger opens the flow, for example a new file in storage or a new form entry, and Language Weaver modules follow it; or the scenario runs on its schedule, every 15 minutes by default and never more often than every 15 minutes on the Free plan. Paid plans allow a schedule down to 1 minute.
04What if a Language Weaver module is missing in Make?
Use the Make an API Call module. It reaches any endpoint of the Language Weaver API with the connection you already have, so an operation without a dedicated module is still possible, provided you write the request yourself from the Language Weaver API documentation. It helps to know that Make currently says it cannot provide complete documentation for this app, so the modules show few explanations; testing each step with Run once is the reliable way to see what comes back.
05Should you use Make or n8n for Language Weaver?
It depends on how you prefer to work, and this page only documents Make. On Make, Language Weaver offers 21 ready modules covering translation, language detection, content insights and usage reports, plus Make an API Call for the rest, and the app is usable from the Free plan. Many apps also have an n8n node, so check whether one exists for Language Weaver and compare the operations each tool exposes for your own process before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations