Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Lokalise

Lokalise is a collaborative translation platform.

CategoryDeveloper Tools
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Lokalise with Flows360

Lokalise is a collaborative translation platform.

Use the Lokalise connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 12 actions and 3 triggers.

Available actions

  • Create Comment
  • Create Key
  • Create Project
  • Create Task
  • Delete Key
  • Retrieve a comment
  • Retrieve a key
  • Retrieve a project
  • Plus 4 additional declared actions.

Available triggers

  • Key Added
  • Key Updated
  • Translation Updated

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Lokalise
  • Package: @activepieces/piece-lokalise@0.1.0
  • Exact artifact digest: sha256:44156ec6e8be0ef2365f1b837c949398fe53f40c486f58f3ffd4fc197f7d03af
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Comment (createComment), Add comments to a key in your Lokalise project Classification: read.
  • Create Key (createKey), Create one or more keys in your Lokalise project Classification: read.
  • Create Project (createProject), Create a new project in your Lokalise team Classification: read.
  • Create Task (createTask), Create a new task in your Lokalise project Classification: read.
  • Delete Key (deleteKey), Delete a key from your Lokalise project (software and marketing projects only) Classification: read.
  • Retrieve a comment (retrieveAComment), Retrieve a specific comment on a key in your Lokalise project Classification: read.
  • Retrieve a key (retrieveAKey), Retrieve detailed information about a specific key in your Lokalise project Classification: read.
  • Retrieve a project (retrieveAProject), Retrieve detailed information about a Lokalise project Classification: read.
  • Retrieve Translation (retrieveTranslation), Retrieve a specific translation from your Lokalise project Classification: read.
  • Update Key (updateKey), Update properties of a key in your Lokalise project Classification: read.
  • Update Translation (updateTranslation), Update a translation in your Lokalise project Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Key Added, polling.
  • Key Updated, polling.
  • Translation Updated, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects15
Supported actionsNot published
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Comment Yes No Add comments to a key in your Lokalise project
Create Key Yes No Create one or more keys in your Lokalise project
Create Project Yes No Create a new project in your Lokalise team
Create Task Yes No Create a new task in your Lokalise project
Delete Key Yes No Delete a key from your Lokalise project (software and marketing projects only)
Retrieve a comment Yes No Retrieve a specific comment on a key in your Lokalise project
Retrieve a key Yes No Retrieve detailed information about a specific key in your Lokalise project
Retrieve a project Yes No Retrieve detailed information about a Lokalise project
Retrieve Translation Yes No Retrieve a specific translation from your Lokalise project
Update Key Yes No Update properties of a key in your Lokalise project
Update Translation Yes No Update a translation in your Lokalise project
Custom API Call Yes No Make a custom API call to a specific endpoint
Key Added Yes No polling trigger declared by the pinned package.
Key Updated Yes No polling trigger declared by the pinned package.
Translation Updated Yes No polling trigger declared by the pinned package.

Triggers

Key Added · Poll

Trigger when a new key is added to your Lokalise project

Inputs

  • projectId · string
Key Updated · Poll

Trigger when a key is updated in your Lokalise project

Inputs

  • projectId · string
Translation Updated · Poll

Trigger when a translation is updated in your Lokalise project

Inputs

  • projectId · string

Setup

Setup

  1. Add the Lokalise connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-lokalise@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 12 actions and 3 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Lokalise connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-lokalise@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com