The connector reads every team the configured API token can see, then each
team’s users and user groups. Team membership carries the user’s team role
(owner, admin, biller, or member) as a profile attribute, and group
membership comes from the member list on each group.
User groups are available on Lokalise Pro and Enterprise plans. On teams
whose plan does not include groups, the connector simply syncs no groups
for that team — users and team membership still sync normally.
Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Integrations > Connectors and click Add connector.
2
Search for Lokalise and click Add.
3
Choose how to set up the new Lokalise connector.
4
Set the owner for this connector.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Enter the Lokalise credentials:
Lokalise API token: the read-only API token you copied
from your personal profile.
Lokalise API base URL: enter
https://api.lokalise.com/api2 — Lokalise’s hosted service
is always at this address.
8
Click Save.
9
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Done. Your Lokalise connector is now pulling access data into C1.
Follow these instructions to run the Lokalise connector in your own
environment.
1
Create a secret for the Lokalise API token.
2
Configure the connector environment variables:
BATON_LOKALISE_API_TOKEN: the read-only API token you
copied from your personal profile.
BATON_BASE_URL: https://api.lokalise.com/api2 —
Lokalise’s hosted service is always at this address.
3
Deploy the connector using your standard self-hosted connector process.
Done. Your Lokalise connector is now pulling access data into C1.
Lokalise limits each API token to 6 requests per second. The connector
stays inside this budget by syncing with low concurrency and retrying
rate-limited requests, so large teams may take a little longer to sync.