Lokalise and PostBin Integration

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

Connect Lokalise and PostBin to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

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

Learn about Lokalise and PostBin

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

  • Lokalise

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

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

  • PostBin

    • Developer Tools
    • 3 searches
    • 4 actions

    Free tool for capturing and inspecting HTTP requests.[6]

How to connect Lokalise to PostBin

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

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

WEXTL exposes actions and triggers for Lokalise and PostBin 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 triggersPostBin 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.

PostBin modules

  • Create a Bin Opens a temporary request bin that collects incoming HTTP calls. The result gives its Bin ID and when it Expires.
  • Delete a Bin Deletes a request bin before its roughly 30-minute lifetime ends. A confirmation Message is returned.
  • Get a Bin Reads when a bin Expires. Bins last about 30 minutes, so this tells you how much time one has left.
  • Get a Request Reads one captured request of a bin, using the Bin ID and Request ID. Output includes the Query string sent with it.
  • Get the Next Request Removes the oldest captured request from a bin and returns it with its Method, Path, Headers and Body. Run it repeatedly to work through the queue.
  • Make an API Call Makes a free-form request to the PostBin REST API.
  • Send a Request Posts an HTTP call to a bin to test it. Use Content type to say how the Body is read, Headers and Query string for extras. Only the Request ID is returned.

Explore alternative integrations

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

Automate Lokalise and PostBin on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Lokalise and PostBin.

How do I connect Lokalise and PostBin?

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

Example: when the "Watch Events" trigger in Lokalise fires, WEXTL can "Create a Bin" in PostBin. Lokalise has 1 trigger (including Watch Events). PostBin has 7 actions (including Create a Bin, Delete a Bin, and Get a Bin). Add filters and transforms between steps when you need them.[1]

Can Lokalise trigger actions in PostBin, and PostBin in Lokalise?

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

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

Does Lokalise integrate with PostBin in real time?

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

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

References

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

  1. Lokalise and PostBin integration source code, module specs and credentials implementation.
  2. Our Lokalise and PostBin integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Lokalise and PostBin, 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. Lokalise integration information
  6. PostBin integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

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

Explore Lokalise and PostBin, or get started