Lokalise and Pingdom Integration
Connect Lokalise and Pingdom 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 Pingdom
Detailed info you need to know about Lokalise and Pingdom integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Lokalise to Pingdom
Set up your Lokalise and Pingdom integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Lokalise and Pingdom
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected Lokalise and Pingdom nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Lokalise and Pingdom. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Lokalise and Pingdom work in WEXTL?
WEXTL exposes actions and triggers for Lokalise and Pingdom 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 triggersPingdom 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.
Pingdom modules
- Create a Check Starts monitoring a Host with a chosen Check Type and Name. Add Check Interval (Minutes), Probe Regions or Response Time Threshold (ms) to tune the runs, and Contacts To Alert or Teams To Alert to notify people.
- Create a Maintenance Window Plans a quiet period with a Description, Start and End, during which chosen Uptime Checks or Transaction Checks are not alerted. Repeat, Repeat Every and Repeat Until make it recur.
- Create a Transaction Check Sets up a scripted browser check from a Name and the Steps to run. Add Region, Interval (Minutes) and Alert After Failed Tests to decide where, how often and when it alerts.
- Create an Alerting Contact Adds a person to notify about check problems. Add Email Targets and SMS Targets for where alerts reach them, or turn on Paused to hold notifications.
- Create an Alerting Team Groups people into a team under a Name, built from a list of Members.
- Delete a Check Deletes an uptime check along with all data collected for it. This cannot be undone.
- Delete a Maintenance Occurrence Removes one scheduled slot that belongs to a maintenance window.
- Delete a Maintenance Window Cancels planned downtime by deleting a maintenance window from the account.
- Delete a Transaction Check Deletes a scripted transaction check from the account.
- Delete an Alerting Contact Deletes a person who is notified about check problems.
- Delete an Alerting Team Removes a group of alert recipients from the account.
- Delete Multiple Checks Removes a batch of uptime checks with one request.
- Delete Multiple Maintenance Occurrences Deletes a batch of downtime slots with a single request.
- Delete Multiple Maintenance Windows Removes several maintenance windows at once.
- Get a Check Reads an uptime check with its Hostname, Status and Resolution. Turn on Include Teams to add the alerting teams.
- Get a Maintenance Occurrence Reads one occurrence of a maintenance window, showing its start (From) and end (To).
- Get a Maintenance Window Shows a maintenance window with its Description, Recurrencetype and Repeatevery.
- Get a Performance Summary Reads the response times of a check, one entry per interval of the chosen Resolution. Turn on Include Uptime to add uptime and downtime to each interval.
- Get a Root Cause Analysis Reads one root cause analysis of an outage for a check. Analysis IDs come from List Root Cause Analyses.
- Get a Transaction Check Fetches a transaction check with its Active flag, Interval and timestamps. Turn on Include Extended Tags for tag details.
- Get a Transaction Check Status Report Shows the States of a transaction check for the period from From to To, sorted by Order.
- Get a Transaction Performance Report Reads response Intervals of a transaction check over time. Use Resolution to pick the interval size and Include Uptime to add availability.
- Get an Alerting Contact Reads a notification contact with its Type, Owner and Notification Targets.
- Get an Alerting Team Reads a notification team and shows all of its Members.
- Get an Average Summary Averages the Responsetime and Status of a check over From to To. Use By Country or By Probe to group the result, and Include Uptime to add the uptime totals.
- Get an Hours Of Day Summary Shows the average response for each Hour of the day for a check. Turn on Use Local Time to group by the time zone of the account instead of UTC.
- Get an Outage Summary Lists the up and down periods (States) of a check from From to To. Use Order to start from the newest or the oldest.
- Get the Credits Shows the credit limits of the account, such as Checklimit, Availablechecks and Availablesms.
- Get the Reference Data Shows lookup lists of Regions, Timezones, Countries and Phonecodes.
- List Alerting Contacts Gives every notification contact with its Paused flag, Type and Notification Targets.
- List Alerting Teams Lists every notification team with their Members to see who belongs where.
- List Alerts Retrieves alerts that were sent, filtered by Check IDs, Contact IDs, Status or Sent Via, within From and To.
- List Check Results Pulls raw test results of a check, each with Probeid, Status and Responsetime. Filter by Probe IDs or response time bounds.
- List Checks Reads uptime checks with their Lasttesttime and Lastresponsetime. Use Tags to keep only checks with those tags.
- List Maintenance Occurrences Retrieves occurrences of maintenance windows from From to To, with Maintenance Window to focus on one.
- List Maintenance Windows Lists maintenance windows with their Description, Recurrencetype and Repeatevery. Use Order By to pick the sort field and Order to set the direction.
- List Probes Finds the testing locations with Country, City and Hostname. Turn on Only Active or Include Deleted to filter.
- List Probes Used By a Check Names the Probes that tested a check since From, up to To if given.
- List Root Cause Analyses Reads the root cause analyses for outages of a check between From and To, each with its Timefirsttest and Timeconfirmtest.
- List Transaction Checks Gets scripted checks with their Active flag and Interval, limited to some Tags or one Type.
- List Transaction Status Reports Shows status reports of transaction checks with their States. Turn on Omit Empty to drop checks without data.
- Make an API Call Sends a free-form request to the Pingdom REST API, signed with your saved credential.
- Run a Single Test Runs one immediate test of a Host with a Check Type, from a Probe or Probe Regions. Set Path, Port or HTTP Authentication to aim the request.
- Run a Traceroute Traces the network route to a Host, optionally from a given Probe.
- Update a Check Edits a monitor, from its Host and Check Interval (Minutes) to its Probe Regions and Contacts To Alert.
- Update a Maintenance Occurrence Moves one occurrence to a new Start and End.
- Update a Maintenance Window Edits the Description, Start, End or repeat settings of a maintenance window. Use Clear Fields to blank chosen values.
- Update a Transaction Check Edits a scripted check, covering its Steps, Region, Interval (Minutes) or Severity.
- Update an Alerting Contact Changes the Name of a notification contact, its Email Targets and SMS Targets, or sets Paused.
- Update an Alerting Team Renames a notification team or replaces its Members.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Lokalise and Pingdom integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Lokalise and Pingdom.
References
List of sources used to gather information about the Lokalise and Pingdom integration.
- Lokalise and Pingdom integration source code, module specs and credentials implementation.
- Our Lokalise and Pingdom integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Lokalise and Pingdom, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Lokalise integration information
- Pingdom integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Lokalise and Pingdom integration page documentation. Used sources, the role of AI, and how the team validates the result.

