Automatically update contact stages in Follow Up Boss or Radius for Zillow Flex users. This integration ensures both systems stay perfectly aligned as your clients move through your pipeline, eliminating the need to manually update statuses in multiple places. This guide is specifically designed for agents using Zillow Flex, which uses a customized set of FUB statuses.

The two-way client status sync between Radius and Follow Up Boss provides:

This integration consists of two components:

The most recent status change always takes precedence, whether initiated in Radius or Follow Up Boss.

Zillow Flex uses a specific set of FUB statuses that map to Radius Client Statuses as follows:

Because Zillow Flex uses multiple static statuses in Follow Up Boss, you must create thirteen separate Zaps to cover all transaction statuses listed above. Each FUB status requires its own dedicated Zap to ensure accurate triggering and status mapping.

You'll need to repeat this process thirteen times, once for each Zillow Flex status.

Connect Follow Up Boss Account:

In the configuration screen, you'll need to select which specific Zillow Flex status this Zap will monitor:

Note: You'll create a separate Zap for each of these thirteen statuses. It's helpful to name each Zap clearly (e.g., "FUB to Radius - Zillow Flex - Lead" or "FUB to Radius - Zillow Flex - Under Contract") so you can easily identify them later.

Connect Radius Account:

You'll need to map three key fields:

1. Stage/Status:

Instead of pulling the status directly from Follow Up Boss, you'll need to manually enter the corresponding Radius Client Status based on the mapping table above.

For example:

Refer to the mapping table in the "Understanding Zillow Flex Status Mapping" section to determine the correct Radius status for each Zap.

2. Primary Email:

3. Assign To (Recommended):

Now that you've created your first Zap, repeat Steps 1-7 for the remaining twelve statuses. Ensure each Zap:

Once complete, you should have a total of fourteen active Zaps:

Q: Why do I need thirteen separate Zaps instead of one?

A: Zillow Flex uses thirteen distinct statuses in Follow Up Boss, and Zapier requires each status to have its own dedicated Zap to ensure accurate triggering and status mapping. This design ensures that each status change is captured correctly and mapped to the appropriate Radius Client Status.

Q: What's the difference between this integration and the standard FUB integration?

A: The standard FUB integration uses five generic transaction statuses (Buyer Contract, Listed, Offer, Pending, Closed). Zillow Flex uses a more granular set of thirteen statuses that provide more detailed tracking throughout the client journey. This integration is specifically designed to work with Zillow Flex's status structure.

Q: What happens if I only create some of the Zaps but not all thirteen?

A: Only the statuses with active Zaps will sync from Follow Up Boss to Radius. For example, if you don't create the "Showing homes" Zap, status changes to that stage in Follow Up Boss won't update in Radius. For complete two-way sync coverage, all thirteen Zaps must be created and active.

Q: Why do multiple FUB statuses map to the same Radius status?

A: Radius uses a streamlined set of client statuses, while Zillow Flex provides more granular tracking. For example, "Lead," "Attempted contact," "Spoke with customer," "Appointment set," and "Nurture" all map to "New Client" in Radius because they represent early-stage prospects who haven't yet progressed to a meeting or transaction stage.

Q: How quickly do status changes sync between systems?

A: Status changes typically sync within 1-2 minutes, depending on your Zapier plan and current system load. Premium Zapier plans offer faster processing times.

Q: What happens if I update a client status in both systems at nearly the same time?

A: The most recent status update will win. Whichever change was made last will be reflected in both systems once the sync processes.

Q: What if a client email doesn't match between systems?

A: The Zap will fail if the email addresses don't match exactly. The client must exist in both systems with the same primary email address for the status sync to work correctly.

Q: Can I customize the status mappings?

A: The mappings provided are based on standard Zillow Flex and Radius status structures. While you can technically create custom mappings, we recommend using the standard mappings to ensure consistency and avoid confusion across your team.

Q: How do I know if my Zaps are working correctly?

A: Check your Zapier dashboard under "Zap History" to see all recent runs, including successes and failures. You can also test by updating a client status in Follow Up Boss and verifying the change appears in Radius within a few minutes.

Q: What should I do if one of my Zaps fails?

A: Review the error message in your Zapier dashboard under Zap History. Common issues include mismatched email addresses, missing client records in Radius, incorrect status mapping, or disconnected accounts. Resolve the underlying issue and the Zap will resume processing.

Q: Will this affect the existing Radius → Follow Up Boss sync?

A: No, the existing sync from Radius to Follow Up Boss continues to work independently. The new Zaps create the reverse direction sync, completing the two-way integration.

Q: Can I pause or turn off specific status Zaps?

A: Yes, you can pause any individual Zap in your Zapier dashboard. However, this will stop syncing for that specific status until you turn it back on. Status changes made while a Zap is paused will not be retroactively synced.

Q: Does the Assign To field need to be mapped?

A: While not strictly required, mapping the Assign To field is recommended to maintain proper agent ownership during status updates. This ensures the correct agent remains associated with the client.

Q: Will historical status changes be synced?

A: No, the sync only applies to status changes made after the Zaps are activated. Historical statuses prior to implementation will remain as they were in each system.

Q: What if Zillow Flex adds or changes statuses in the future?

A: If Zillow Flex modifies their status structure, you may need to create additional Zaps or update existing ones to accommodate the changes. Contact Radius support if you notice discrepancies after Zillow Flex system updates.

Q: Is there a way to set up all thirteen Zaps more quickly?

A: While each Zap must be created individually, you can speed up the process by duplicating an existing Zap and then modifying the trigger status and mapped Radius status. This preserves your account connections and field mappings, requiring only the status-specific changes for each new Zap.