Sync Client Status Changes from Radius to Follow Up Boss
Automatically update contact stages in Follow Up Boss when client statuses change in Radius Agent. 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
Automatic Status Updates: Client status changes in Radius instantly update stages in Follow Up Boss
Pipeline Consistency: Keep both CRMs synchronized without manual work
Time Savings: No more duplicate data entry across platforms
Real-Time Tracking: Status changes sync within minutes
Accurate Reporting: Ensure both systems reflect the current state of your pipeline
Seamless Workflow: Focus on clients, not data management
What You'll Need
Before getting started, make sure you have:
An active Zapier account
Access to your Radius Agent account with API key
Admin access to your Follow Up Boss account
The Notes sync Zap already configured (recommended but not required)
Setting Up Client Status Sync
Step 1: Create a New Zap
In Zapier, click Create Zap
Name your Zap something descriptive like:
"Radius → FUB | Status Change Sync"
"Client Status: Radius to Follow Up Boss"
Pro Tip: Clear naming helps you quickly identify Zaps when managing multiple integrations.
Step 2: Set Up the Trigger (Radius Agent)
The trigger will fire whenever a client's status changes in Radius.
Search for and select Radius Agent
Under Event, select Change Client Status
Click Continue
Step 3: Connect Your Radius Account
If you've already connected Radius (from the Notes Zap), the account will appear automatically—simply select it
If this is your first time connecting Radius:
Navigate to Radius → Integrations → Zapier
Copy your API key (Integration Key)
Return to Zapier and paste the key in the connection prompt
Select the correct account and verify using the agent's email address
Click Continue
Step 4: Test the Trigger
Verify that Zapier can successfully detect status changes from Radius:
Click Test Trigger
Zapier will fetch a sample record showing a lead with a changed status
Review the sample data to ensure it looks correct
Click Continue with Selected Record
Step 5: Set Up the Action (Follow Up Boss)
The action determines what happens in Follow Up Boss when a status changes in Radius.
For the Action App, choose Follow Up Boss
Under Event, select Change Stage of a Contact
Click Continue
Step 6: Connect Your Follow Up Boss Account
Select the same Follow Up Boss account used in your previous Zap (if applicable)
If connecting for the first time, enter your Follow Up Boss API Key
Verify the correct account is selected (check the account name)
Click Continue
Step 7: Configure and Map Fields
This critical step connects the client data between Radius and Follow Up Boss:
Map the Contact Email
Click the + icon beside the Contact Email field
Select and map it to Radius Lead Email
This ensures the status update applies to the correct contact
Set the Stage/Status
Under Stage / Status, select the value that should update in Follow Up Boss
Common mappings include:
Buyer - In Contract
Buyer - Closed
Seller - Listing Prepped
Seller - Under Contract
And other stages that match your Follow Up Boss pipeline
Important Note: The stage you select here will be the stage applied in Follow Up Boss. Make sure it aligns with your Follow Up Boss pipeline stages.
3. Click Continue
Step 8: Test and Publish
Test the integration before making it live:
Click Test Action
Wait for the success message:
✅ "Stage of Contact successfully updated in Follow Up Boss"
Verify the test worked by checking the contact in Follow Up Boss
Click Publish to activate your Zap
Validating Your Integration
After publishing, test with real data to ensure everything syncs correctly:
Go to Radius CRM
Select any client and change their status
Wait approximately 2 minutes (Zapier processes updates in cycles)
Log into Follow Up Boss
Find the corresponding contact and verify their stage/status has been updated
If the status updates successfully, your integration is working! 🎉
Understanding Status Mapping
Common Status Mappings
Here's how Radius statuses typically map to Follow Up Boss stages:
Radius Status | Follow Up Boss Stage |
New Client | New Lead |
Pre-approved | Pre-Qualified |
Showings-Tours | Active Buyer |
In Contract | Under Contract |
Closed | Closed - Won |
Listing Prepped | Preparing Listing |
Sending & Receiving Offers | Negotiating |
Note: Your specific mappings may vary based on your Follow Up Boss pipeline configuration.
Multiple Status Zaps
If you need different Radius statuses to map to different Follow Up Boss stages, you can:
Create multiple Zaps (one for each status mapping)
Use Zapier's Filter feature to route different statuses to different stages
Use Zapier's Paths feature for conditional logic (available on paid plans)
Troubleshooting
Status not updating in Follow Up Boss?
Verify your Zap is turned On in Zapier
Check that the email in Radius matches exactly with the contact in Follow Up Boss
Review Zap History for error messages
Ensure the stage you selected exists in your Follow Up Boss pipeline
Wrong stage being applied?
Review your field mapping in Step 7
Verify you selected the correct Follow Up Boss stage
Check if you need multiple Zaps for different status scenarios
Zap failing with "Contact not found" error?
The email in Radius must match a contact in Follow Up Boss exactly
Create the contact in Follow Up Boss first, then update their status in Radius
Updates happening slowly?
Free Zapier accounts sync every 15 minutes
Paid accounts sync more frequently (1-5 minutes)
Check your Zapier plan for sync timing details
Managing Your Zap
Editing Your Zap
Navigate to Zapier → Zaps
Find your Status Change Sync Zap
Click the three dots (•••) and select Edit
Make changes and republish
Pausing Your Zap
Go to Zapier → Zaps
Find your Status Change Sync Zap
Toggle the switch to Off to pause syncing
Monitoring Zap Activity
Click on your Zap name
Select Zap History to view:
Successful runs
Failed runs with error details
Status change events processed
Best Practices
Keep Stage Names Consistent
Align your Radius status names with Follow Up Boss stage names when possible to avoid confusion.
Test Thoroughly Before Going Live
Run multiple test status changes to ensure all scenarios work correctly before relying on the automation.
Monitor Regularly
Check your Zap History weekly during the first month to catch any issues early.
Document Your Mappings
Keep a reference document showing which Radius statuses map to which Follow Up Boss stages for your team.
Communicate with Your Team
Let your team know about the automation so they understand status changes will sync automatically.
Frequently Asked Questions
Q: How quickly do status changes sync between systems?
A: Status changes typically sync within 1-5 minutes on paid Zapier plans, or up to 15 minutes on free plans.
Q: Can I sync status changes from Follow Up Boss back to Radius?
A: Yes! Create a separate Zap with Follow Up Boss as the trigger and Radius as the action for two-way syncing.
Q: What happens if I change a status multiple times quickly?
A: Each status change will trigger the Zap separately. All changes will sync, though there may be a slight delay between updates.
Q: Will historical status changes sync?
A: No, only status changes that occur after the Zap is published will sync. Past changes won't be transferred.
Q: Can I sync multiple status types with one Zap?
A: You can map one status type per Zap. For multiple status mappings, create separate Zaps or use Zapier Paths (paid feature).
Q: Does this count against my Zapier task limit?
A: Yes, each status change that syncs counts as one task. Monitor your usage to stay within your plan limits.
Q: What if the contact doesn't exist in Follow Up Boss yet?
A: The Zap will fail with a "Contact not found" error. You'll need to create the contact in Follow Up Boss first, or set up a separate Zap to create contacts automatically.
Q: Can I customize which fields update besides the stage?
A: Yes! In Step 7, you can map additional fields from Radius to Follow Up Boss, such as tags, notes, or custom fields.