Flex Contact Sync: Import Flex Contacts as Crew and Collaborators
How Flex contact sync brings Flex companies in as collaborators and Flex people in as crew, how resource types are mapped, and how the enrichment backlog works.
Flex contact sync brings the contacts you already keep in Flex Rental Solutions into BackOps: Flex companies become collaborators and Flex people become crew. It runs on its own schedule, separate from event sync, and is set up by an organization admin on the Contact Sync tab of Settings › Integrations › Flex Rental Solutions.
Contact sync also matters for event sync. When an event sync mapping points at a Flex reference field, such as a project manager or a client, BackOps fills the crew or collaborator attribute or event role with the contact that sync linked. Without contact sync, those values stay blank.
Set Up Contact Sync
Connect Flex
Discover resource types
Open the Contact Sync tab. BackOps reads the resource types defined in your Flex instance the first time; use Re-discover after adding types in Flex.
Map each resource type
The mapping matrix has two tabs, Companies → Collaborators and People → Crew. For each Flex resource type, either map it to a collaborator type or crew type and choose which Flex fields fill which BackOps fields, or set it to Disabled to skip it.
Set the sync schedule
Set the start date and interval for contact sync. Its schedule is independent from event sync; the interval is at least 1 minute and defaults to 10.
Turn it on
Turn on Activate. It is refused until every discovered resource type is mapped or disabled on both the Companies and People tabs, and every required field of each target type has a source or a static default.
A company mapping needs a source for the name. A person mapping needs at least one of first name, last name, email, or phone number. A contact that matches several mapped resource types gets all of their types. Where two mappings fill the same field, the one higher in the list wins.
Conflicts Between Flex and BackOps
Contact sync has the same When both systems change the same field setting as event sync: Keep the Flex value (the default) or Keep the BackOps value. It applies only when the same field changed in both places since the last sync. Contacts are never pushed back to Flex.
Sync Now and the Enrichment Backlog
Once contact sync is on, Sync now asks for a run at the next one-minute tick instead of waiting for the interval.
Flex limits how quickly its API can be called, so BackOps first imports the basics of each contact and then completes the rest of its details in the background. The Enrichment backlog shows how many contacts are waiting, need attention, or are completed. To move one contact to the front of the queue, open its crew or collaborator record and use Enrich from Flex. A contact that fails five times is counted under needs attention until you queue it again.
Each contact sync and enrichment run appears on the History tab with its counts, warnings, and errors.