--- title: "Connect Gravity Forms and Lokalise - APIANT.ai" description: "When \"Form Submission\" fires in Gravity Forms, your agent runs \"Create a Task\" in Lokalise." canonical: "https://apiant.ai/connect/gravity-forms-to-lokalise" --- # Connect Gravity Forms and Lokalise When **Form Submission** fires in [Gravity Forms](https://apiant.ai/connections/gravity-forms), your agent runs **Create a Task** in [Lokalise](https://apiant.ai/connections/lokalise), or **Contributor Added** in Lokalise to **Add Entry Note** in Gravity Forms. Describe the whole flow and it is built, tested on every scenario and kept running. Gravity Forms **1** trigger Gravity Forms **30** actions Lokalise **16** triggers Lokalise **26** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Gravity Forms and Lokalise 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 Gravity Forms and Lokalise can do together ### From Gravity Forms to Lokalise - When **Form Submission** in Gravity Forms then **Create a Task** in Lokalise - When **Form Submission** in Gravity Forms then **Create Comment** in Lokalise ### From Lokalise to Gravity Forms - When **Contributor Added** in Lokalise then **Add Entry Note** in Gravity Forms - When **Key Added** in Lokalise then **Create Entry** in Gravity Forms 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 Gravity Forms and Lokalise ## Triggers and actions 17 triggers · 56 actions - Trigger **Form Submission** Triggers when the specified form is submitted. - Action **Add Entry Note** Adds a note to a form entry. Use it to write a progress record back onto a submission — for example noting that the submission was synced to your CRM, who handled it, or why it was skipped — so the note is visible to anyone reviewing that entry in WordPress. - Action **Create Entry** Creates a new form entry. - Action **Create Feed** Attaches a new add-on feed to a form. A feed is one add-on's configuration on a form — the rule that says what should happen when the form is submitted, such as creating a WordPress user, adding the person to a mailing list, or taking a payment. - Action **Create Form** Creates a new form on the WordPress site and returns its id. Supply the form's title and, if you want the form ready to collect data, the fields it should show. - Action **Create Form Feed** Attaches a new add-on feed to a named form. Does the same thing as Create Feed, but takes the form as part of the address rather than in the settings — use whichever reads better in your automation. - Action **Delete Entry** Removes a form entry. By default the entry is moved to the trash and can still be restored from the Entries list; you can choose instead to delete it outright so it cannot be recovered. - Action **Delete Feed** Permanently removes an add-on feed from a form, so that add-on no longer acts on the form's submissions. The form itself and its entries are untouched. - Action **Delete Form** Moves a form to the trash on the WordPress site. The form stops accepting submissions and disappears from the forms list, and the site owner can still restore it or empty the trash in WordPress. - Action **Delete Note** Permanently removes an entry note. Use it to clear a note you logged against a submission, for example after a failed sync was retried successfully. - Action **Get Entry** Retrieve a single form entry, including every field value the person submitted. - Action **Get Feed** Returns one add-on feed by its id, including the add-on's settings. A feed is one add-on's configuration attached to a form — the rule that says what should happen when the form is submitted. - Action **Get Form** Returns one form's full definition, including every field on it, its notifications and its confirmations. Use it to read a form's field ids and labels before mapping data into that form. - Action **Get Form Results** Returns the summarised answers for a survey, quiz or poll form — how many people picked each choice, and how many answered each free-text question — rather than the individual entries. On a form with a lot of entries the summary is built in the background, so the result can come back marked as still being calculated. - Action **Get Note** Returns a single entry note by its id, including the note text, the entry it belongs to, when it was recorded and who it is credited to. - Action **List Entries** Returns form entries from across every form on the site, newest first, and can narrow the results to one form or to entries whose answer to a chosen question matches a value you give. - Action **List Entry Notes** Returns every note attached to one form entry — both notes people have added and the notes Gravity Forms records automatically, such as notification failures. Use it to read back what has already been logged against a submission. - Action **List Feeds** Returns every add-on feed configured on the site. A feed is one add-on's configuration attached to a form — the rule that says what should happen to a submission, such as sending it to a mailing list or charging a payment. - Action **List Form Entries** Returns the entries submitted on one particular form, newest first, and can narrow them to entries whose answer to a chosen question matches a value you give. - Action **List Form Feeds** Returns the add-on feeds attached to one form — the rules that say what happens when that form is submitted. Returns an empty list when the form has no feeds. - Action **List Forms** Returns every active form on the WordPress site, with each form's id, title and entry count. Use it to look up the id a form needs before working with that form's entries. - Action **List Notes** Returns every entry note on the site, across all forms and entries. Use it to sweep recently logged notes when you do not already know which entry you are looking for; to read the notes on one known entry, use List Entry Notes instead. - Action **Send Entry Notifications** Sends the notification emails an entry's form is set up to send, for an entry that already exists — useful for re-sending a confirmation, or for notifying people about an entry that was created through the API rather than by someone filling the form in. - Action **Submit Form** Submit a form the way a visitor would — Gravity Forms runs the form's own validation, saves the entry, and fires its notifications and confirmation. - Action **Update Entry** Change the answers on an existing form entry. Answers you leave blank keep the values they already have. - Action **Update Entry Properties** Changes an entry's housekeeping flags without touching any of its answers — whether it is starred, whether it counts as read, and whether it sits in the active list, the trash or spam. - Action **Update Feed** Changes an existing add-on feed's settings. Settings you do not include are left as they are, so you can change one thing without restating the rest of the add-on's configuration. - Action **Update Feed Properties** Switches an add-on feed on or off, and sets the order it runs in. The add-on's own settings are left completely untouched, so this is the safe way to pause a feed without risking its configuration. - Action **Update Form** Replaces an existing form's definition with the one you supply. Gravity Forms overwrites the whole form, so read the form first with Get Form and send back every part of it you want to keep. - Action **Update Note** Replaces the text of an existing entry note. Use it to revise a note you logged earlier against a submission — for example updating "Sync started" to "Synced to CRM as contact 4821". - Action **Validate Submission** Checks a set of answers against a form's own validation rules without saving an entry or sending any notifications. Returns whether the answers would be accepted, and the per-field error messages when they would not. - 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. ## Each app on its own - [ **Gravity Forms** Gravity Forms is a premier WordPress plugin that makes it easy to create powerful forms on the fly.](https://apiant.ai/connections/gravity-forms) - [ **Lokalise** Lokalise is a translation management tool that lets you structure and automate workflows while encouraging...](https://apiant.ai/connections/lokalise) Reviews ## What our customers say ## More from Gravity Forms - [ **Gravity Forms to Harness.io** Harness.io is an AI-native software delivery platform to automate CI/CD pipelines, manage feature flags, and...](https://apiant.ai/connect/gravity-forms-to-harness-io) - [ **Gravity Forms to Persona** Identity verification API for KYC checks, document verification, and fraud prevention workflows.](https://apiant.ai/connect/gravity-forms-to-persona) - [ **Gravity Forms to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/gravity-forms-to-hubspot) - [ **Gravity Forms to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/gravity-forms-to-salesforce) - [ **Gravity Forms to Google Sheets** Google Sheets](https://apiant.ai/connect/gravity-forms-to-google-sheets) - [ **Gravity Forms to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gravity-forms-to-gmail) ## More into Lokalise - [ **HubSpot to Lokalise** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-lokalise) - [ **Google Sheets to Lokalise** Google Sheets](https://apiant.ai/connect/google-sheets-to-lokalise) - [ **Gmail to Lokalise** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-lokalise) - [ **Google Calendar to Lokalise** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-lokalise) - [ **Google Drive to Lokalise** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-lokalise) - [ **ActiveCampaign to Lokalise** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-lokalise) Questions ## Gravity Forms and Lokalise, answered ### ### What can start an automation from Gravity Forms? Any of Gravity Forms's 1 trigger in the catalog, including Form Submission. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Lokalise when something happens in Gravity Forms? 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 Gravity Forms? Yes. When something happens in Lokalise, your agent can act in Gravity Forms too. This page covers both directions: Lokalise's triggers and Gravity Forms's actions are listed here as well. ### ### Do I have to build a connector for Gravity Forms 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 Gravity Forms 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.