The Zapier path is the recommended connection method when your Follow Up Boss account owner is not on RealScout and the native FUB integration is not available. It creates a Zap that automatically adds or updates contacts in RealScout when contacts are created or modified in Follow Up Boss.
When to Use Zapier vs. the Native FUB Integration
Scenario | Recommended path |
Your FUB account owner is on RealScout | Use the native FUB integration — it supports tag automation and does not require a Zapier account |
Your FUB account owner is not on RealScout | Use Zapier — this is the supported fallback path |
Important: The Zapier path does not support tag-based automation. If you need tags to trigger Auto Nurture or search Template assignments in RealScout, you need the native FUB integration. See Trigger RealScout Actions from Your CRM Using Tags for details.
Before You Start
You need:
A RealScout agent account
A Follow Up Boss account (agent-level access is sufficient)
A Zapier account — a free Zapier account supports basic Zaps; check zapier.com/pricing for task limits
Setting Up the Connection
Go to the pre-built FUB + RealScout integration page on Zapier: zapier.com/apps/follow-up-boss/integrations/realscout
Select or create the Zap that fits your workflow. The most common setup: New Contact in Follow Up Boss → Create or Update Contact in RealScout.
Connect your Follow Up Boss account to Zapier when prompted — you will need your FUB API key.
Connect your RealScout account to Zapier when prompted — you will need your RealScout API key.
Map the contact fields between FUB and RealScout. At minimum, map email address — this is the primary match key RealScout uses to identify contacts.
Turn on the Zap and run a test with a real contact to confirm the connection is working.
Note: Zapier tasks have usage limits depending on your plan. Monitor your Zapier task count if you have a high-volume contact pipeline.
What the Zap Does
Once active, the Zap watches Follow Up Boss for new or updated contacts and passes the contact data to RealScout. This keeps your RealScout contact list in sync with FUB without manual imports.
What is included in the sync: contact fields you map (name, email, phone, etc.).
What is not included: tags, stage data, or action plan triggers. Tag-based automation in RealScout is only available through the native FUB integration.
Frequently Asked Questions
Can I use both Zapier and the native FUB integration at the same time?
This is not recommended. Running both simultaneously can create duplicate contacts or conflicting sync behavior. Choose one path and use it consistently. If your FUB account owner is on RealScout, use the native integration.
Will existing FUB contacts sync when I first turn on the Zap?
Zapier Zaps only trigger on new events after the Zap is active — they do not backfill existing records by default. To get existing FUB contacts into RealScout, export them from FUB and import them into RealScout via the contact import tool.
What fields should I map in the Zap?
At minimum, map email address (required for contact matching), first name, and last name. You can also map phone numbers and address fields. Do not map tags — tag sync is not supported via Zapier.
The Zap is active but contacts are not appearing in RealScout. What should I check?
Check your Zapier task history for errors. Common issues: incorrect API key, email field not mapped, or the RealScout account connection needs to be re-authenticated. If the Zap history shows success but the contact is still missing in RealScout, contact Member Support with the contact's email address and the Zapier task ID.
Related Articles