Azure Storage and Lokalise Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build developer tools workflows between Azure Storage and Lokalise on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Azure Storage and Lokalise

Detailed info you need to know about Azure Storage and Lokalise integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Azure Storage

    • Developer Tools
    • 6 searches
    • 9 actions

    Manage containers and blobs in Azure Blob Storage.[5]

  • Lokalise

    • Developer Tools
    • 1 trigger
    • 53 searches
    • 63 actions

    Translation management with projects, keys, translations, files, tasks, orders, contributors and webhooks.[6]

How to connect Azure Storage to Lokalise

Set up your Azure Storage and Lokalise integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Azure Storage and Lokalise work in WEXTL?

WEXTL exposes actions and triggers for Azure Storage and Lokalise that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Lokalise triggersAzure Storage actions

Lokalise modules

  • Watch Events Starts the workflow instantly when Lokalise fires a project event through a webhook. Each event arrives with its Project, User and Created At.
  • Add Members to a Group Adds a list of Users to a team group in Lokalise and shows the updated group with its Projects.
  • Add Projects to a Group Gives a team group access to more projects through its Projects list. Returns the group with its Permissions.
  • Create a Branch Creates a branch within a project, with an optional Name. The Branch ID and its creator are returned.
  • Create a Group Sets up a team group. Choose Is Reviewer or Is Admin, pick Role ID and Admin Rights for permissions, and limit languages through Languages Reference and Languages Contributable.
  • Create a Project Creates a Lokalise project from a Name, with its languages listed by Language ISO Code. Pick a Project Type such as Localization Files or Paged Documents, and a Base Lang.
  • Create a Service Token Issues a service token for one project, with Ota as the Service, and returns the Jwt.
  • Create a Snapshot Saves the current state of a project as a snapshot, labeled with an optional Title.
  • Create a Task Creates a translation or review task from a Title, with Languages, Keys, a Due Date and a Source Language. Set the auto close options to finish work automatically.
  • Create a Translation Status Adds a custom translation status for a project, using a Title and a Color.
  • Create a Webhook Registers a webhook in a project that posts the chosen Events to a URL. Use Branch to watch one branch and Event Lang Map to limit events to languages. Returns the Secret.
  • Create an Order Places a PAID translation order with a Provider Slug and Translation Tier for the Keys of a project. Fill in a Briefing, Source Language and Target Language ISO Codes, or turn on Dry Run to get a quote only.
  • Create Billing Details Saves the invoicing details of a team from a Billing Email, Country Code and Zip. Add Address1, Address2, City, Company or Vatnumber for the full address.
  • Create Contributors Invites people by Email, giving each the Languages they may work on. Created contributors show their admin and reviewer rights.
  • Create Glossary Terms Adds terms to a project glossary with a Description and the flags Case Sensitive, Translatable and Forbidden. Each created term is returned with its Translations.
  • Create Key Comments Posts Comments on a translation key, optionally on a Branch. The saved comments show who added them and when.
  • Create Keys Creates translation keys, each with a Key Name and Platforms. Turn on Use Automations to run project automations on them, and read each Filenames value in the result.
  • Create Languages Adds target languages to a project through a Language ISO Code each. The result shows the Lang Name and Plural Forms of every language.
  • Create Screenshots Uploads screenshots to a project as base64 Data, with Title, Description and linked Key IDs. Each result includes the screenshot URL.
  • Delete a Branch Deletes a branch within a project. The reply shows Project ID and Branch ID.
  • Delete a Card Removes a stored payment card from the team.
  • Delete a Comment Deletes one comment left on a key. Pass a Branch to reach a comment on a branch.
  • Delete a Contributor Revokes the access of one contributor to a project.
  • Delete a File Deletes an uploaded file from a project, and reports the File ID with Deleted.
  • Delete a Group Deletes a user group of a team, returning Deleted, Team ID and Group ID.
  • Delete a Key Removes a single translation key and reports Deleted.
  • Delete a Language Removes a language from translation work in a project, giving back its Lang ID.
  • Delete a Project Deletes a whole project along with ALL the keys inside it, and reports Deleted with its Project ID.
  • Delete a Screenshot Deletes a screenshot, returning Deleted and the Screenshot ID.
  • Delete a Snapshot Removes a saved copy of a project, giving back its Snapshot ID.
  • Delete a Task Removes a translation task from the project.
  • Delete a Team User Removes a member from a team, giving back Team ID and User ID.
  • Delete a Translation Status Deletes a custom translation status, returning its Status ID.
  • Delete a Webhook Deletes a webhook and returns Deleted with its Webhook ID.
  • Delete All Contributors Removes ALL contributors from a project in a background job, once Confirm is set. Returns a Job ID to follow it.
  • Delete Glossary Terms Removes all the chosen terms from the glossary of a project.
  • Delete Multiple Keys Removes all the chosen translation keys in one request, and the result counts Keys Removed and Keys Locked.
  • Delete Project Content Clears ALL keys and translations of a project once Confirm is set.
  • Download Files Exports project translations in a chosen Format as a zip. Use Filter Langs to limit languages, Directory Prefix and Bundle Structure to shape paths, and receive a Bundle URL.
  • Download Files Async Queues an export of project translations in a Format and returns a Process ID to poll.
  • Get a Branch Looks up a branch of a project and shows who it was Created By and when.
  • Get a Card Shows a stored payment card by Brand and Last4.
  • Get a Comment Fetches one comment on a key with its Comment text and who it was Added By. Pass a Branch to read from a branch.
  • Get a Contributor Returns a project contributor with Email and Fullname, plus whether they are an admin or reviewer through Is Admin and Is Reviewer.
  • Get a Contributor Deletion Job Checks a deletion job by Job ID, showing its State and how far it got through Total, Processed and Deleted.
  • Get a Glossary Term Retrieves a glossary entry with its Description and Translations, plus Case Sensitive, Translatable and Forbidden settings.
  • Get a Group Shows a team group with its Name, Permissions and the Projects it can reach.
  • Get a Key Retrieves a translation key with its Key Name, Description and Platforms. Turn on Include Ai Scoring to add AI quality scores, or Disable References to skip reference resolution.
  • Get a Key Language Segment Fetches a segment of a key in a single language, using Language ISO Code and Segment Number. Returns the Value and who Modified By.
  • Get a Language Gets a project language with its Lang Name, Is Rtl flag and Plural Forms.

