Follow Up Boss Action Plans can include a Zapier step that automatically sends a contact to RealScout when the contact reaches a specific stage or is enrolled in a plan. This is the recommended approach for FUB teams that are routing leads through RealScout for property alerts and nurturing — and where the Zapier integration, rather than the native FUB integration, is in use.
Prerequisite: Complete the connection setup in Zapier Integration: Follow Up Boss > How to Connect RealScout before creating Action Plans that reference the Zap.
What Is a Follow Up Boss Action Plan?
An Action Plan in Follow Up Boss is an automated sequence of tasks, emails, and third-party actions that runs when a contact is assigned to it. Action Plans can include a Zapier step — which fires the connected Zap and passes the contact to RealScout at a specific point in the sequence.
This lets you control when a contact enters RealScout based on where they are in your FUB pipeline — rather than syncing every contact immediately on creation.
Creating an Action Plan with a Zapier Step
In Follow Up Boss, go to Admin → Action Plans.
Click New Action Plan and give it a descriptive name (for example, "New Buyer Lead → RealScout").
Add the steps you want before the Zapier trigger — for example, an initial email or task.
Add a new step and select Zapier as the action type.
Select the Zap you set up that sends contacts to RealScout.
Set the timing for when the Zapier step fires (immediately, or after a delay).
Save the Action Plan.
Tip: Name your Zap clearly in Zapier (for example, "FUB → RealScout: New Buyer") so it is easy to identify when selecting it inside FUB Action Plans.
Enrolling Contacts in the Action Plan
Contacts can be enrolled in an Action Plan:
Manually — select a contact in FUB and assign the Action Plan
Automatically — using FUB Smart Lists or lead routing rules to auto-enroll contacts that match a filter
When the contact reaches the Zapier step in the plan, the Zap fires and the contact is sent to RealScout.
What Syncs When the Zapier Step Fires
The Zap passes whichever contact fields you mapped during setup (name, email, phone, etc.). Tags and FUB stage data are not included — tag-based automation in RealScout requires the native FUB integration.
Once the contact is in RealScout, you can enroll them in Auto Nurture, assign a search Template, and send Listing Alerts.
Frequently Asked Questions
Can I use an Action Plan to remove a contact from RealScout?
Not via Zapier. The Zapier integration supports creating or updating contacts in RealScout, not removing them. To archive a contact in RealScout, you would need to do so manually in your RealScout Contacts list.
Can I have multiple Action Plans that each send contacts to RealScout?
Yes. You can create separate Action Plans for different lead types or stages, each with its own Zapier step pointing to the same (or a different) Zap. Make sure each Zap maps the correct fields.
What if a contact is enrolled in the Action Plan but the Zapier step does not fire?
Check your Zapier task history to see if the Zap was triggered. If it was triggered but the contact is missing in RealScout, confirm the email field is mapped correctly in the Zap. If the Zap was not triggered, confirm the Action Plan step is correctly configured and that your Zap is turned on in Zapier.
Is there a limit to how many contacts I can send through an Action Plan Zapier step?
The limit is determined by your Zapier plan's monthly task allowance, not by RealScout or FUB. Monitor your Zapier task usage if you are enrolling high volumes of contacts.
Can Action Plans trigger tag-based Auto Nurture in RealScout?
No. Tag sync is not supported through the Zapier integration. To use RealScout tags and tag-based Auto Nurture triggers, your team needs the native FUB integration. See Trigger RealScout Actions from Your CRM Using Tags.
Related Articles