Integration
Connect Dastra and Lokalise
When New Task fires in Dastra, your agent runs Create a Task in Lokalise, or Contributor Added in Lokalise to Create a Task in Dastra. 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 Dastra and Lokalise 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 Dastra and Lokalise can do together
From Dastra to Lokalise
When New Task in Dastra
then Create a Task in Lokalise
When New Task in Dastra
then Create Comment in Lokalise
From Lokalise to Dastra
When Contributor Added in Lokalise
then Create a Task in Dastra
When Key Added in Lokalise
then Update task in Dastra
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 Dastra and Lokalise
Triggers and actions 17 triggers · 43 actions
Trigger
New TaskTriggers when a new task is created in the chosen Dastra workspace.
Action
Add assetCreates an asset (software, building, network, data store and so on) in a Dastra workspace and returns the new asset record.
Action
Add data processingCreates a new data processing activity in your Dastra record of processing activities, in the organizational unit you choose.
Action
Attach an Actor to a Data ProcessingLinks one or more actors (vendors, internal services, third parties, data controllers) to a data processing activity in your Dastra register, as recipients, data controllers, stakeholders or referents.
Action
Create an ActorCreates an actor (a vendor, partner, processor or other third party) in a Dastra workspace and returns the new actor record.
Action
Create a TaskCreates a task in a Dastra workspace, with its priority, dates, assignee, project and links to other Dastra records.
Action
Delete actorDeletes an actor (a controller, processor or other third party) from a Dastra workspace.
Action
Delete taskDeletes a task from a Dastra workspace.
Action
Get actorReturns one actor (vendor, processor, controller or other third party) from a Dastra workspace by its id, including its contact details, tags, contracts and custom field values.
Action
Get data processingReturns a data processing activity from your Dastra register of processing activities, including its purposes, recipients, data subject rights and custom fields.
Action
Get taskReturns a single Dastra task by its id, including its state, priority, deadline, assignee and custom field values.
Action
List assetsReturns the assets (software, buildings, networks, data stores and other resources) in a Dastra workspace, optionally filtered by type, state, owner, tag, organizational unit or a search text.
Action
List tasksReturns the tasks in a Dastra workspace, optionally filtered by state, priority, assignee, project, linked object, dates or search text.
Action
Search ActorReturns the actors (vendors, data controllers, third parties and other organizations or people) in a Dastra workspace that match the search text and filters.
Action
Search Data ProcessingSearches the data processing activities in a Dastra workspace by text and optional filters, returning every matching activity with its full record.
Action
Update actorUpdates an existing actor (vendor, partner or person) in a Dastra workspace. Fields you leave blank keep their current values.
Action
Update data processingUpdates an existing data processing activity in a Dastra workspace, changing only the fields you fill in, and returns the updated record.
Action
Update taskUpdates an existing Dastra task. Fields you leave blank keep their current values.
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.
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 Dastra
Dastra to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Dastra to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Dastra to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Dastra to Google SheetsGoogle Sheets
Dastra to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Dastra to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Lokalise
HubSpot to LokaliseHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LokaliseGoogle Sheets
Gmail to LokaliseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LokaliseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to LokaliseGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to LokaliseActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Dastra and Lokalise, answered
What can start an automation from Dastra?
Any of Dastra's 1 trigger in the catalog, including New Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Lokalise when something happens in Dastra?
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 Dastra?
Yes. When something happens in Lokalise, your agent can act in Dastra too. This page covers both directions: Lokalise's triggers and Dastra's actions are listed here as well.
Do I have to build a connector for Dastra 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 Dastra 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.