Integration
Connect Lokalise and ServiceM8
When Contributor Added fires in Lokalise, your agent runs Add company contact in ServiceM8, or New Job in ServiceM8 to Create a Task in Lokalise. 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 ServiceM8 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 and ServiceM8 can do together
From Lokalise to ServiceM8
When Contributor Added in Lokalise
then Add company contact in ServiceM8
When Key Added in Lokalise
then Add job payment in ServiceM8
From ServiceM8 to Lokalise
When New Job in ServiceM8
then Create a Task in Lokalise
When Job Queued in ServiceM8
then Create Comment in Lokalise
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 ServiceM8
Triggers and actions 18 triggers · 49 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.
Trigger
Job QueuedTriggers when a Job is assigned to a Queue.
Trigger
New JobTriggers when a new job is created.
Action
Add attachmentUploads a file and attaches it to a job (or another ServiceM8 record), so it appears in that record's diary.
Action
Add company contactCreates a new contact person on a ServiceM8 client (company), such as a billing or job contact.
Action
Add job allocationAllocates a ServiceM8 job to a staff member, optionally with a scheduled date and allocation window.
Action
Add job materialAdds a material line item to a ServiceM8 job, with quantity, pricing and tax details.
Action
Add job paymentRecords a payment against a ServiceM8 job, with its amount, method, date and optional note.
Action
Add noteAdds a note to a job, client or other ServiceM8 record.
Action
Create ClientCreates a new client (company) record in ServiceM8.
Action
Create JobCreates a new job in ServiceM8, optionally linked to a client, category and queue, and returns the new job's UUID.
Action
Delete clientDeletes (archives) a client in ServiceM8.
Action
Delete jobDeletes (archives) a job in ServiceM8. The job is hidden in the app and can be restored later.
Action
Get attachmentReturns the details of a single file attachment (photo, PDF or other file) by its UUID.
Action
Get clientReturns one ServiceM8 client (company) record by its UUID, including its name, address and billing details.
Action
Get jobReturns a single ServiceM8 job by its UUID, including its status, client, address and totals.
Action
Get Job AllocationReturns a single job allocation — which staff member a job is allocated to, its window, dates and status.
Action
List clientsReturns the clients (companies) in your ServiceM8 account, optionally narrowed by a filter.
Action
List job materialsReturns the materials (line items) recorded on jobs, optionally filtered, for example to a single job.
Action
List job paymentsReturns the payments recorded against jobs, optionally filtered (for example to a single job).
Action
List Job QueuesReturns the job queues set up in the ServiceM8 account.
Action
List jobsReturns the jobs in your ServiceM8 account, optionally narrowed by a filter.
Action
List notesReturns the notes in your ServiceM8 account, optionally filtered and sorted.
Action
List staff membersReturns the staff members in your ServiceM8 account, optionally narrowed by a filter.
Action
Update clientUpdates an existing client (company) in ServiceM8. Only the fields you fill in are changed.
Action
Update jobUpdates an existing job in ServiceM8, changing only the fields you fill in.
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 ServiceM8
HubSpot to ServiceM8HubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ServiceM8Salesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to ServiceM8Google Sheets
Gmail to ServiceM8Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ServiceM8Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ServiceM8Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Lokalise and ServiceM8, 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 ServiceM8 when something happens in Lokalise?
Any of ServiceM8's 23 actions, including Create Client, Create Job, Update client and Update job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ServiceM8 to Lokalise?
Yes. When something happens in ServiceM8, your agent can act in Lokalise too. This page covers both directions: ServiceM8's triggers and Lokalise's actions are listed here as well.
Do I have to build a connector for Lokalise or ServiceM8?
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 ServiceM8 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.