Integration
Connect Lokalise to Brex
When Contributor Added fires in Lokalise, your agent runs Update a Budget - “Brex Empower” Customers Only in Brex. 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 Lokalise and Brex 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)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 Lokalise can start in Brex
When Contributor Added in Lokalise
then Update a Budget - “Brex Empower” Customers Only in Brex
When Key Added in Lokalise
then Create User in Brex
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 Brex
Triggers and actions 16 triggers · 53 actions
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.
Action
Create DepartmentCreates a new department in your Brex account and returns its ID, name and description.
Action
Create LocationCreates a new location in your Brex account and returns its ID, name and description.
Action
Create UserCreates a new Brex employee user without sending an invitation, leaving the user inactive until they are invited later. Returns the id of the new user.
Action
Create VendorCreates a new vendor in Brex, with optional contact details and payment accounts, and returns the created vendor.
Action
Disable UserDisables (suspends) an active Brex user and returns the updated user. Optionally changes the user's manager, department, location, title, cost center, legal entity or metadata at the same time.
Action
Email Card DetailsSends a secure email containing a card's number, CVV, and expiration date to the recipient you specify.
Action
Find a Card by IDReturns a single Brex card by its ID, including its owner, status, type, spend controls, addresses and expiration date.
Action
Find a UserReturns the Brex users that match a name, email address or identity-provider ID, optionally narrowed by status, manager, department, location, title, cost center, legal entity or custom field value.
Action
Find Department by NameReturns the Brex departments that match the specified department name.
Action
Find Location by NameReturns the Brex locations that match the specified name.
Action
Find User by EmailReturns the Brex user whose email address exactly matches the one you specify, or reports that no user was found.
Action
Find Vendor by NameReturns the vendors whose name matches the name you supply.
Action
Get Card NumberReturns the full card number, CVV, expiration date and cardholder name for a Brex card.
Action
Get Card TransactionsReturns settled card transactions across all of the company's Brex card accounts, optionally narrowed by user or posted date.
Action
Get Cash TransactionsReturns the transactions for a Brex cash account, optionally only those posted on or after a given date.
Action
List cardsReturns the company's Brex cards, optionally only those belonging to one user.
Action
List Cash AccountsReturns all of the company's Brex cash accounts with their status, balances, account and routing numbers, and which one is primary.
Action
List departmentsReturns the departments in your Brex account, optionally filtered by name.
Action
List ExpensesReturns the expenses on the Brex account, optionally narrowed by user, budget, type, status or date range. Admins and bookkeepers see every expense; other users see only their own.
Action
List locationsReturns the locations in your Brex account, optionally filtered by name.
Action
List usersReturns the users in your Brex account, optionally narrowed by name, email, status, manager, department, location, title, cost center, legal entity or custom field value.
Action
List vendorsReturns the vendors in the Brex account, optionally only those matching a vendor name.
Action
Terminate cardPermanently terminates a Brex card and returns the updated card. The card owner is notified.
Action
Update a Budget - “Brex Empower” Customers OnlyUpdates an existing Brex budget's name, description, parent, owners, period, amount or dates. Available to Brex Empower customers only.
Action
Update cardUpdates an existing Brex vendor card's spend controls and metadata, and returns the updated card.
Action
Update UserUpdates a Brex user's status, manager, department, location, title, cost center, legal entity or metadata. Anything left blank is unchanged.
Action
Update Vendor by NameFinds a Brex vendor by its company name and updates that vendor's name, email, phone, beneficiary name or payment accounts.
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 Lokalise
Lokalise to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Lokalise to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Lokalise to MailchimpMailchimp marketing automation and email platform.
Lokalise to StripeStripe is a payment processing platform for online businesses.
Lokalise to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Lokalise to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Brex
HubSpot to BrexHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to BrexSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to BrexSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to BrexGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to BrexGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to BrexGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Lokalise and Brex, 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 Brex when something happens in Lokalise?
Any of Brex's 27 actions, including Create Department, Create Location, Create User and Create Vendor. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Brex to Lokalise?
Brex has no triggers in the catalog today, so automations start in Lokalise. If you need the other direction, ask: your agent reads Brex's API documentation and adds it.
Do I have to build a connector for Lokalise or Brex?
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 Brex 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.