---
title: "Connect Lokalise and Resource Guru - APIANT.ai"
description: "When \"Contributor Added\" fires in Lokalise, your agent runs \"Add task\" in Resource Guru."
canonical: "https://apiant.ai/connect/lokalise-to-resource-guru"
---

# Connect Lokalise and Resource Guru

When **Contributor Added** fires in [Lokalise](https://apiant.ai/connections/lokalise), your agent runs **Add task** in [Resource Guru](https://apiant.ai/connections/resource-guru), or **New or Updated Booking** in Resource Guru 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 Resource Guru **5** triggers Resource Guru **30** 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 Resource Guru 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 Resource Guru can do together

### From Lokalise to Resource Guru

- When **Contributor Added** in Lokalise then **Add task** in Resource Guru
- When **Key Added** in Lokalise then **Create Client** in Resource Guru

### From Resource Guru to Lokalise

- When **New or Updated Booking** in Resource Guru then **Create a Task** in Lokalise
- When **New or Updated Client** in Resource Guru 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 Resource Guru

## Triggers and actions 21 triggers · 56 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 or Updated Booking**

Triggers when a new booking is created and/or a booking is updated.

- Trigger

**New or Updated Client**

Triggers when a new client is created and/or a client is updated.

- Trigger

**New or Updated Project**

Triggers when a new project is created and/or when a project is updated.

- Trigger

**New or Updated Resource**

Triggers when a new resource is created and/or when a resource is updated.

- Trigger

**New or Updated Time Off Event**

Triggers when a time off event is created and/or a time off event is updated.

- Action

**Add task**

Creates a new task in a Resource Guru project phase. The task's dates may widen the phase's date range.

- Action

**Create Booking**

Creates a new booking for one or more resources in Resource Guru.

- Action

**Create Client**

Creates a new client in a Resource Guru account.

- Action

**Create Phase**

Creates a phase in a Resource Guru project.

- Action

**Create Project**

Creates a new project.

- Action

**Create Resource**

Creates a new resource (person, placeholder, meeting room, vehicle or other resource type) in a Resource Guru account. The new resource gets the account's default availability unless working hours are supplied.

- Action

**Create Time Off Event**

Creates a time off (downtime) event for one or more resources in Resource Guru.

- Action

**Delete booking**

Deletes a booking, or a single date or set of occurrences of a repeating booking.

- Action

**Delete client**

Deletes a client from a Resource Guru account.

- Action

**Delete project**

Deletes a project from a Resource Guru account.

- Action

**Delete resource**

Deletes a resource. Future bookings the resource booked are transferred to the connected user, and future bookings of the resource are deleted.

- Action

**Delete time off event**

Deletes a time off event (downtime) from a Resource Guru account.

- Action

**Get booking**

Get one booking by id.

- Action

**Get client**

Returns a specific client by its ID.

- Action

**Get Phase**

Returns a single phase by its id.

- Action

**Get project**

Returns a specific project by its id, including its client, team, activity types and custom field values.

- Action

**Get resource**

Returns the details of a specific resource (person, meeting room, vehicle, etc.) in a Resource Guru account.

- Action

**Get task**

Returns one Resource Guru task with its phase, dates and estimate.

- Action

**Get time off event**

Returns a single time off (downtime) event by its id.

- Action

**List bookings**

List bookings.

- Action

**List clients**

Lists the clients in a Resource Guru account. Active clients only by default; optionally include archived and deleted clients.

- Action

**List projects**

Returns every active project in a Resource Guru account, optionally including archived and deleted projects.

- Action

**List resources**

Returns the active resources (people, rooms, equipment and other bookable resources) in a Resource Guru account.

- Action

**List time off events**

Lists time off (downtime) events in a Resource Guru account, optionally filtered by resource, booker and date range.

- Action

**List users**

Returns every user on the Resource Guru account, both active and deleted.

- Action

**Update Booking**

Updates an existing booking by ID.

- Action

**Update Client**

Updates an existing client in Resource Guru. Only the fields you fill in are changed.

- Action

**Update Project**

Update an existing project in Resource Guru. Only the fields you fill in are changed.

- Action

**Update Resource**

Updates an existing resource.

- Action

**Update Time Off Event**

Updates a time off event.

## 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)
- [ **Resource Guru** The fast, simple way to schedule people, equipment and other resources online.](https://apiant.ai/connections/resource-guru)

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 Resource Guru

- [ **HubSpot to Resource Guru** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-resource-guru)
- [ **Google Sheets to Resource Guru** Google Sheets](https://apiant.ai/connect/google-sheets-to-resource-guru)
- [ **Gmail to Resource Guru** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-resource-guru)
- [ **Google Calendar to Resource Guru** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-resource-guru)
- [ **Google Drive to Resource Guru** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-resource-guru)
- [ **Mailchimp to Resource Guru** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-resource-guru)

Questions

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

Any of Resource Guru's 30 actions, including Create Booking, Create Client, Create Phase and Create Project. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Resource Guru to Lokalise?

Yes. When something happens in Resource Guru, your agent can act in Lokalise too. This page covers both directions: Resource Guru's triggers and Lokalise's actions are listed here as well.

###

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

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 Resource Guru 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.
