File Support

Article content is machine translated from English to other languages by Phrase Translate.

All supported actions save their results in a file that can be used by subsequent actions. Only files output from previous actions can be used (uploading of files is not supported).

All file formats returned by supported APIs can be used.

Use {{ @raw }} or {{ @file.path }} for referencing in subsequent actions.

Supported actions

  • Strings

    • Create a new screenshot

    • Upload a new file

  • TMS

    • Create job

    • Create segmentation rule

    • Download preview file

    • Download prepared file

    • Upload term base

    • Import TMX

    • Update source

    • Update target

    • Upload bilingual file

    • Upload a file to a subfolder of the selected connector

    • Upload handover file

Use case

The following workflow gets triggered when a locale inside a Phrase Strings job is marked completed. It downloads the locale as .json and imports it into a different project. This allows having a separate project, for example as a backup or an over-the-air specific one.


The locale’s .json export has a highly variable size. For smaller projects, it may only be a few lines, whereas for larger projects it can grow in length very quickly. By using the {{ @file.path }} reference, the export can be referenced without concerns for file size limitations.

Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question, submit a request to our Support team.
Thank you for your feedback.