Follow Up Boss

Work leads in Follow Up Boss the moment they arrive. Agents create and update people, log events and notes, manage deals, and read pipelines, stages, and users to route real estate follow-up.

10 actions Basic auth available

Follow Up Boss website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A buyer inquiry arrives from the website form or a listing portal feed

List People searches the inquiry's email and phone for an existing relationship

The flow compares any match against its stage, source, and assigned agent

When the inquiry matches a past client or an active deal, the team lead picks the route before any automation fires

Create Event pushes the inquiry into Follow Up Boss, firing lead routing and action plans

Create Note logs the full inquiry context on the person's timeline

The assigned agent gets an alert with the lead details and source attribution

What This Integration Enables

Follow Up Boss is built on a blunt premise: in real estate, the first agent to respond usually wins the client, so a lead that waits is a lead that is gone. The platform's entire design serves that premise, and Create Event is its front door: one call that creates or updates the person, attributes the source, and fires the team's routing rules and action plans. FlowRunner's job is to make sure every lead source in the business reaches that front door the moment it fires, and that the exceptions reach a person instead. - Push inquiries from forms, portals, and imports through Create Event so routing and action plans fire automatically - Create and update people with emails, phones, tags, stages, and sources, leaning on Follow Up Boss's built-in dedup - Log call summaries and showing feedback to the timeline with Create Note - Track transactions with List Deals and Create Deal against real pipeline stages - Resolve agents and stages with List Users and List Stages so IDs are never hardcoded

Without FlowRunner

Speed-to-lead depends on who is at a desk Portal inquiries sit in an inbox until someone forwards them, and the hottest leads cool first

Source attribution is guesswork Nobody can say which portal or campaign produced the closing, so spend decisions run on instinct

Call context dies with the call Showing feedback and phone summaries live in agents' heads, not on the record

With FlowRunner

Every source feeds one pipe Forms, portals, and spreadsheets all hit Create Event, so routing and action plans fire within seconds of the inquiry

Attribution rides in with the lead Each event carries its source, so the pipeline report says which channels actually produce deals

The timeline is the record Agents log summaries and feedback as notes automatically, and the next person to open the lead reads the whole story

Use Case Scenarios

Every inquiry hits the pipe in seconds

A buyer fills out a [Typeform](/integrations/typeform) on a listing page. The flow calls List People to check for an existing relationship, then Create Event with the inquiry details, the property address, and the source. Follow Up Boss routes the lead to the on-duty agent and starts the action plan. Create Note attaches the original inquiry text to the timeline, and a [Slack](/integrations/slack) message pings the assigned agent with the context. The same flow handles the portal email feed, so a Zillow inquiry at 9 pm gets the identical treatment as a website form at 9 am.

Showing feedback that actually lands on the record

After each showing block, a recap arrives from the team's meeting notes tool or a quick form. The flow matches the client with List People, writes the feedback as Create Note on their timeline, and calls Update Person to adjust tags or stage when the feedback says the client is ready to write an offer. When an offer is accepted, the flow resolves the right pipeline stage with List Stages and creates the transaction with Create Deal, linked to the person and priced from the offer.

The Monday pipeline report nobody compiles by hand

On a schedule, the flow pulls List Deals filtered by pipeline and stage, joins in List People for the buyer details, and appends the snapshot to [Google Sheets](/integrations/google-sheets). Deals that have not moved stage in three weeks get flagged in the digest to [Slack](/integrations/slack), with the source attribution attached so the team lead sees which channels feed the stuck deals. List Users keeps the report grouped by the agent who owns each transaction.

Human-in-Loop Highlight

Create Event is not a quiet database write. It fires the team's action plans, which start texting and emailing a real person immediately, and a sent text cannot be recalled. The failure mode is specific: a past client, an agent's personal referral, or a party to an active deal comes through a portal feed looking like a cold lead, and the drip campaign treats them like one. So the FlowRunner agent checks first. When List People finds a match with deal history or an assigned agent, the flow holds the event and posts the evidence: this inquiry matches a person in Closed stage with 14 timeline notes, assigned to Dana. The team lead decides whether it routes as a new lead or lands as a note on the existing relationship. Only then does Create Event fire. The automation moves at portal speed; the decision about who gets the automated treatment stays human.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

10 actions

People

List People Retrieves a paginated list of people with free-text search and filtering. The lookup step that finds a person's ID and checks for an existing relationship before anything fires.
Get Person Retrieves a single person by ID, including emails, phones, tags, stage, source, and assigned agent. The full-context read before a routing decision.
Create Person Creates a new person with name, emails, phones, source, and stage. Follow Up Boss deduplicates on email and phone, so a matching person is updated rather than duplicated.
Update Person Updates an existing person by ID, changing only the fields provided. Used for stage moves, tag changes, and contact detail corrections.

Lead Capture

Create Event Creates a lead event, the core lead-capture endpoint. Submitting an event creates or updates the matching contact, attributes the source, and triggers lead routing and action plans. The step this page's human gate protects.

Timeline

Create Note Adds a note to a person's activity timeline with a subject and body. Where call summaries, showing feedback, and inquiry context land.

Deals

List Deals Retrieves a paginated list of deals with pipeline and stage filters. The read behind pipeline reports and stuck-deal sweeps.
Create Deal Creates a deal in a pipeline stage, optionally linked to a person and priced. The step that turns an accepted offer into a tracked transaction.

Account

List Users Retrieves the team members in the account with name, email, and role. Used to resolve agent IDs for assignment and reporting.
List Stages Retrieves the configured stages with ID, name, and pipeline. Used to resolve the stage ID before creating a deal.

Frequently Asked Questions

What can FlowRunner do with Follow Up Boss?

FlowRunner agents can run List People, Get Person, and Create Person in Follow Up Boss, plus 7 more actions.

Does connecting Follow Up Boss to FlowRunner require OAuth?

No. Follow Up Boss connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Follow Up Boss trigger a FlowRunner workflow automatically?

Follow Up Boss doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Follow Up Boss

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us