Integration
Connect Humanity and Lokalise
When New/Updated Employees fires in Humanity, your agent runs Create a Task in Lokalise, or Contributor Added in Lokalise to Create Shift in Humanity. 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 Humanity 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 Humanity and Lokalise can do together
From Humanity to Lokalise
When New/Updated Employees in Humanity
then Create a Task in Lokalise
When New/Updated Time Entries in Humanity
then Create Comment in Lokalise
From Lokalise to Humanity
When Contributor Added in Lokalise
then Create Shift in Humanity
When Key Added in Lokalise
then Create/Update Employee in Humanity
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 Humanity and Lokalise
Triggers and actions 21 triggers · 43 actions
Trigger
Approved Leave RequestsTriggers when a leave request is approved or an approved leave request changes.
Trigger
New/Updated EmployeesTriggers when an employee is added or an existing employee is updated.
Trigger
New/Updated Time EntriesTriggers when a time entry is created or updated in the last day.
Trigger
Published ShiftsTriggers when a shift in the next 30 days is published or a published shift changes.
Trigger
Published Shifts by EmployeeTriggers when a published shift in the next 30 days that has employees assigned is created or changes.
Action
Assign Leave Type to EmployeeEnables a leave type for an employee, optionally setting how many days they are entitled to.
Action
Assign Positions to EmployeeAssigns positions to an employee, and optionally removes positions from them.
Action
Assign Skills to EmployeeAssigns a skill to an employee in Humanity, optionally with an expiration date and reminder.
Action
Create ShiftCreates a new shift in a Humanity schedule (position), optionally assigning an employee to it.
Action
Create/Update EmployeeCreates a new employee, or updates an existing employee when their ID is given.
Action
Create/Update LocationCreates a new location, or updates an existing location when its ID is given.
Action
Create/Update PositionCreates a new position, or updates an existing position when its ID is given.
Action
Create/Update SkillCreates a new skill, or renames an existing skill when its ID is given.
Action
Create/Update Time EntryCreates a new time entry (timeclock record), or updates an existing one when its ID is given.
Action
Delete shiftDeletes a shift from the Humanity schedule, optionally including the rest of its repeating series.
Action
Find EmployeeFinds a employee by its Humanity ID and returns its details.
Action
Find leave requestsReturns leave requests in a date range, optionally filtered by status and employee.
Action
Find locationsFinds locations and remote sites in Humanity, optionally by name, ID, type or last update time.
Action
Find PositionFinds a position by its Humanity ID and returns its details.
Action
Find shiftsReturns the shifts scheduled within a date range, optionally narrowed to specific employees, positions, locations or skills.
Action
Find timeclocksReturns timeclock records, optionally filtered by date range, employee, position, status or last update.
Action
Update shiftUpdates an existing shift's times, position, title, notes, location or staffing needs.
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 Humanity
Humanity to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Humanity to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Humanity to MailchimpMailchimp marketing automation and email platform.
Humanity to StripeStripe is a payment processing platform for online businesses.
Humanity to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Humanity to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
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
Humanity and Lokalise, answered
What can start an automation from Humanity?
Any of Humanity's 5 triggers in the catalog, including New/Updated Employees, New/Updated Time Entries, Approved Leave Requests and Published Shifts. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Lokalise when something happens in Humanity?
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 Humanity?
Yes. When something happens in Lokalise, your agent can act in Humanity too. This page covers both directions: Lokalise's triggers and Humanity's actions are listed here as well.
Do I have to build a connector for Humanity 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 Humanity 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.