The automated import and export feature lets you set up a smooth, hands-free content exchange between your Lokalise project and a third-party app of your choice. No need to manually trigger imports or exports—this process runs automatically for you.
Right now, this feature is available for these apps:
To get started, open your Lokalise project (Marketing and support type), go to the Content management tab, and click the cog icon (Automated settings) in the top menu to manage automated import and export.
If you’re working with a Web and mobile project, open the project and switch to the Apps tab instead. Find the app you want to configure automated import or export for, open it, and click the cog icon as shown in the screenshot above.
Automated import
You can turn automated import on or off under the Import tab:
View image
View image
Import languages — select one or more languages to include in the automated import process.
Overwrite updated translations — update existing keys linked to items on the third-party service with new values.
Skip key creation for empty translations — if checked, Lokalise will not create a translation key for empty items on the chosen third-party service.
Import references — import all references from the third-party service.
Tags — assign specific tags to the imported items.
Frequency — set how often the import process should run.
Content type — choose a saved filter with the items you want to import (find instructions on creating a custom filter below).
Special notes
When reviewing the activity log for an automated import, you might notice two separate entries for a single operation. This occurs because scheduled imports involve two distinct processes: a cache refresh and the actual import. In the screenshot below, the first entry corresponds to the cache refresh, while the second entry represents the import itself.
Automated export
You can turn automated export on or off under the Export tab:
View image
View image
Export languages — select one or more languages to include in the automated export process.
Don't export empty translations — skip empty translation items and don't export them to the third-party service.
Export references — export all references to the third-party service.
Frequency — set how often the export process should run.
Content type — choose a saved filter with the items you want to export (find instructions on creating a custom filter below).
Translation filter — choose which translations should be exported from Lokalise based on their review status. You can export only reviewed translations, only verified translations, or require both statuses. The exact filtering behavior depends on the connected app.
Contentful Native: Translation status filters are applied at the Contentful entry level. If any required translation for a localizable field or selected export language does not meet the selected status requirements, the entire Contentful entry is skipped. This also applies to LFC-generated segments. Learn more about translation status filtering in the Contentful Native documentation.
Once you have scheduled the import or export, the UI will update accordingly.
Creating a custom filter to narrow content for importing and exporting
Custom filters let you control which content is included in automated import and export. You can create a filter and use it to make sure that only content matching specific criteria is processed automatically.
To create a custom filter, open your Lokalise Marketing and support project and navigate to the Content management tab. If you’re using a Web and mobile project, open the project first and then select the app from the Apps tab. From there, add a new filter:
Adjust the filter criteria as needed, then click Save and apply. When prompted, give the filter a clear and recognizable name so it’s easy to reuse later.
Once the filter is ready, open the scheduled import or export settings. In the Content type dropdown, select your custom filter and save the changes.
From that point on, only content that matches the filter criteria will be automatically imported or exported, depending on the automation you’ve configured.