--- title: "Connect Lokalise to Memberspot - APIANT.ai" description: "When \"Contributor Added\" fires in Lokalise, your agent runs \"Revoke Order Access\" in Memberspot." canonical: "https://apiant.ai/connect/lokalise-to-memberspot" --- # Connect Lokalise to Memberspot When **Contributor Added** fires in [Lokalise](https://apiant.ai/connections/lokalise), your agent runs **Revoke Order Access** in [Memberspot](https://apiant.ai/connections/memberspot). Describe the whole flow and it is built, tested on every scenario and kept running. Lokalise **16** triggers Lokalise **26** actions Memberspot **20** 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 Memberspot 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 can start in Memberspot - When **Contributor Added** in Lokalise then **Revoke Order Access** in Memberspot - When **Key Added** in Lokalise then **Enable Chapter Access by User Id** in Memberspot 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 Memberspot ## Triggers and actions 16 triggers · 46 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. - Action **Delete Access** Removes a user's access to an offer entirely, identified by the user's email address. - Action **Delete Order Access** Removes a user's access to every offer granted under a specific order ID, identified by the user's email. - Action **Delete User by User Id (POST)** Deletes up to 10 Memberspot users by their user IDs. Users not found in the school are skipped. - Action **Delete Users** Deletes up to 10 users from your Memberspot school by email address. - Action **Delete Users by User Id (DELETE Method)** Deletes up to 10 Memberspot users by their user IDs. Users not found in the school are skipped. - Action **Enable Chapter Access by User Id** Gives a member access to a specific chapter of a course, identified by their user ID. - Action **Find User by Mail** Finds a Memberspot user by their email address and returns their profile, active state and custom user properties. - Action **Find User by User Id** Returns the Memberspot user with the given user id, or found=false when no such user exists. - Action **Grant Access** Grants a user access to an offer by email address, creating the user if they don't exist yet. - Action **Grant User Access by User Id** Grants an existing Memberspot user access to an offer, identified by the user's id. - Action **Revoke Access** Revokes (deactivates) a user's access to an offer, identified by the user's email address. - Action **Revoke Order Access** Revokes (deactivates) a user's access to every offer granted under a given order ID, identified by the user's email. The access is kept but set inactive. - Action **Set Access Expires** Sets or removes the date a user's access to an offer expires. - Action **Set Access State by UserId** Sets whether a user's access to an offer is active or inactive, identified by the user's id. Leaving the state blank removes the offer from the user. - Action **Set Custom Property** Sets one custom user property on a Memberspot user identified by email, and returns the updated user. - Action **Set Custom User Property by Users Id** Sets the values of one or more custom properties on a Memberspot user, identified by user ID, and returns the updated user. - Action **Set Order State by Order Id** Sets the state of all offers with a given order ID across every user — activates, deactivates or removes them. - Action **Set Order State by User Id** Sets the active state of every offer a user holds under a given order ID, or removes that access when no state is given. - Action **Users Course Progress List by User Id** Returns the course progress of a Memberspot user, for every course they have, looked up by user ID. - Action **Users Course Progress List by User Id and Course Id** Returns a member's progress in one specific course, looked up by their user ID. ## 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) - [ **Memberspot** Memberspot is an online course and video-hosting platform.](https://apiant.ai/connections/memberspot) 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 Memberspot - [ **HubSpot to Memberspot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-memberspot) - [ **Salesforce to Memberspot** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-memberspot) - [ **Slack to Memberspot** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-memberspot) - [ **Google Sheets to Memberspot** Google Sheets](https://apiant.ai/connect/google-sheets-to-memberspot) - [ **Gmail to Memberspot** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-memberspot) - [ **Google Calendar to Memberspot** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-memberspot) Questions ## Lokalise and Memberspot, 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 Memberspot when something happens in Lokalise? Any of Memberspot's 20 actions, including Enable Chapter Access by User Id, Find User by Mail, Find User by User Id and Grant Access. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Memberspot to Lokalise? Memberspot has no triggers in the catalog today, so automations start in Lokalise. If you need the other direction, ask: your agent reads Memberspot's API documentation and adds it. ### ### Do I have to build a connector for Lokalise or Memberspot? 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 Memberspot 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.