Integration
Connect Lokalise to Neon Api Keys
When Contributor Added fires in Lokalise, your agent runs Add project in Neon Api Keys. 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 Neon Api Keys 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 Neon Api Keys
When Contributor Added in Lokalise
then Add project in Neon Api Keys
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 Neon Api Keys
Triggers and actions 16 triggers · 39 actions
- Contributor Added
Triggers when a new contributor is added to a Lokalise project.
- Contributor Removed
Triggers when a contributor is removed from the selected Lokalise project.
- 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.
- Key Comment Added
Triggers when someone adds a comment to a translation key in a Lokalise project.
- Key Modified
Triggers when a translation key is modified in a Lokalise project, either individually or in bulk (renames, tag changes, file assignments, hiding).
- 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.
- Language Added
Triggers when one or more languages are added to a Lokalise project, firing once for each language added.
- Language Removed
Triggers when a language is removed from a Lokalise project.
- Poll Tasks
Triggers when a new task is created in a Lokalise project.
- Project Exported
Triggers when translation files are downloaded (exported) from a Lokalise project.
- Project Imported
Triggers when a translation file is uploaded to a Lokalise project. Fires once per uploaded file.
- Project Snapshot
Triggers when a snapshot is taken of the selected Lokalise project.
- Task Created
Triggers when a new translation or review task is created in a Lokalise project.
- Task Deleted
Triggers when a task is deleted in a Lokalise project.
- Translation Reviewed
Triggers when a translation is marked or unmarked as reviewed in a Lokalise project, individually or in bulk.
- 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.
- Add Contributor
Adds a contributor to a Lokalise project, inviting them by email with the chosen languages and permissions.
- Add Languages
Adds one or more languages to a Lokalise project, optionally overriding each language's code, name and plural forms.
- 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.
- Create a Task
Creates a translation, review or automatic-translation task in a Lokalise project for the chosen keys and languages.
- Create Comment
Adds a comment to a translation key in a Lokalise project.
- Create Project
Creates a new Lokalise project in your team, optionally with its languages, base language and project type. Returns the created project.
- Create Snapshot
Creates a snapshot of a Lokalise project, saving its current state so it can be restored later.
- Delete a Key
Deletes a key, with its translations, from a Lokalise project.
- Delete a Language
Removes a language from a Lokalise project.
- Delete a Task
Deletes a task from a Lokalise project.
- Download Files
Exports a Lokalise project's translation files as a .zip bundle and returns the download URL of the bundle.
- List All Orders
Returns all translation orders placed under a Lokalise team.
- List All Tasks
Returns the tasks in a Lokalise project, optionally filtered by title or status.
- 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.
- List Project Languages
Returns the languages set up in a Lokalise project, with each language's code, name, direction and plural forms.
- List Snapshots
Returns the snapshots saved for a Lokalise project, with each snapshot's title and creation details.
- Remove Contributor
Removes a contributor from a Lokalise project.
- Retrieve a Comment
Returns a single comment left on a key in a Lokalise project, including its text, author and when it was added.
- Retrieve a Contributor
Returns a contributor of a Lokalise project, including their email, name, role flags, languages and permissions.
- Retrieve a Key
Returns one translation key from a Lokalise project, including its names, description, platforms, tags, comments, screenshots and translations.
- Retrieve a Task
Returns a Lokalise task, including its status, progress, due date and the languages and assignees it covers.
- Retrieve Project
Returns a Lokalise project's details, including its name, type, base language, settings and translation statistics.
- 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.
- Update a Translation
Updates the text and review flags of a translation in a Lokalise project.
- Update Language
Updates a language in a Lokalise project, changing its code, name or plural forms.
- 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.
- Add API key
Creates a new personal Neon API key and returns its token.
- Add branch
Creates a branch in a Neon project. By default the branch is forked from the project's default branch with no compute, and Neon generates its name.
- Add compute endpoint
Creates a compute endpoint (a Neon compute instance) on a branch of a Neon project. A branch can have one read-write compute and any number of read-only computes.
- Add database
Creates a Postgres database in a branch of a Neon project.
- Add project
Creates a new Neon Postgres project, including its default branch, database, role and compute, and returns the project along with its connection details.
- Add role
Creates a Postgres role in the specified Neon project branch.
- Delete API key
Revokes (permanently deletes) a Neon API key. This cannot be undone.
- Delete branch
Deletes a branch from a Neon project. Compute endpoints on the branch go idle and existing connections are dropped.
- Delete database
Deletes the specified database from a branch of a Neon project.
- Delete project
Deletes a Neon project along with all of its branches, databases, roles and compute endpoints. Deleted projects can be recovered within 7 days.
- List API keys
Lists the API keys for your Neon account. Key tokens are not returned.
- List projects
List all Neon projects owned by the account.
- Update project
Updates an existing Neon project by ID: its name, history retention period, project settings (quotas, IP allowlist, maintenance window, and more) and default compute settings.
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 Neon Api Keys
HubSpot to Neon Api KeysHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Neon Api KeysGoogle Sheets
Gmail to Neon Api KeysGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Neon Api KeysGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Lokalise and Neon Api Keys, 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 Neon Api Keys when something happens in Lokalise?
Any of Neon Api Keys's 13 actions, including Update project, Add API key, Add branch and Add compute endpoint. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Neon Api Keys to Lokalise?
Neon Api Keys has no triggers in the catalog today, so automations start in Lokalise. If you need the other direction, ask: your agent reads Neon Api Keys's API documentation and adds it.
Do I have to build a connector for Lokalise or Neon Api Keys?
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 Neon Api Keys 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.