Integrate Gymdesk

with Localazy

Automated connections called Zaps, set up in minutes with no coding, can automate your day-to-day tasks and build workflows between apps that otherwise wouldn’t be possible.

Each Zap has one app as the Trigger, where your information comes from and which causes one or more Actions (Searches or Creates) in other apps, where your data gets sent automatically.

Triggers #️⃣

The Zapier Trigger is what kicks off the automated process between your apps. Learn more about the triggers that are available for Localazy.

• Comment added into a Localazy project
• Project Published
• Content Import Finished (or finished without any changes)

Actions #️⃣

There are two types of Actions - Searches and Creates. The most common actions are “Create” actions, which, as their name implies, make new items from the data you enter. Searches are Actions in Zapier that find existing data and fill in gaps if needed. Searches can be used as a mid-step while creating Zaps.

• Create: Import to Localazy
• Search: Zip Files in Languages

To use the Zapier Integration, the organization that owns the Localazy project must be on the Autopilot Tier or higher.

14-day Free Trial #️⃣

Every account comes with a 14-day trial period with the Business Plan active to try all the features before committing to a paid subscription, so you can test all of the Autopilot integrations before you pay.

You can find all available Zap Templates on the Localazy Integration page on the Zapier website.

You can also visit the Localazy documentation or find inspiration on the Localazy blog.

Localazy doesn’t have a native Jira integration, but you can still connect the two.

The most direct route is Zapier, available on the Autopilot plan. Use a trigger like Content Imported or Comment Added to automatically create or update a Jira issue whenever new content lands in your project.

If you’d rather build something custom, combine webhooks, also an Autopilot feature, with the Localazy API to call Jira’s own API directly whenever an event fires.

n8n works the same way. It has no dedicated Localazy node, so you’d wire it up through its generic HTTP Request node against the Localazy API instead of a pre-built connector.