--- title: "Connect DocuPipe and Lokalise - APIANT.ai" description: "When \"Document Processed\" fires in DocuPipe, your agent runs \"Create a Task\" in Lokalise." canonical: "https://apiant.ai/connect/docupipe-to-lokalise" --- # Connect DocuPipe and Lokalise When **Document Processed** fires in [DocuPipe](https://apiant.ai/connections/docupipe), your agent runs **Create a Task** in [Lokalise](https://apiant.ai/connections/lokalise), or **Contributor Added** in Lokalise to **Upload Document** in DocuPipe. Describe the whole flow and it is built, tested on every scenario and kept running. DocuPipe **1** trigger DocuPipe **15** 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 DocuPipe 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 DocuPipe and Lokalise can do together ### From DocuPipe to Lokalise - When **Document Processed** in DocuPipe then **Create a Task** in Lokalise - When **Document Processed** in DocuPipe then **Create Comment** in Lokalise ### From Lokalise to DocuPipe - When **Contributor Added** in Lokalise then **Upload Document** in DocuPipe - When **Key Added** in Lokalise then **Analyze document** in DocuPipe 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 DocuPipe and Lokalise ## Triggers and actions 17 triggers · 41 actions - Trigger **Document Processed** Triggers when a document finishes parsing and OCR is complete. - Action **Add schema** Creates a new extraction schema in DocuPipe from a JSON schema you supply, and returns its schema ID. - Action **Analyze document** Asks DocuPipe a list of plain-language questions about one document and starts the analysis, returning the analysis ID to fetch the answers with. - Action **Classify Document** Sends one or more documents to DocuPipe to be sorted into your classes, and returns the job that is doing the work. - Action **Delete document** Removes a document from your DocuPipe account. - Action **Delete schema** Removes an extraction schema from your DocuPipe account. - Action **Extract Data From Document** Pulls structured data out of a document using one of your schemas, and returns the extraction to fetch the results with. - Action **Find documents by criteria** Finds documents in your DocuPipe account whose file name or document ID matches what you search for. - Action **Get Document** Returns one document from your DocuPipe account, with its file details, processing status, parsed text and your own metadata. - Action **Get Extraction Result** Returns the data DocuPipe pulled out of a document, shaped by the schema that was used, along with per-field confidence details. - Action **Get schema** Returns one extraction schema from your DocuPipe account, including the JSON schema it applies and its guidelines. - Action **List documents** Returns the documents in your DocuPipe account, optionally narrowed to one dataset or a date range. - Action **List extractions** Returns the data extractions in your DocuPipe account, optionally narrowed to one schema, one document, or a specific set of extractions. - Action **List schemas** Returns the extraction schemas in your DocuPipe account. - Action **Upload and Extract Data** Sends a file to DocuPipe and immediately starts pulling structured data out of it, returning both the new document and the extraction. - Action **Upload Document** Sends a file to DocuPipe to be read and turned into a document you can extract data from. - 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 - [ **DocuPipe** DocuPipe is a service that turns PDFs, images, and scanned documents into structured JSON data.](https://apiant.ai/connections/docupipe) - [ **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 DocuPipe - [ **DocuPipe to Publora** Publish and schedule posts to ten social networks from one endpoint](https://apiant.ai/connect/docupipe-to-publora) - [ **DocuPipe to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/docupipe-to-hubspot) - [ **DocuPipe to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/docupipe-to-salesforce) - [ **DocuPipe to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/docupipe-to-slack) - [ **DocuPipe to Google Sheets** Google Sheets](https://apiant.ai/connect/docupipe-to-google-sheets) - [ **DocuPipe to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/docupipe-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 ## DocuPipe and Lokalise, answered ### ### What can start an automation from DocuPipe? Any of DocuPipe's 1 trigger in the catalog, including Document Processed. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Lokalise when something happens in DocuPipe? 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 DocuPipe? Yes. When something happens in Lokalise, your agent can act in DocuPipe too. This page covers both directions: Lokalise's triggers and DocuPipe's actions are listed here as well. ### ### Do I have to build a connector for DocuPipe 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 DocuPipe 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.