Lokalise and Merge.dev Integration

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

Connect Lokalise and Merge.dev 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 Merge.dev

Detailed info you need to know about Lokalise and Merge.dev 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]

  • Merge.dev

    • Developer Tools
    • 15 triggers
    • 62 searches
    • 18 actions

    Unified API platform that connects HRIS, ATS, and CRM systems through a single integration.[6]

How to connect Lokalise to Merge.dev

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

How does the integration between Lokalise and Merge.dev work in WEXTL?

WEXTL exposes actions and triggers for Lokalise and Merge.dev 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 triggersMerge.dev 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.

Merge.dev modules

  • Create a Contact Adds a person to the CRM, starting from their First Name. Attach a Last Name and an Account, plus Phone Numbers or Email Addresses, each with a type such as Mobile or Work.
  • Create a Lead Adds a lead to the CRM with a Lead Source, Title and Company, plus First Name and Last Name. Use Converted Contact and Converted Account to link a lead that already became a contact and account.
  • Create a Note Writes note Content into the CRM and attaches it to an Account ID, a Contact ID or an Opportunity ID, one at a time. Give an Owner ID to assign the note.
  • Create a Task Opens a CRM task with a Subject and Content, an Owner, a Due Date and a Status. Link it to an Account, an Opportunity or a Contact.
  • Create a Time Off Request Records a time off request for an Employee, with an Approver, a Start Time and End Time. Use Time-Off Units to count the Amount in hours or days, and add an Employee Note for the reason.
  • Create a Timesheet Entry Books hours against an Employee, with Hours Worked and a Start Time in ISO 8601.
  • Create an Account Adds a CRM account with an Account Name and a Number of Employees. Assign an Owner ID, and give the account one or more postal addresses through Addresses.
  • Create an Engagement Logs an engagement in the CRM against an Owner, an Account or a Subject, with at least one of the three supplied. It can also carry an Engagement Type and related Contacts.
  • Create an Opportunity Adds an opportunity under an Opportunity Name, with an Amount and a Status of OPEN, WON or LOST. Tie it to an Account ID, an Owner ID and a Stage ID. Output includes the new Opportunity ID.
  • Get a Bank Info Record by ID Reads one bank account saved for an employee, with its Bank name, Account type, Account number and Routing number.
  • Get a Benefit by ID Loads one benefit with its Provider name, Employee contribution and Company contribution, plus Start date and End date.
  • Get a Company by ID Fetches one company from the HRIS with its Legal name, Display name and Eins.
  • Get a Contact by ID Pulls a CRM contact by ID with their First name, Last name, Email addresses and Phone Numbers. Use Expand with a value like account,owner to return those relations in full.
  • Get a Dependent by ID Reads a dependent of an employee: Relationship, Date of birth, Gender and Is student. Turn on Include Sensitive Fields to add values such as social security numbers.
  • Get a Group by ID Reads a group, showing its Parent group, Type and whether Is commonly used as team is set. Use Show Enum Origins to return enum values as the provider names them.
  • Get a Lead by ID Pulls one CRM lead, including its Company and Lead source.
  • Get a Location by ID Reads one location with its Street 1, City, State, Zip code, Country and Location type.
  • Get a Note by ID Loads a note with its Content and the Contact, Account and Opportunity it is linked to.
  • Get a Pay Group by ID Reads one pay group and returns its Pay group name from the HRIS.
  • Get a Payroll Run by ID Reads one payroll run with its Run state, Run type, Start date, End date and Check date.
  • Get a Stage by ID Reads one pipeline stage from the CRM and returns its Name.
  • Get a Task by ID Reads a task, listing the Subject, Due date, Completed date and Status.
  • Get a Time Off Balance by ID Reads a time off balance with the Balance, Used and Policy type for one employee.
  • Get a Time Off Request by ID Loads one time off request with its Employee, Approver, Status, Request type and Amount. Use Expand Relations with a value like employee,approver to return those people in full.
  • Get a User by ID Reads one CRM user, with a Name, an Email and an Is active flag.
  • Get Account Metadata Describes the payload of an account create call in the CRM, giving a Request schema and a Status.
  • Get Account Patch Metadata Describes what updating one existing account will accept, as a Request schema.
  • Get Accounts Lists CRM accounts, showing Name, Industry, Website and Number of employees. Search by Name or Owner ID.
  • Get an Account by ID Pulls one CRM account with its Name, Industry, Website and Number of employees.
  • Get an Employee by ID Reads one employee with an Employee number, Preferred name, Username and Work email. Turn on Include Sensitive Fields for sensitive values, or use Show Enum Origins to get the provider enum values.
  • Get an Employee Payroll Run by ID Reads what one employee received in a payroll run: Gross pay, Net pay, Earnings, Deductions and Taxes.
  • Get an Employer Benefit by ID Reads a benefit offered by the employer, including its Benefit plan type, Name and Deduction code.
  • Get an Employment by ID Reads one employment record, showing the Job title, Pay rate, Pay frequency, Pay currency and Effective date. Use Show Enum Origins to get the original third-party values of enum fields.
  • Get an Engagement by ID Returns an engagement from the CRM, showing the Direction, Engagement type and Start time. Turn on Include Remote Fields to add fields not mapped to the common model.
  • Get an Engagement Type by ID Fetches one engagement type, giving its Name and Activity type.
  • Get an Opportunity by ID Reads an opportunity from the CRM, covering its Amount, Stage, Status and Close date.
  • Get Bank Info Records Lists saved bank accounts with Bank name, Account type, Routing number and Employee. Restrict by Employee ID, Account Type (SAVINGS or CHECKING) or Bank Name, and sort with Order By.
  • Get Benefits Lists benefits with the Provider name, Benefit plan type, Employee contribution and Company contribution of each. Use Employee ID to return the benefits of one employee.
  • Get Companies Lists companies with their Legal name, Display name and Eins. Turn on Include Deleted Data to also return companies deleted in the third-party platform.
  • Get Contacts Lists CRM contacts with First name, Last name, Account and Owner. Search by Account ID, Email Addresses or Phone Numbers.
  • Get Contacts Metadata Lists what a create call for a CRM contact will accept, in a Request schema alongside a Status and Has conditional params.
  • Get CRM Contact Metadata Shows the shape of a valid new CRM contact as a Request schema, with Has required linked account params.
  • Get Dependents Lists dependents with Relationship, Date of birth and Is student. Use Employee ID to see the dependents of one employee.
  • Get Employee Creation Metadata Fetches the fields a new HRIS employee may carry, as a Request schema with Has conditional params.
  • Get Employees Lists employees with filters such as Job Title, Employment Status, Manager ID, Team ID or Work Email. Each has an Employee number, names and a Work email.
  • Get Employer Benefits Lists the benefits an employer offers, each with a Benefit plan type, Name and Deduction code.
  • Get Employments Lists employment records with Job title, Pay rate, Pay period and Employment type. Use Order By to sort by effective date, and Employee to see one person.
  • Get Engagement Creation Metadata Pulls the Request schema behind engagement creation, together with Remote field classes from the linked CRM.
  • Get Engagements Lists CRM engagements with Subject, Direction and Engagement type, plus when each began and ended. Narrow by when they began with Started After and Started Before.
  • Get Groups Lists groups from the HRIS, returning a Name, a Type, a Parent group and an Is commonly used as team flag per group. Narrow them through Group Types or Group Names.

Explore alternative integrations

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

Automate Lokalise and Merge.dev on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Lokalise and Merge.dev.

How do I connect Lokalise and Merge.dev?

Connect your Lokalise and Merge.dev 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 Merge.dev?

Example: when the "Watch Events" trigger in Lokalise fires, WEXTL can "Create a Contact" in Merge.dev. Lokalise has 1 trigger (including Watch Events). Merge.dev has 80 actions (including Create a Contact, Create a Lead, and Create a Note). Add filters and transforms between steps when you need them.[1]

Can Lokalise trigger actions in Merge.dev, and Merge.dev 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 Merge.dev?

No. Lokalise-to-Merge.dev 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 Merge.dev in real time?

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

You can build your Lokalise + Merge.dev 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 Merge.dev integration.

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

Explore Lokalise and Merge.dev, or get started