Azure Storage modules

  • Copy a Blob Copies a blob to a Destination container under a Destination blob name, with the copy done on the Azure side. Use Source URL to copy from another storage account, or leave it empty to copy inside this one. Returns the Copy status.
  • Create a Container Adds a new container to your Azure storage account under the Container name of your choice. Use Public access to set who can read its blobs and Metadata to attach your own key and value entries. Returns the Request ID.
  • Delete a Blob Removes a single blob from the container it sits in.
  • Delete a Container Deletes a storage container from your Azure account. Returns the Request ID of the call.
  • Get a Blob Downloads the data of one blob from a container. The blob body is returned as Content.
  • Get the Metadata of a Container Retrieves the custom name and value pairs set on a container, taken from the response headers.
  • Get the Properties of a Blob Shows the details Azure keeps about a blob without downloading its data, such as its Content length.
  • Get the Properties of a Container Finds the details Azure reports for a container in its response headers, including the Lease status.
  • List Blobs Lists the blobs inside one container, each as its own result with its Name. Use Prefix to keep only blobs whose names start with a chosen text, and Limit to set how many blobs are listed.
  • List Containers Lists the containers of the storage account, each as a separate result with its Name. Use Limit to set the largest number returned.
  • Make an API Call Sends a free-form request to the Azure Storage REST API, signed with your saved credential.
  • Set a Blob Tier Moves a blob to another access tier. Fill Tier with the target tier. Returns the Request ID.
  • Set the Metadata of a Blob Writes custom name and value pairs to a blob. Each Metadata entry takes a Header name, written in full like x-ms-meta-author, and a Value. Returns the Request ID.
  • Set the Metadata of a Container Sets user-defined metadata on a container. Fill Metadata with entries made of a Header name and a Value. Returns the Request ID.
  • Upload a Blob Stores new Content as a block blob under a Blob name in a container, in a single request. Set Content type to label the file. Large files may hit Azure size limits. Returns the ETag.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Azure Storage and Lokalise integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Azure Storage and Lokalise on WEXTL®

Claim your 3-day trial to build Azure Storage with Lokalise integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Azure Storage and Lokalise.

How do I connect Azure Storage and Lokalise?

Connect your Azure Storage and Lokalise accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Azure Storage and Lokalise?

Example: when the "Watch Events" trigger in Lokalise fires, WEXTL can "Copy a Blob" in Azure Storage. Azure Storage has 15 actions (including Copy a Blob, Create a Container, and Delete a Blob). Lokalise has 116 actions (including Add Members to a Group, Add Projects to a Group, and Create a Branch). Add filters and transforms between steps when you need them.[1]

Can Azure Storage trigger actions in Lokalise, and Lokalise in Azure Storage?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Azure Storage and Lokalise?

No. Azure Storage-to-Lokalise automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Azure Storage integrate with Lokalise in real time?

Yes. Trigger-based automations start the moment Azure Storage (or Lokalise) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Azure Storage + Lokalise integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Azure Storage with Lokalise?

You can build your Azure Storage + Lokalise automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Azure Storage and Lokalise integration.

  1. Azure Storage and Lokalise integration source code, module specs and credentials implementation.
  2. Our Azure Storage and Lokalise integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Azure Storage and Lokalise, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Azure Storage integration information
  6. Lokalise integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Azure Storage and Lokalise integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Azure Storage and Lokalise, or get started