Sync Client Status Changes from Radius to Follow Up Boss, and vice versa
Automatically update contact stages in Follow Up Boss or Radius. 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.
Key Benefits
The two-way client status sync between Radius and Follow Up Boss provides:
Bidirectional synchronization – Status changes in either platform automatically update the other, keeping your systems aligned
Real-time accuracy – The latest status update always wins, ensuring your client records reflect the most current information
Consistent data across platforms – Eliminates discrepancies between Radius and Follow Up Boss client statuses
Reduced manual updates – No need to update client statuses in both systems separately
Improved team coordination – All team members see the same accurate status regardless of which platform they're using
Comprehensive coverage – Works for both buyers and sellers across all transaction stages
Step-by-Step Instructions
Understanding the Two-Way Sync
This integration consists of two components:
Radius → Follow Up Boss – Status changes made in Radius automatically update Follow Up Boss
Follow Up Boss → Radius – Status changes made in Follow Up Boss automatically update Radius (requires setup below)
The most recent status change always takes precedence, whether initiated in Radius or Follow Up Boss.
Important: Multiple Zaps Required
Follow Up Boss has multiple static statuses for buyers and sellers. Because of this structure, you must create five separate Zaps to cover all transaction statuses:
Buyer Statuses:
Buyer Contract
Seller Statuses:
Listed
Shared Statuses (work for both buyers and sellers):
Offer
Pending
Closed
Setting Up Follow Up Boss → Radius Sync
You'll need to repeat this process five times, once for each status.
Step 1: Create a New Zap
Log in to your Zapier account
Click Create Zap
Select Follow Up Boss as the Trigger App
Step 2: Configure the Trigger (Follow Up Boss)
Set Trigger App to Follow Up Boss
Set Trigger Event to Person Stage Updated
This fires whenever a client's stage/status is updated in Follow Up Boss
Click Continue
Connect Follow Up Boss Account:
Select the Follow Up Boss account you want to connect
Confirm the connection is established
Step 3: Select the Status for This Zap
In the configuration screen, you'll need to select which specific status this Zap will monitor:
Click on the Status dropdown
Select one of the following values:
Buyer Contract (for buyer transactions)
Listed (for seller transactions)
Offer (works for both buyers and sellers)
Pending (works for both buyers and sellers)
Closed (works for both buyers and sellers)
Click Continue
Note: You'll create a separate Zap for each of these five statuses. It's helpful to name each Zap clearly (e.g., "FUB to Radius - Buyer Contract" or "FUB to Radius - Listed Status") so you can easily identify them later.
Step 4: Test the Trigger
Click Test Trigger to verify the connection is working
Confirm that Follow Up Boss data appears correctly
If the test is successful, click Continue
If you prefer, you can skip the test and proceed to the action setup
Step 5: Configure the Action (Radius)
Set Action App to Radius
Set Action Event to Update Client Status
Click Continue
Connect Radius Account:
Select or connect your Radius account
Confirm the connection is established
Step 6: Configure Action Fields
You'll need to map three key fields:
1. Stage/Status:
Click the + (Insert Data) button in the Stage field
Search for and select Stage from the Follow Up Boss trigger data
This will pull the status from Follow Up Boss and apply it to Radius
2. Primary Email:
Click the + (Insert Data) button in the Email field
Search for and select Primary Email from the Follow Up Boss trigger data
This identifies which client to update in Radius
3. Assign To (Recommended):
If available, click the + (Insert Data) button in the Assign To field
Select the appropriate agent assignment field from the trigger data
This maintains agent ownership during the status update
Step 7: Test and Publish
Click Test Action to verify the status update works correctly
Confirm that:
The correct client was identified in Radius
The status was updated successfully
No error messages appeared
Once the test is successful, click Continue
Click Publish to activate the Zap
Turn the Zap ON
Step 8: Repeat for All Five Statuses
Now that you've created your first Zap, repeat Steps 1-7 for the remaining four statuses:
If you started with Buyer Contract, create Zaps for: Listed, Offer, Pending, and Closed
Name each Zap clearly to distinguish between them
Ensure all five Zaps are published and turned ON
Verifying Your Setup
Once complete, you should have a total of six active Zaps:
Radius → Follow Up Boss (existing)
Follow Up Boss → Radius - Buyer Contract (new)
Follow Up Boss → Radius - Listed (new)
Follow Up Boss → Radius - Offer (new)
Follow Up Boss → Radius - Pending (new)
Follow Up Boss → Radius - Closed (new)
Frequently Asked Questions
Q: Why do I need five separate Zaps instead of one?
A: Follow Up Boss uses multiple static statuses for buyers and sellers. 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.
Q: Do the Offer, Pending, and Closed Zaps work for both buyers and sellers?
A: Yes, these three statuses apply to both buyer and seller transactions, so one Zap for each of these statuses handles both transaction types.
Q: What happens if I only create some of the Zaps but not all five?
A: Only the statuses with active Zaps will sync from Follow Up Boss to Radius. For example, if you don't create the "Listed" Zap, listing status changes in Follow Up Boss won't update in Radius. For complete two-way sync coverage, all five Zaps must be created and active.
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 add custom statuses beyond these five?
A: Yes, you can create additional Zaps for custom statuses by following the same setup process. However, the five standard statuses (Buyer Contract, Listed, Offer, Pending, Closed) cover the primary transaction stages for most workflows.
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, 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.
