This integration connects the Redzone Reliability CMMS module with Limble. Redzone Reliability must be used with this integration.
If you are unsure whether your Redzone plan includes Reliability, contact your Redzone account manager.
Overview
The integration automatically keeps Redzone Reliability maintenance actions in sync with Limble work orders. When a maintenance action is created or updated in Redzone Reliability, a corresponding work order appears in Limble. When your Limble technician completes that work order, the Redzone action is automatically marked as done. Comments flow in both directions.
What syncs
From Redzone | What happens in Limble |
New maintenance action | New work order is created |
Updated action (status, priority, due date, etc.) | Existing work order is updated |
New action comment | Comment added to the Limble task |
From Limble | What happens in Redzone |
Work order completed | Redzone action is marked DONE |
Comment added to work order | Comment posted to the Redzone action |
Note: File attachments, comment edits, and Limble field changes (due date, assignment, priority) do not sync back to Redzone. Refer to Known Limitations for the full list.
Before You Begin
Required: Redzone Reliability
This integration requires the Redzone Reliability module; confirm your organization has Redzone Reliability before proceeding. Contact your Redzone account manager or visit rzsoftware.com/product/reliability for more information.
Gather the following before starting the setup wizard:
Redzone App credentials: a client ID and client secret generated by registering an app client in the Redzone admin portal. A Redzone administrator at your organization can do this by logging into the Redzone admin portal and registering a new app client. If this has not been done yet, it must be completed before you can proceed with setup.
Limble location: decide in which Limble location work orders should be created. You can find locations in Limble.
(If using asset sync) Limble custom field names: the exact names of custom fields in Limble that you want Redzone asset data mapped to.
Step-by-Step Setup
Step 1: Connect Redzone
Enter the client ID and client secret for your Redzone app client.
How to get these credentials: A Redzone administrator at your organization needs to register an app client in the Redzone admin portal. Once registered, the portal provides a client ID and client secret to copy and paste here. If no app client has been registered yet, this must be done before you can continue.
If your Redzone account is associated with more than one enterprise, you will see a picker to select which enterprise to sync. Choose the correct one before proceeding.
Step 2: Configure Work Order Sync
This section controls how Redzone actions become Limble work orders.
Default Limble Location - Select the Limble location where new work orders will be created. This is also required if you plan to enable Asset Sync.
Sync Schedule - Choose how often the integration checks Redzone for new and updated actions. Options range from every 5 minutes to every 24 hours.
Status Filter - Select which Redzone action statuses are included in the sync. The default is NEW, TO_DO, IN_PROGRESS, and MISSED. Actions in other statuses (such as CANCELLED) are ignored unless you explicitly add them.
Task Type Mapping - Map each Redzone action type to a Limble task type or set to do not sync:
Work Order
Work Request
Breakdown
Auto-Approve Work Requests (default: on) - When enabled, the integration automatically approves Redzone WORK_REQUEST actions as soon as the corresponding Limble task is created. Disable this if your workflow requires manual approval in Redzone.
Historical Sync Window - Choose how far back to pull existing Redzone actions on the first deployment:
Now: only new actions going forward
7 days / 30 days / 365 days: pull actions updated within that window
All time: pull all matching actions (may take longer on large accounts)
User Assignment Mode
Default Only: all work orders are assigned to the user or team you select below
Match by Name: the integration tries to match the Redzone user name against Limble user display names; falls back to the default assignment if no match is found
If using Match by Name, select Redzone User Field to control whether the creator (from) or the assignee (owner) of the Redzone action is used for matching.
Default Task Assignment - The Limble user or team that receives work orders when name matching is not used or no match is found.
Default Task Priority - The Limble priority level for normal-priority Redzone actions. High-priority actions always use the highest Limble urgency level regardless of this setting.
Step 3: Configure Asset Sync (optional)
Enable this to automatically create and update Limble assets based on the assets referenced in Redzone maintenance actions.
Enable Asset Sync - toggle on to activate.
Asset Field Mapping - Map Redzone asset fields to the exact names of custom fields in your Limble account. The UUID field mapping is required; all others are optional.
Redzone Field | Map to Limble Custom Field |
UUID | (required - enter the exact Limble custom field name) |
External ID | (optional) |
Description | (optional) |
Model Number | (optional) |
Serial Number | (optional) |
Asset Type UUID | (optional) |
Configuration | (optional) |
Custom field names must match exactly. To verify your custom field names in Limble, open your list of existing fields:
Go to the Assets page (in the location you're using for the integration).
Click on an asset to open it.
Click Add & Edit Fields.
Make sure Existing fields is selected. Review your custom field names.
How the Sync Works
Once deployed, the integration runs automatically. Here's what to expect:
Redzone → Limble: The integration polls Redzone on the schedule you configured. New and updated actions are created or updated as Limble work orders. New comments on Redzone actions appear in Limble after the next scheduled poll.
Limble → Redzone: This happens in real time. The moment you complete a work order or add a comment in Limble, the integration immediately updates Redzone with no waiting for the next poll.
About the comment tags
You may notice comments in Limble or Redzone that end with a tag like [rz:…] or [limble:…]. These are origin markers generated by the integration that prevent comments from being duplicated infinitely.
Do not remove or edit these tags. If they are deleted, the same comment may be re-posted by the integration on the next sync.
About the meta1 field on work orders
Work orders created by this integration store a Redzone action ID in Limble's meta1 field. This is what links the Limble task back to the Redzone action for completions and comment syncing.
Do not clear or overwrite meta1 on work orders created by this integration. If it is removed, completing the task in Limble will no longer close the Redzone action.
Forcing a Re-Sync
If you change a configuration setting (such as Task Type Mapping or Asset Field Mapping) and want to re-process existing actions:
Open the integration's configuration wizard.
Toggle Force Historical Re-Sync on.
Save and deploy.
The next scheduled poll will reset the sync cursor and re-process all actions within the configured Historical Sync Window. The toggle resets itself automatically after one cycle. You do not need to turn it off manually.
Known Limitations
File attachments are not transferred. Files attached to Redzone actions or comments do not appear in Limble, and vice versa.
Comment edits are not synced. Once a comment is transferred, edits to it in either system are not propagated.
Limble field changes do not update Redzone. If you change the due date, assignment, priority, or name of a work order in Limble, those changes are not sent back to Redzone.
Asset sync is one-directional. Redzone assets are pushed into Limble, but changes made to Limble assets are not pushed back to Redzone.
Comments on completed tasks are not swept. If a Redzone action comment is added after the Limble task has already been completed, that comment will not appear in Limble.
Redzone → Limble is not real-time. New Redzone actions and comments appear in Limble after the next scheduled poll, not instantly.
Need Help?
If actions are not appearing in Limble, or completions are not being sent back to Redzone, contact our support team and reference this article. Include:
The Limble location where work orders should be appearing.
The type and status of the Redzone action that is not syncing.
Any recent configuration changes made to the integration.