Flex Integration
How to connect Flex Rental Solutions to BackOps so events sync automatically.
If your organization uses Flex Rental Solutions to manage inventory and projects, you can connect it to BackOps once and have events flow over automatically. When a job is created or updated in Flex, BackOps reflects that change on the next sync cycle.
How the sync works
Once connected, BackOps polls your Flex instance on a configurable interval. On each cycle, it fetches any elements that have been created or modified since the last sync and either creates the corresponding BackOps event or updates it with the latest values from Flex.
Flex is the source of truth for any field you map. If a value changes in Flex, the next sync overwrites the BackOps field. Edits made directly to mapped fields inside BackOps will be overwritten on the next poll.
Fields not included in your mapping are unaffected and can be managed freely in BackOps.
Setup
Open Organization Settings and navigate to Integrations
Go to your organization settings and select the Integrations section. Find the Flex card and click Connect.
Enter your Flex credentials
Provide your Flex instance name and API key. BackOps stores the API key encrypted and uses it only for sync requests.
Select the element definition
Flex organizes records by element definition (for example, "Event Folder" or "Production Job"). Choose the definition that corresponds to your events in BackOps.
This choice is permanent. Once you save the element definition, it cannot be changed through the UI. If you need to change it, contact support.
Discover fields
BackOps fetches the available fields from your selected element definition. This includes both standard Flex fields and any custom fields configured in your instance.
Configure field mappings
Map each Flex field to the corresponding BackOps event field or custom property. You can also select an event template to apply automatically when a new event arrives from Flex.
Set a sync start date and interval
Choose the date BackOps should start syncing from. Events created or modified in Flex on or after this date will be included. Set the poll interval in minutes; the minimum is 1.
Activate
Toggle the integration to active. BackOps will begin polling on your next scheduled cycle.
Field mapping behavior
BackOps supports mapping text, date, and reference fields in v1. Reference fields (such as project manager, location, or status) are mapped as text by extracting the display name from the Flex record.
If a mapped Flex field is blank, the corresponding BackOps field is cleared on the next sync. Flex's value (including a blank one) is always authoritative for mapped fields.
Templates on new events
If you configure a template during setup, BackOps applies it when a new event arrives from Flex. The template populates areas, collaborators, tasks, and advance assignments so your team can start advancing and scheduling immediately.
Templates are applied once, at creation. Changing the template after setup does not reapply it to existing events.
Changing field mappings
If you update your field mappings after the integration is active, BackOps resets the sync to your original start date and reprocesses all historical events with the new field set. This ensures every event reflects the updated mapping.
Reprocessing on mapping changes can create or update a large number of events depending on your sync start date. If you want to limit the scope, contact support before making changes.
What's not included in v1
- No delete handling. Events deleted in Flex are not deleted in BackOps.
- No bidirectional sync. Changes made in BackOps are not written back to Flex.
- No select or multi-select option sync. These field types are not mapped in v1.