--- title: "Connect Busybusy and Lokalise - APIANT.ai" description: "When \"Certifications: Certification Updated\" fires in Busybusy, your agent runs \"Create a Task\" in Lokalise." canonical: "https://apiant.ai/connect/busybusy-to-lokalise" --- # Connect Busybusy and Lokalise When **Certifications: Certification Updated** fires in [Busybusy](https://apiant.ai/connections/busybusy), your agent runs **Create a Task** in [Lokalise](https://apiant.ai/connections/lokalise), or **Contributor Added** in Lokalise to **Create Project** in Busybusy. Describe the whole flow and it is built, tested on every scenario and kept running. Busybusy **6** triggers Busybusy **27** 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 Busybusy 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 Busybusy and Lokalise can do together ### From Busybusy to Lokalise - When **Certifications: Certification Updated** in Busybusy then **Create a Task** in Lokalise - When **Certifications: New Certification Created** in Busybusy then **Create Comment** in Lokalise ### From Lokalise to Busybusy - When **Contributor Added** in Lokalise then **Create Project** in Busybusy - When **Key Added** in Lokalise then **Create Break Entry** in Busybusy 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 Busybusy and Lokalise ## Triggers and actions 22 triggers · 53 actions - Trigger **Certifications: Certification Updated** Triggers when a certification is created or updated in Busybusy. - Trigger **Certifications: New Certification Created** Triggers when a new certification type is created in Busybusy. - Trigger **Employee Created** Triggers when a new employee (member) is added to your busybusy organization. - Trigger **Employee Updated** Triggers when an employee in busybusy is created or changed. - Trigger **Project Created** Triggers when a new project is created in busybusy. - Trigger **Project Updated** Triggers when a project or subproject is created or changed in Busybusy, including when it is unarchived. - Action **Archive Employee** Archives an employee (member) in busybusy by setting their archived date. - Action **Archive Project** Archives a project in Busybusy by setting its archived date. - Action **Certifications: Create Certification** Creates a certification type in your Busybusy organization that employees can later be certified against. - Action **Certifications: Create Employee Certification** Records that an employee holds a certification, with its issue, renewal and expiry dates. - Action **Certifications: Delete Certification** Deletes a certification from your Busybusy organization by marking it deleted. - Action **Certifications: Renew Employee Certification** Renews an employee's certification record in busybusy by setting a new renewal date and, optionally, a new expiration date. - Action **Certifications: Search Certifications** Searches certifications in Busybusy by name, ID or date filters and returns the matching certifications. - Action **Certifications: Update Certification** Updates an existing certification's name, description, renewal period or documentation settings. - Action **Certifications: Update Employee Certification** Updates an employee's certification record in busybusy, such as its issue, renewal or expiration date or the employee it belongs to. - Action **Create Break Entry** Creates a break on an existing busybusy time entry, with its start time and optional end time. - Action **Create Budget** Creates a cost budget for a busybusy project, optionally scoped to a cost code or piece of equipment. - Action **Create Cost Code Group** Creates a cost code group in busybusy for organizing cost codes. - Action **Create Employee** Creates a new employee (member) in your busybusy organization. - Action **Create Equipment** Creates a piece of equipment in busybusy with its name, model, serial number and tracking options. - Action **Create Project** Creates a new project in busybusy. - Action **Create Time Entry** Creates a time entry (clock-in record) for an employee in busybusy, optionally against a project, cost code and equipment. - Action **Search Break Entries** Returns the break entries that match the filters you supply, such as a time entry, start time or paid status. - Action **Search Employee (Single)** Finds a single employee by ID and returns the first matching employee record. - Action **Search Employees (Multiple)** Returns the employees that match the filters you supply, such as name, username, employee number or group. - Action **Search Projects (Multiple)** Returns all projects matching the given title, parent project, ID or dates. - Action **Unarchive Cost Code** Restores an archived cost code so it is active again. - Action **Unarchive Employee** Restores an archived employee in busybusy so they are active again. - Action **Unarchive Project** Restores an archived project in Busybusy so it is active again. - Action **Update Cost Code** Updates an existing cost code's title, code, unit, group, insurance classes or custom fields. - Action **Update Employee** Updates an existing busybusy employee's name, username, contact details, position, employee number or group. - Action **Update Equipment** Updates an existing piece of equipment in busybusy, changing only the details you fill in. - Action **Update Project** Updates an existing project's name, parent project, or archive date in busybusy. - 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 - [ **Busybusy** Busybusy is the perfect time tracking & job costing app built BY construction companies FOR construction...](https://apiant.ai/connections/busybusy) - [ **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 Busybusy - [ **Busybusy to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/busybusy-to-hubspot) - [ **Busybusy to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/busybusy-to-salesforce) - [ **Busybusy to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/busybusy-to-slack) - [ **Busybusy to Google Sheets** Google Sheets](https://apiant.ai/connect/busybusy-to-google-sheets) - [ **Busybusy to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/busybusy-to-gmail) - [ **Busybusy to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/busybusy-to-google-calendar) ## 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 ## Busybusy and Lokalise, answered ### ### What can start an automation from Busybusy? Any of Busybusy's 6 triggers in the catalog, including Certifications: Certification Updated, Certifications: New Certification Created, Employee Created and Employee Updated. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Lokalise when something happens in Busybusy? 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 Busybusy? Yes. When something happens in Lokalise, your agent can act in Busybusy too. This page covers both directions: Lokalise's triggers and Busybusy's actions are listed here as well. ### ### Do I have to build a connector for Busybusy 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 Busybusy 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.