---
title: "Connect Lokalise to ManyRequests - APIANT.ai"
description: "When \"Contributor Added\" fires in Lokalise, your agent runs \"Add invoice\" in ManyRequests."
canonical: "https://apiant.ai/connect/lokalise-to-manyrequests"
---

# Connect Lokalise to ManyRequests

When **Contributor Added** fires in [Lokalise](https://apiant.ai/connections/lokalise), your agent runs **Add invoice** in [ManyRequests](https://apiant.ai/connections/manyrequests). Describe the whole flow and it is built, tested on every scenario and kept running.

Lokalise **16** triggers Lokalise **26** actions ManyRequests **27** 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 ManyRequests 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 ManyRequests

- When **Contributor Added** in Lokalise then **Add invoice** in ManyRequests
- When **Key Added** in Lokalise then **Create Client** in ManyRequests

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 ManyRequests

## Triggers and actions 16 triggers · 53 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

**Add invoice**

Adds a new invoice for a client from catalog services, pricing variations or custom line items, and returns the new invoice's id. The invoice is emailed to the client unless it is created as a draft.

- Action

**Add organization**

Creates a new organization in your ManyRequests portal along with its owner client user. Returns the organization that was added.

- Action

**Add organization member**

Adds a member to an organization, creating a new client user if no user with that email exists yet.

- Action

**Add subscription to organization**

Adds a recurring service subscription to a client organization and returns the new subscription.

- Action

**Add time entry**

Logs time worked on a request for a team member, from a start time to an end time.

- Action

**Cancel Client Subscription**

Cancels an active recurring service subscription belonging to a client organization.

- Action

**Create Client**

Creates a client user in a ManyRequests organization. If a user with the email already exists, they are added to the organization.

- Action

**Create Comment**

Adds a comment to a request, posted as the chosen user, optionally internal-only or scheduled for later delivery.

- Action

**Create organization brand**

Creates a new brand within an organization.

- Action

**Create Request**

Creates a new service request for a client under one of your services, with an optional description, priority, status, due date, brand, assignees and tags.

- Action

**Delete client**

Deletes a client and removes them from their organization. A client who is the sole owner of an organization with active subscriptions cannot be deleted.

- Action

**Delete organization**

Deletes an organization and all of its members from your ManyRequests portal.

- Action

**Delete request**

Deletes a request in ManyRequests.

- Action

**Find Comments for Request**

Returns the comments on a ManyRequests request, optionally limited to internal or non-internal comments.

- Action

**Find Organization**

Finds organizations whose name, owner name or owner email matches the search text, optionally narrowed by tags or subscription status.

- Action

**Find Request**

Returns the service requests that match your search text or filters, such as status, priority, client, organization, assignee or request number.

- Action

**Get client**

Returns a single client by ID, including their name, email and organization.

- Action

**Get invoice**

Returns a single invoice with its status, number, notes, payment details and dates, optionally with its line items, taxes, client, coupon and payment gateway.

- Action

**Get organization**

Returns a single organization by its ID, with its name, logo and dates, plus any related records you ask to include. An error occurs if the organization is not found.

- Action

**Get request**

Returns a single service request by its ID or slug, with optional related records such as status, client, service, tags and form fields.

- Action

**List clients**

Returns the clients in your ManyRequests portal, with optional search, organization filter and sorting.

- Action

**List services**

Returns the services offered in your ManyRequests portal, optionally filtered by search text, type, allocation or sale status.

- Action

**List team members**

Returns the portal admins, admins and team members in your ManyRequests portal, optionally filtered by email or role.

- Action

**Update client**

Updates a client's name and/or email address.

- Action

**Update organization**

Updates the name of an existing organization and returns the updated organization.

- Action

**Update Request**

Updates an existing request's title, description, priority, status, due date, brand, assignees, tags or form fields.

- Action

**Update Request Status**

Moves a ManyRequests request to a different status.

## 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)
- [ **ManyRequests** ManyRequests is a Client Portal Software for Creative Agencies that helps you manage your entire Business...](https://apiant.ai/connections/manyrequests)

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 ManyRequests

- [ **HubSpot to ManyRequests** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-manyrequests)
- [ **Salesforce to ManyRequests** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-manyrequests)
- [ **Slack to ManyRequests** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-manyrequests)
- [ **Google Sheets to ManyRequests** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-manyrequests)
- [ **Gmail to ManyRequests** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-manyrequests)
- [ **Google Calendar to ManyRequests** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-manyrequests)

Questions

## Lokalise and ManyRequests, 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 ManyRequests when something happens in Lokalise?

Any of ManyRequests's 27 actions, including Create Client, Create Comment, Create organization brand and Create Request. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from ManyRequests to Lokalise?

ManyRequests has no triggers in the catalog today, so automations start in Lokalise. If you need the other direction, ask: your agent reads ManyRequests's API documentation and adds it.

###

### Do I have to build a connector for Lokalise or ManyRequests?

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 ManyRequests 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.
