Follow Up Boss + ShowingTime: What Actually Works
There is no real-time native integration between Follow Up Boss and ShowingTime. The connection requires email-based middleware that parses ShowingTime confirmations and writes structured data to FUB via its API. That's exactly what Showing Signal does.
Why This Comes Up
Follow Up Boss is the CRM of choice for a significant share of independent buyer's agent teams. ShowingTime is the showing scheduling tool most MLS markets require. So the question "do they work together?" is one nearly every FUB user on a buyer's agent team asks eventually.
The short answer: yes, they can — but not natively, and not in real time without middleware.
What Follow Up Boss Actually Offers
Follow Up Boss has a well-documented public API and supports webhooks out of its own platform — meaning you can receive notifications when contacts change in FUB. The CRM is genuinely integration-friendly on its own end.
The problem is the other side of the equation. ShowingTime does not have a native Zapier trigger, a public API for buyer-side integrations, or any outbound webhook you can point at FUB. ShowingTime is owned by Zillow, was designed for MLS coordinators, and has no incentive to build open CRM connectivity for independent buyer's agent teams.
So the gap is entirely on ShowingTime's side. FUB is ready. ShowingTime isn't pushing anything.
The Manual Reality Most Teams Are Living
Without middleware, keeping Follow Up Boss current after a showing is a manual process. An agent (or VA) opens ShowingTime, sees the confirmation, opens FUB, finds the contact, updates the deal stage, adds a showing note, and sets a follow-up task. On a good day this takes 4 minutes. On a busy showing day — 6 showings, 3 agents — it either doesn't happen or it happens at 9 PM.
The cost isn't just time. It's the follow-up that fires 6 hours late because the process waited on a human. By the time the email lands, the buyer has already heard from someone faster.
The Middleware Approach: How It Works
The approach that actually closes the loop: intercept ShowingTime's confirmation emails at the inbound level, parse the structured data, and write it to Follow Up Boss via the FUB API.
Here's the sequence:
What Gets Written to Follow Up Boss
When Showing Signal parses a ShowingTime confirmation and writes to FUB, the following fields update by default:
FUB Contact: full_name, email, phone FUB Deal: stage → "Showing Scheduled" address → "1402 Elm Street, Austin TX" custom_showing_count → 3 custom_last_showing_dt → "2026-08-06T14:30:00Z" FUB Activity: note + timestamp logged automatically
Custom properties are fully supported. If your Follow Up Boss setup uses different field names, you map them in Showing Signal's field mapping step during onboarding — no code required.