Bitbucket and Lokalise Integration

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

Build developer tools workflows between Bitbucket 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 Bitbucket and Lokalise

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

  • Bitbucket

    • Developer Tools
    • 5 triggers
    • 65 searches
    • 50 actions

    Bitbucket Cloud REST 2.0 with repositories, pull requests, pipelines, commits and webhooks.[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 Bitbucket to Lokalise

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

How does the integration between Bitbucket and Lokalise work in WEXTL?

WEXTL exposes actions and triggers for Bitbucket 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.

Bitbucket triggersLokalise actions

Bitbucket modules

  • Approve a Commit Marks a commit as approved by the connected account. The result reports the participant Role and State, plus the Participated On time.
  • Approve a Pull Request Signs off on a pull request from List Pull Requests as the connected account. The output shows whether Approved is set for that participant.
  • Compare Commits Builds a diff from a Spec holding one commit hash, compared with its first parent, or two commits separated by two dots. Use Path to narrow it to one file and Ignore Whitespace to skip whitespace edits.
  • Create a Branch Creates a branch from the commit hash or branch name given as the Hash of Target. Use Branch Name without the refs/heads prefix. Output includes the Merge Strategies and Default Merge Strategy of the new branch.
  • Create a Build Status Reports a build result against a commit. Set State to FAILED, INPROGRESS, STOPPED or SUCCESSFUL, give each status its own Key and add a Url that links back to the build system.
  • Create a Commit Comment Leaves a comment against a commit, with Content as its text. The new comment returns with its Id, Created On time and User.
  • Create a Commit from Files Commits files straight into a repository from File Parts, each part keyed by its repository path. Use Message and Author to describe the commit and Branch to say where it lands. The new commit returns with its Hash.
  • Create a Pipeline Schedule Sets up a recurring pipeline run from a Target and a Cron Pattern, which uses seven fields for second precision. Set Enabled to switch the schedule on.
  • Create a Project Sets up a project in a workspace with a Name and Key. Use Description to explain its purpose and turn on Is Private to make it private.
  • Create a Pull Request Opens a pull request that merges one branch into another, using Title and Summary for the text. Turn on Close Source Branch to close the source branch after merging, and list Reviewers to request their review.
  • Create a Pull Request Comment Writes a comment onto a pull request from List Pull Requests, using Content for the text. Output includes its Id, Parent and Resolution.
  • Create a Pull Request Task Adds a to-do item to a pull request. Use Task Raw Content for the wording and turn on Pending to mark it pending.
  • Create a Repository Sets up a repository under a workspace with a Repository Slug. Add a Name, Description or Language, and turn on Is Private, Has Issues or Has Wiki as needed.
  • Create a Repository Variable Saves a pipeline variable against a repository, defined by Key and Value. Turn on Secured to keep its value out of the logs and the REST API.
  • Create a Tag Marks a commit with a tag. Use Name to label the tag, Target to choose the commit and Message to annotate it.
  • Create an Environment Variable Defines a variable inside a deployment environment from List Environments, with a Key and a Value. Turn on Secured to keep the value out of the logs and the REST API.
  • Decline a Pull Request Closes a pull request from List Pull Requests without merging it. The returned pull request shows its State and the Reason it was declined.
  • Delete a Branch Deletes a Bitbucket branch by name from a repository.
  • Delete a Commit Comment Removes a comment attached to a repository commit.
  • Delete a Download Artifact Deletes a file stored in the downloads section of a repository.
  • Delete a Pipeline Schedule Deletes a recurring pipeline schedule from a repository.
  • Delete a Project Deletes a workspace project by its key.
  • Delete a Pull Request Comment Removes a comment written on a pull request.
  • Delete a Pull Request Task Deletes a task listed on a pull request review.
  • Delete a Repository Deletes a whole repository. Use Redirect To to point the old address at a new location.
  • Delete a Repository Variable Removes a pipeline variable stored on a repository.
  • Delete a Tag Removes a git tag in a Bitbucket repository, located by its Workspace, Repository and Tag.
  • Delete an Environment Variable Removes a variable defined for a deployment environment.
  • Fork a Repository Makes a fork of a repository under a new Name. Use Description, Is Private and Fork Policy to adjust the copy. The fork returns with its Full Name and Uuid.
  • Get a Branch Reads one branch, using a Branch from List Branches. Output includes its Name, Target and Default Merge Strategy.
  • Get a Build Status Finds the build status on a commit that matches the Build Status Key from List Commit Statuses. Output includes State, Url and Description.
  • Get a Commit Loads a commit for the Commit from List Commits, with its Hash, Author, Message and Summary.
  • Get a Commit Comment Reads one comment left on a commit, using a Comment from List Commit Comments. Output includes its Content, User and Deleted setting.
  • Get a Commit Diffstat Summarises the files touched by a Spec, giving Lines Added and Lines Removed for each. Use Limit to set roughly how many entries to return.
  • Get a Commit Patch Produces a patch for a Spec that holds one commit or two commits separated by two dots. Output includes Body with the patch text.
  • Get a Download Artifact Retrieves a stored download using the Download from List Downloads. Output includes the File, its Filename, Size and Content Type.
  • Get a File or Directory Reads whatever sits at a Path in a repository, for the Commit from List Commits. Use Max Depth to control how far a directory listing descends.
  • Get a Merge Base Finds the shared ancestor of two commits given as revspec. The ancestor is returned with its Hash, Date, Author and Message.
  • Get a Pipeline Loads a run from List Pipelines, including its Build Number, State, Trigger and Build Seconds Used.
  • Get a Pipeline Config Shows whether pipelines are Enabled for a repository, along with the Repository it belongs to.
  • Get a Pipeline Schedule Reads a schedule from List Pipeline Schedules. Output includes its Cron Pattern, Target and Enabled setting.
  • Get a Pipeline Step Examines one step of a pipeline from List Pipeline Steps. Output includes its Image, Setup Commands, Script Commands, Started On and Completed On.
  • Get a Pipeline Step Log Fetches the log output of one pipeline step from List Pipeline Steps. Output includes Body with the log text.
  • Get a Project Reads one project of a workspace, with its Key, Name, Description and Is Private setting.
  • Get a Pull Request Opens a pull request from List Pull Requests for reading, with its Title, State, Author, Source and Destination.
  • Get a Pull Request Comment Reads a single comment on a pull request, using a Comment from List Pull Request Comments. Output includes Content, Inline placement and Resolution.
  • Get a Pull Request Diff Fetches the unified diff of a pull request. Output includes Body, the whole diff.
  • Get a Pull Request Diffstat Counts the changes on a pull request file by file, with Status, Lines Added and Lines Removed. Use Limit to set roughly how many files to return.
  • Get a Pull Request Merge Task Status Checks progress of an asynchronous merge using a Task from List Pull Request Tasks. Output includes Task Status and Merge Result.
  • Get a Pull Request Patch Gets a pull request as a patch. Output includes Body with the patch text.

Lokalise modules

  • 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.
  • Get a Process Checks a background process of a project, showing its Type, Status and Message.

Explore alternative integrations

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

Automate Bitbucket and Lokalise on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Bitbucket and Lokalise.

How do I connect Bitbucket and Lokalise?

Connect your Bitbucket 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 Bitbucket and Lokalise?

Example: when the "Watch Commits" trigger in Bitbucket fires, WEXTL can "Add Members to a Group" in Lokalise. Bitbucket has 5 triggers (including Watch Commits, Watch Pipelines, and Watch Pull Requests). 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 Bitbucket trigger actions in Lokalise, and Lokalise in Bitbucket?

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 Bitbucket and Lokalise?

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

Does Bitbucket integrate with Lokalise in real time?

Yes. Trigger-based automations start the moment Bitbucket (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 Bitbucket + 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 Bitbucket with Lokalise?

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

References

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

  1. Bitbucket and Lokalise integration source code, module specs and credentials implementation.
  2. Our Bitbucket and Lokalise integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Bitbucket 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. Bitbucket 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 Bitbucket and Lokalise integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Bitbucket and Lokalise, or get started