Below, we’ll guide you through setting up Google Drive and Transifex Zaps. However, the beauty of Zapier is that it’s flexible. You can use the supported triggers and actions to create similar Zaps connected to other services (e.g., HipChat or Box) or create something totally new.

Sending new files from Google Drive to Transifex

Suppose you store spreadsheets and documents you wish to translate on Google Drive. In that case, you can use Zapier to automatically upload new and updated files to Transifex while automatically sending completed translations back to Google Drive.

Please note that the procedure described here needs to be repeated for each directory in Google Drive or each project in Transifex. A single zap can be used to push multiple source files within the same Google Drive directory to Transifex.

Create a new Zap.
Choose Google Drive to trigger the zap whenever something happens there.
From the events list, choose the second option, "New File In Folder," as seen below:

Click "Continue" to proceed.
Connect your Google Drive Account

Press "Continue" to proceed.
Choose the Google Drive path containing the source files you want to upload to Transifex.

Press "Continue" to proceed and click 'Test the trigger' to ensure the criteria set are correct. After receiving the successful message, press "Continue" to move on to the next step.
Now, we will configure the Transifex side. Choose the latest version of Transifex when prompted to do so, as seen below:
From the events list, choose "Upload File":

Click "Continue" to proceed.
Connect your Transifex User Account - Your API token will be requested, so you must visit your settings page and generate it as described here.

Click "Continue" to proceed.
Select the organization you want to create a zap for and the project where the source content hosted in the specific Google Drive folder will be uploaded.

Then, provide values for the rest of the fields as shown below:

Click on the "Continue" button to proceed, then "Test Action" to confirm that everything is configured correctly. Once you receive a successful message, you can save the Zap and turn it on.
Troubleshooting:
- Be patient. When uploading a new file to Google Drive, the zap can take up to an hour to trigger.
- Please review the following guide if the file still hasn't been uploaded.

Manually triggering Zaps

You can manually trigger Zaps to avoid waiting up to 1 hour for automatic detection. Here's how it works for each scenario:

Creating new Transifex resources: Manual triggers work when files are created directly in or uploaded to Google Drive but not when files are moved between folders. Only the specific file that triggered the Zap will be processed.
Updating existing resources: When source files are updated in Google Drive, you can manually trigger the Zap to update the corresponding Transifex resources immediately.
Sending completed translations: Manual triggering isn't available for multi-step Zaps. Once you complete a translation, you must wait for automatic detection (typically a few minutes but may take up to an hour).

Updating Existing Resources in Transifex With Changes Detected in Google Drive

Please note that a zap needs to be created for each Google Drive directory or each Transifex project. However, a single zap can be used to push multiple updated files residing in the same Google Drive directory. As a prerequisite to this step, please create a Zap for "Sending new files from Google Drive to Transifex".

The AutoUpdate Resource feature can also accomplish the same functionality. The benefit of using Zapier is that your files do not need to be public. They can be private files that sit behind a secure login.

From within your Zapier Home Page, copy the Zap created in step "Sending new files from Google Drive to Transifex". To do this, find your Zap, click the down arrow button, and select copy as seen below:
Once the Zap is copied, click the down arrow button again to rename it. Then click on the zap to edit it.
Click on the Google Drive entry and modify the event from New File to Updated File as seen below:

Click "Continue" twice to proceed.
Customize the updated file parameters as seen below:

Click "Continue" to proceed.
Update a file on Google Drive and test to ensure the update is detected.

Click "Continue" to proceed.
Turn on the Zap if the test is successful.
Troubleshooting:
- Any source updates after turning on your zap may take up to 1 hour to trigger the zap.
- When a file is deleted in Google Drive, that file has to be deleted in Transifex either manually, through the CLI Client, or the API.

Sending Completed Translations From Transifex to Google Drive

Please note that a single zap is required for each directory in Google Drive or each project in Transifex. However, a single zap will upload translation files from multiple resources and language pairs. Manually triggering the zap is not an option for a multi-step zap. So, once you fully translate the language of a resource, then you will need to wait for Zapier to automatically identify the changes.

Create a new Zap.
Choose Transifex so that whenever something happens there, the zap will be triggered - Search for the latest version as seen below:
Select "Localization Activity Completed"

Click "Continue" to proceed.
Connect your TX User Account:

Click "Continue" to proceed.
Set up the trigger by selecting the organization you want to create this zap for and the project where the translations are hosted.

Then, define when the translations in your Google Drive folder will be updated:

You can select more than one event from the list:

Click "Continue" to proceed.
Click "Test trigger" to confirm that the zap was configured correctly. Once you receive a successful message, click "Continue" to proceed.
Add a new action. Find the latest version of the Transifex App and select it.
Select "Download file from Transifex" as the Action Event.

Press the "Continue" button to proceed.
Choose the account created/used in step 4 above. Press "Continue" to proceed.
In the "Set up action" section, populate the dropdowns as seen below:

Press "Continue" to proceed.
As an option, test the configuration to see if a file is downloaded. Keep in mind that this test will not return anything if you don't have any languages in your project that are 100% translated.

Click "Test Action" to proceed.
Add a new action for Google Drive. Find the "Google Drive" app and select it.
Select Upload file as Action event:

Press "Continue" to proceed.
Connect your Google Account and press "Continue" to proceed:
Customize the "Upload File" (i.e., translation file) as seen below and then press the "Continue" button to proceed:

Note that the "Filename" is customizable with a mix of text and predefined variables.

Please always use the predefined variables if you wish to use this zap for all the resources in a given project. The "Filename of the file:" parameter uses the resource slug of the source file. If you are unhappy with the resource slug, you can change it in Transifex.

⚠️Warning: To prevent translation files from syncing with your Transifex project as source files, please choose a different folder in Google Drive to store your translations from where you keep your source files.

Click "Continue," then "Test Action" to confirm a successful setup, and once you are done, turn on your zap.

Additional Reading

💡Tip

Looking for more help? Get support from our Transifex Community Forum!

Find answers or post to get help from Transifex Support and our Community.