You can integrate Langzy with other web apps via Zapier, a productivity tool designed for end users. Zapier can move data between web apps, you just need to design the workflows first.

As an example, a Zapier automation can pick up a Microsoft Word document you’ve just dropped into a Dropbox folder, and send it to Langzy for translation. It can also extract the body text of an email in a Gmail Inbox, and send back the translation to the requester.

This help article explains how you can automate translations with Langzy and Zapier. We assume that you have a basic understanding of the key concepts in Zapier

Prerequisites to automating translations

You’ll need the following accounts and keys:

  1. Register a Langzy account
    You’ll need a Professional plan or an active trial.

  2. Sign up to Zapier
    You’ll need a Starter plan or greater.

  3. Obtain the Langzy API key on the Settings / API key page:

You can obtain the Langzy API key on the

Langzy Translate app in Zapier

Langzy provides a Zapier app called Langzy Translate that you can integrate into your Zaps.

Langzy Translate supports the following Actions:

  • Request a Translation (Plain Text)
    Translates plain text with machine translation.

  • Request a File Translation
    Translates a file with machine translation.
    (This action runs in the background; you have to wait until it finishes)

  • Download Translated File by ID
    Downloads a translated file after Langzy has finished the translation. It’s recommended to wait at least 5 minutes before initiating download.

Langzy Translate supports three Actions: Request a translation (plain text), Request a File Translation, and Download Translated File by ID.

Langzy Translate doesn’t support Searches and Triggers. Zaps need to be triggered by other Apps, after which the Zap can perform Langzy actions.

Creating your Zap using the App directory

You can create your translation Zap by following these steps

1) Find your Trigger app on the Apps page:

The first step of creating a Zap is finding a trigger app on the

2) Search for Langzy Translate, and connect it to the Trigger app:

When creating a Zap, search for Langzy Translate, and connect it to the trigger app.

3) Select a Trigger and an Action, and press “Connect”:

Finish connecting the trigger app and Langzy Translate by selecting the trigger and the action.

4) Zapier creates a new Zap, and opens it in the Zap editor. The Trigger and first Action steps are populated automatically. You only need to configure these steps, and add more steps if neccessary:

Once the new Zap is created in the Zap editor, you can further configure the prepopulated trigger and action steps, or add new steps.

Creating your Zap using the Connect wizard

You can also create a Zap using the Connect wizard. It’s similar to creating a Zap on the Apps page.

1) Select the Apps you would like to connect on the Dashboard page:

You can also create a Zap by using Zapier's Connect wizard on the

2) Select a Trigger and an Action, and press the “Use Zap” button: 

Finish connecting the trigger app and Langzy Translate by selecting the trigger and the action.

3) Zapier creates a new Zap, and opens it in the Zap editor. The Trigger and first Action steps are populated automatically.you only need to configure these steps, and add more steps if neccessary: 

Once the new Zap is created in the Zap editor, you can further configure the prepopulated trigger and action steps, or add new steps.

Creating your Zap from scratch

You can also create your Zap from a blank state.

1) Press the “Make a Zap” button in the top-left corner of the Dashboard page:

You can also create a Zap from a blank state by pressing the

2) Find and select your Trigger app by searching for it: 

Find and select your Trigger app by searching for it.

3) Find and select Langzy as your first Action app by searching for it: 

Find and select Langzy Translate as your first action of your Zap.

4) Configure the Trigger and first Action steps, and add more steps if necessary. 

Setting up plain text translation

In order to translate plain text with Langzy, you need to set up a Langzy Action as follows:

1) Select the “Request a Translation (Plain text)” as the action event:

For setting up a plain text translation, select the

2) Select a Langzy account, or create a new one by clicking on the “Add a New Account” link:

Select a Langzy account, or create a new one by clicking on the “Add a New Account” link.

3) If you chose to add a new Langzy account, then enter the API key in the popup, and press “Yes, Continue”:

When adding a new Langzy account, you have to enter the Langzy API key.

 4) Select the source language (or leave it empty for automatically detecting the source language), target language, and the text to be translated. You can use data from Trigger or previous Actions: the “Request a Translation (Plain Text)” action exposes data that you can use in subsequent actions:

Configure your translation action: select the source language, target language, and the text to be translated. You can use data from Trigger or previous Actions.

The “Request a Translation (Plain Text)” action exposes data that you can use in subsequent actions:

  • Detected source language
    The language name in English

  • Detected source language code
    Two-letter source language code (eg. “en” for English)

  • Target language code
    Two-letter target language code (eg. “en” for English)

  • Translated Text

Setting up file translation

A file translation can be achieved by adding two Langzy actions to your Zap: 1) request a file translation, 2) download the translated file.

Configuring Zapier to request a file translation

You can initiate a file translation by configuring the “Request a File Translation” action as follows:

1) Select the “Request a File Translation” as the action event:

For setting up a file translation, select the

2)  Select a Langzy account, or create a new one by clicking on the “Add a New Account” link:

Select a Langzy account, or create a new one by clicking on the “Add a New Account” link.

3) Select the source language (or leave it empty for automatically detecting the source language), target language, and the file to be translated. You can use data from the Trigger or previous Actions:

Configure your translation action: select the source language, target language, and the file to be translated. You can use data from Trigger or previous Actions.

The “Request a File Translation” action exposes data that you can use in subsequent actions:

  • Translated file ID
    Use this identifier to download the translated file with the “Download Translated File by ID” action.

File translations run in the background. It’s recommended to wait 5 minutes before you initiate file download.

Configuring Zapier to download a translated file

You can download a translated file by using the “Download Translated File by ID” action as follows:

1) Select the “Download Translated File By ID” as action event:

For downloading the translated file, select the

2) Select a Langzy account, or create a new one by clicking on the “Add a New Account” link:

Select a Langzy account, or create a new one by clicking on the “Add a New Account” link.

3) Enter the ID of the translated file you’d like to download. You can use the exposed “Translated file ID” parameter exposed by the “Request File Translation” action:

Enter the ID of the translated file you’d like to download. You can use the exposed “Translated file ID” parameter exposed by the “Request File Translation” action.

The “Download Translated File by ID” action exposes data that you can use in subsequent actions:

  • Source file name
    File name without path and extension.

  • Source file extension
    File extension including the leading dot, eg. “.docx”.

  • Detected source language
    The language name in English

  • Detected source language code
    Two-letter source language code (eg. “en” for English)

  • Target language code
    Two-letter target language code (eg. “en” for English)

  • Translated file
    You can supply it as input parameter to file Actions.

Did this answer your question?