--- title: "Connect Lokalise and Ninety - APIANT.ai" description: "When \"Contributor Added\" fires in Lokalise, your agent runs \"Create Issue\" in Ninety, or \"New Issue Created\" in Ninety to \"Create a Task\" in Lokalise." canonical: "https://apiant.ai/connect/lokalise-to-ninety" --- # Connect Lokalise and Ninety When **Contributor Added** fires in [Lokalise](https://apiant.ai/connections/lokalise), your agent runs **Create Issue** in [Ninety](https://apiant.ai/connections/ninety), or **New Issue Created** in Ninety to **Create a Task** in Lokalise. Describe the whole flow and it is built, tested on every scenario and kept running. Lokalise **16** triggers Lokalise **26** actions Ninety **4** triggers Ninety **21** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Lokalise and Ninety to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Lokalise and Ninety can do together ### From Lokalise to Ninety - When **Contributor Added** in Lokalise then **Create Issue** in Ninety - When **Key Added** in Lokalise then **Update Issue** in Ninety ### From Ninety to Lokalise - When **New Issue Created** in Ninety then **Create a Task** in Lokalise - When **New Measurable** in Ninety then **Create Comment** in Lokalise 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 Lokalise and Ninety ## Triggers and actions 20 triggers · 47 actions - Trigger **Contributor Added** Triggers when a new contributor is added to a Lokalise project. - Trigger **Contributor Removed** Triggers when a contributor is removed from the selected Lokalise project. - Trigger **Key Added** Triggers 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 Added** Triggers when someone adds a comment to a translation key in a Lokalise project. - Trigger **Key Modified** Triggers when a translation key is modified in a Lokalise project, either individually or in bulk (renames, tag changes, file assignments, hiding). - Trigger **Key Removed** Triggers 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 Added** Triggers when one or more languages are added to a Lokalise project, firing once for each language added. - Trigger **Language Removed** Triggers when a language is removed from a Lokalise project. - Trigger **Poll Tasks** Triggers when a new task is created in a Lokalise project. - Trigger **Project Exported** Triggers when translation files are downloaded (exported) from a Lokalise project. - Trigger **Project Imported** Triggers when a translation file is uploaded to a Lokalise project. Fires once per uploaded file. - Trigger **Project Snapshot** Triggers when a snapshot is taken of the selected Lokalise project. - Trigger **Task Created** Triggers when a new translation or review task is created in a Lokalise project. - Trigger **Task Deleted** Triggers when a task is deleted in a Lokalise project. - Trigger **Translation Reviewed** Triggers when a translation is marked or unmarked as reviewed in a Lokalise project, individually or in bulk. - Trigger **Translation Updated** Triggers 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 Contributor** Adds a contributor to a Lokalise project, inviting them by email with the chosen languages and permissions. - Action **Add Languages** Adds one or more languages to a Lokalise project, optionally overriding each language's code, name and plural forms. - Action **Create a Key** Creates a new translation key in a Lokalise project, optionally with its translations, tags, comments and screenshots, and returns the new key. - Action **Create a Task** Creates a translation, review or automatic-translation task in a Lokalise project for the chosen keys and languages. - Action **Create Comment** Adds a comment to a translation key in a Lokalise project. - Action **Create Project** Creates a new Lokalise project in your team, optionally with its languages, base language and project type. Returns the created project. - Action **Create Snapshot** Creates a snapshot of a Lokalise project, saving its current state so it can be restored later. - Action **Delete a Key** Deletes a key, with its translations, from a Lokalise project. - Action **Delete a Language** Removes a language from a Lokalise project. - Action **Delete a Task** Deletes a task from a Lokalise project. - Action **Download Files** Exports a Lokalise project's translation files as a.zip bundle and returns the download URL of the bundle. - Action **List All Orders** Returns all translation orders placed under a Lokalise team. - Action **List All Tasks** Returns the tasks in a Lokalise project, optionally filtered by title or status. - Action **List All Translations** Returns 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 Languages** Returns the languages set up in a Lokalise project, with each language's code, name, direction and plural forms. - Action **List Snapshots** Returns the snapshots saved for a Lokalise project, with each snapshot's title and creation details. - Action **Remove Contributor** Removes a contributor from a Lokalise project. - Action **Retrieve a Comment** Returns a single comment left on a key in a Lokalise project, including its text, author and when it was added. - Action **Retrieve a Contributor** Returns a contributor of a Lokalise project, including their email, name, role flags, languages and permissions. - Action **Retrieve a Key** Returns one translation key from a Lokalise project, including its names, description, platforms, tags, comments, screenshots and translations. - Action **Retrieve a Task** Returns a Lokalise task, including its status, progress, due date and the languages and assignees it covers. - Action **Retrieve Project** Returns a Lokalise project's details, including its name, type, base language, settings and translation statistics. - Action **Update a Key** Updates an existing key in a Lokalise project, such as its name, description, platforms, tags or flags, and returns the updated key. - Action **Update a Translation** Updates the text and review flags of a translation in a Lokalise project. - Action **Update Language** Updates a language in a Lokalise project, changing its code, name or plural forms. - Action **Upload File** Uploads a localization file to a Lokalise project and queues it for import. Returns the queued import process so you can follow its status. - Trigger **New Issue Created** Triggered when a new issue is created in Ninety, optionally only on one team or only short-term vs long-term issues. - Trigger **New Measurable** Triggered when a new measurable (KPI) is added to your Ninety scorecard, optionally only those tracked over a given period like weekly or monthly. - Trigger **New Team** Triggered when a new team is created in your Ninety company. - Trigger **To-Do Created, Updated, or Deleted** Triggered when a to-do is created or changed in Ninety — including being completed or archived — optionally only on one team or only personal to-dos. Ninety's API does not report hard deletions, so a removed to-do simply stops appearing rather than firing this trigger. - Action **Create Issue** Creates an issue on a Ninety team's issues list. - Action **Create Milestone** Creates a milestone on a Ninety rock, with a title and due date. - Action **Create Rock** Creates a rock (a quarterly goal) for a Ninety team, with a due date, status and level. - Action **Create To-Do** Creates a to-do on a Ninety team, with a due date and optional description. - Action **Delete Issue** Deletes an existing Issue in Ninety by its ID. - Action **Delete Measurable Note** Deletes the note on a Measurable for one scorecard period. - Action **Delete Measurable Score** Deletes the score on a Measurable for one scorecard period. - Action **Delete Rock** Deletes a Rock in Ninety by its ID. Returns the deleted Rock's ID along with the status Ninety returned. - Action **Delete To-Do** Deletes a to-do in Ninety by its ID. Use it to remove a to-do that was created by mistake or is no longer needed. - Action **Find Issue** Searches Ninety for issues matching the words you provide, optionally narrowed to one team or to short-term vs long-term issues. Returns the matching issues. - Action **Find Measurable** Searches Ninety's scorecard for measurables (KPIs) matching the words you provide, optionally limited to a tracking period like weekly or monthly. Returns the matching measurables. - Action **Find Milestone** Searches Ninety for milestones by title. Ninety carries milestones on their rocks, so this reads the rocks (optionally just one team's) and returns the milestones whose title matches, optionally limited to a single rock. - Action **Find Rock** Searches Ninety for rocks (quarterly goals) matching the words you provide, optionally narrowed to one team or one status. Returns the matching rocks. - Action **Find Team** Returns the teams in your Ninety company, optionally only those whose name contains the words you provide. Use it to get the team ID other Ninety actions need. - Action **Find To-Do** Searches Ninety for to-dos matching the words you provide, optionally narrowed to one team, to personal to-dos, or to finished vs open ones. Returns the matching to-dos. - Action **Update Issue** Changes an existing issue in Ninety — its title, detail, team, priority, short-term/long-term setting, or whether it is solved. Fields you leave blank are left as they are. - Action **Update Measurable Note** Saves the note on a Ninety scorecard measurable for one period, replacing any note already there. - Action **Update Measurable Score** Records the score on a Ninety scorecard measurable for one period, replacing any score already there. - Action **Update Milestone** Changes an existing milestone in Ninety — its title, detail, due date, owner, or whether it is finished. Fields you leave blank are left as they are. - Action **Update Rock** Changes an existing rock (quarterly goal) in Ninety — its title, detail, status, owner, team, quarter, due date, or whether it is archived. Fields you leave blank are left as they are. - Action **Update To-Do** Changes an existing to-do in Ninety — its title, detail, due date, owner, team, repeat setting, or whether it is done or archived. Fields you leave blank are left as they are. ## Each app on its own - [ **Lokalise** Lokalise is a translation management tool that lets you structure and automate workflows while encouraging...](https://apiant.ai/connections/lokalise) - [ **Ninety** Ninety is a platform that helps organizations execute their strategies by aligning goals, managing tasks...](https://apiant.ai/connections/ninety) Reviews ## What our customers say ## More from Lokalise - [ **Lokalise to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/lokalise-to-salesforce) - [ **Lokalise to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/lokalise-to-slack) - [ **Lokalise to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/lokalise-to-mailchimp) - [ **Lokalise to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/lokalise-to-stripe) - [ **Lokalise to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/lokalise-to-shopify) - [ **Lokalise to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/lokalise-to-quickbooks-online) ## More into Ninety - [ **HubSpot to Ninety** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-ninety) - [ **Google Sheets to Ninety** Google Sheets](https://apiant.ai/connect/google-sheets-to-ninety) - [ **Gmail to Ninety** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-ninety) - [ **Google Calendar to Ninety** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-ninety) - [ **Google Drive to Ninety** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-ninety) - [ **Mailchimp to Ninety** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-ninety) Questions ## Lokalise and Ninety, answered ### ### What can start an automation from Lokalise? Any of Lokalise's 16 triggers in the catalog, including Contributor Added, Contributor Removed, Key Added and Key Comment Added. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Ninety when something happens in Lokalise? Any of Ninety's 21 actions, including Create Issue, Create Milestone, Create Rock and Create To-Do. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Ninety to Lokalise? Yes. When something happens in Ninety, your agent can act in Lokalise too. This page covers both directions: Ninety's triggers and Lokalise's actions are listed here as well. ### ### Do I have to build a connector for Lokalise or Ninety? 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 Lokalise and Ninety 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.