Capabilities
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.
Gather Lokalise credentials
1
Sign in to Lokalise as a team owner or admin.
2
Open your personal profile and go to the API tokens section.
3
Generate a read-only API token and copy it.
Configure the Lokalise connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your Lokalise connector is now pulling access data into C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Lokalise and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
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.
9
Click Save.
10
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
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.