Integration
Connect Cling and Lokalise
When New Document fires in Cling, your agent runs Create a Task in Lokalise, or Contributor Added in Lokalise to Add project in Cling. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Cling and Lokalise to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Cling and Lokalise can do together
From Cling to Lokalise
When New Document in Cling
then Create a Task in Lokalise
When Document Accepted in Cling
then Create Comment in Lokalise
From Lokalise to Cling
When Contributor Added in Lokalise
then Add project in Cling
When Key Added in Lokalise
then Create Client in Cling
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Cling and Lokalise
Triggers and actions 21 triggers · 47 actions
Trigger
Document AcceptedTriggers when a Cling document is fully accepted (signed by all clients).
Trigger
Document DeniedTriggers when a client denies a Cling document.
Trigger
Document ExpiredTriggers when a Cling document passes its expiration date.
Trigger
Document SentTriggers when a Cling document is sent to its clients.
Trigger
New DocumentTriggers when a new document is created in Cling.
Action
Add projectCreates a new project in Cling to group documents.
Action
Add templateCreates a new document template in your Cling company.
Action
Create ClientCreates a new client (end customer) in Cling that documents can be sent to.
Action
Create DocumentCreates a new Cling document from a template for one signing client. The document is created as a draft; use Send Document to deliver it.
Action
Delete clientDeletes a client (end customer) from your Cling account.
Action
Delete DocumentDeletes a Cling document by its ID.
Action
Delete projectDeletes a project in Cling by its ID.
Action
Delete templateDeletes a template from your Cling account.
Action
Get clientReturns a single client (end customer) by its ID, including contact details, addresses and notes.
Action
Get DocumentReturns one Cling document by its ID, including its status and dates.
Action
Get projectReturns a single Cling project by its ID, including its status, totals, clients and main document summary.
Action
Get templateReturns a single Cling template by its ID.
Action
List ClientsReturns the clients (end customers) in your Cling account.
Action
List documentsReturns documents in your Cling account, optionally filtered by status or an advanced filter and sorted.
Action
List projectsReturns the projects in your Cling account, optionally filtered and sorted.
Action
List TemplatesReturns the document templates in your Cling account.
Action
Send DocumentSends an existing Cling document to its clients for signing.
Action
Update clientUpdates an existing client's details in Cling, such as name, contact information and addresses. Fields left blank are not changed.
Action
Update documentUpdates a Cling document's status or assigned company user. Only the values you fill in are changed.
Action
Update projectUpdates an existing project's name or status in Cling.
Action
Update templateRenames an existing Cling template.
Trigger
Contributor AddedTriggers when a new contributor is added to a Lokalise project.
Trigger
Contributor RemovedTriggers when a contributor is removed from the selected Lokalise project.
Trigger
Key AddedTriggers when a new translation key is added to a Lokalise project, whether individually or in bulk (import, API or bulk action). Fires once per added key.
Trigger
Key Comment AddedTriggers when someone adds a comment to a translation key in a Lokalise project.
Trigger
Key ModifiedTriggers when a translation key is modified in a Lokalise project, either individually or in bulk (renames, tag changes, file assignments, hiding).
Trigger
Key RemovedTriggers when one or more translation keys are removed from a Lokalise project, whether deleted individually, in bulk, through the API, or moved to another project. Fires once per removed key.
Trigger
Language AddedTriggers when one or more languages are added to a Lokalise project, firing once for each language added.
Trigger
Language RemovedTriggers when a language is removed from a Lokalise project.
Trigger
Poll TasksTriggers when a new task is created in a Lokalise project.
Trigger
Project ExportedTriggers when translation files are downloaded (exported) from a Lokalise project.
Trigger
Project ImportedTriggers when a translation file is uploaded to a Lokalise project. Fires once per uploaded file.
Trigger
Project SnapshotTriggers when a snapshot is taken of the selected Lokalise project.
Trigger
Task CreatedTriggers when a new translation or review task is created in a Lokalise project.
Trigger
Task DeletedTriggers when a task is deleted in a Lokalise project.
Trigger
Translation ReviewedTriggers when a translation is marked or unmarked as reviewed in a Lokalise project, individually or in bulk.
Trigger
Translation UpdatedTriggers when a translation is changed in the selected Lokalise project, either one at a time or several at once through a bulk action, file upload or the API.
Action
Add ContributorAdds a contributor to a Lokalise project, inviting them by email with the chosen languages and permissions.
Action
Add LanguagesAdds one or more languages to a Lokalise project, optionally overriding each language's code, name and plural forms.
Action
Create a KeyCreates a new translation key in a Lokalise project, optionally with its translations, tags, comments and screenshots, and returns the new key.
Action
Create a TaskCreates a translation, review or automatic-translation task in a Lokalise project for the chosen keys and languages.
Action
Create CommentAdds a comment to a translation key in a Lokalise project.
Action
Create ProjectCreates a new Lokalise project in your team, optionally with its languages, base language and project type. Returns the created project.
Action
Create SnapshotCreates a snapshot of a Lokalise project, saving its current state so it can be restored later.
Action
Delete a KeyDeletes a key, with its translations, from a Lokalise project.
Action
Delete a LanguageRemoves a language from a Lokalise project.
Action
Delete a TaskDeletes a task from a Lokalise project.
Action
Download FilesExports a Lokalise project's translation files as a .zip bundle and returns the download URL of the bundle.
Action
List All OrdersReturns all translation orders placed under a Lokalise team.
Action
List All TasksReturns the tasks in a Lokalise project, optionally filtered by title or status.
Action
List All TranslationsReturns the translation items of a Lokalise project (one row per key and language), optionally filtered by language, review status, QA issues or task.
Action
List Project LanguagesReturns the languages set up in a Lokalise project, with each language's code, name, direction and plural forms.
Action
List SnapshotsReturns the snapshots saved for a Lokalise project, with each snapshot's title and creation details.
Action
Remove ContributorRemoves a contributor from a Lokalise project.
Action
Retrieve a CommentReturns a single comment left on a key in a Lokalise project, including its text, author and when it was added.
Action
Retrieve a ContributorReturns a contributor of a Lokalise project, including their email, name, role flags, languages and permissions.
Action
Retrieve a KeyReturns one translation key from a Lokalise project, including its names, description, platforms, tags, comments, screenshots and translations.
Action
Retrieve a TaskReturns a Lokalise task, including its status, progress, due date and the languages and assignees it covers.
Action
Retrieve ProjectReturns a Lokalise project's details, including its name, type, base language, settings and translation statistics.
Action
Update a KeyUpdates an existing key in a Lokalise project, such as its name, description, platforms, tags or flags, and returns the updated key.
Action
Update a TranslationUpdates the text and review flags of a translation in a Lokalise project.
Action
Update LanguageUpdates a language in a Lokalise project, changing its code, name or plural forms.
Action
Upload FileUploads a localization file to a Lokalise project and queues it for import. Returns the queued import process so you can follow its status.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Cling
Cling to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cling to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cling to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cling to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Cling to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cling to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Lokalise
HubSpot to LokaliseHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LokaliseGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LokaliseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LokaliseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to LokaliseGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to LokaliseActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Cling and Lokalise, answered
What can start an automation from Cling?
Any of Cling's 5 triggers in the catalog, including New Document, Document Accepted, Document Denied and Document Expired. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Lokalise when something happens in Cling?
Any of Lokalise's 26 actions, including Create a Key, Create a Task, Create Comment and Create Project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Lokalise to Cling?
Yes. When something happens in Lokalise, your agent can act in Cling too. This page covers both directions: Lokalise's triggers and Cling's actions are listed here as well.
Do I have to build a connector for Cling or Lokalise?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Cling and Lokalise without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.