Three recipes for Follow Up Boss. Each names its trigger and the BlueBot step, lists the fields to map and says how to test it with your own number before anyone else gets a text.
How Follow Up Boss connects
Zapier: BlueBot’s Zapier app has a Send Text action and instant triggers for incoming texts and every change of state.
API: Your own code calls BlueBot’s REST API and listens to its signed webhooks.
Start a Zap with Follow Up Boss’s trigger for a new person.
Add BlueBot’s Send Text action and map the person’s phone to To.
Write the text with their first name mapped in.
Map the fields
BlueBot field
Map it to
To
The person’s mobile number from Follow Up Boss. US numbers can leave off the +1.
Text
Hi {{first_name}}, this is Jordan with Harbor Realty. I saw your request come in. Would you like to see some homes this week?
{{first_name}} in the text
Follow Up Boss’s first name field.
Metadata
source set to follow-up-boss, and record_id set to the record’s id, so the status and reply webhooks for this text can find the record again.
Service
Auto, the default: iMessage when the person uses it, otherwise SMS through your iPhone.
Test it
Put your own number in To and press Test step. A text arrives on your phone from your own number, and Zapier shows the message BlueBot returned with state: "queued". Then map Follow Up Boss’s field back into To and turn the Zap on.
Log replies on the person
Part
What it is
Trigger
A text comes in (BlueBot’s message.received webhook)
Action
A webhook for message.received starts it, and Follow Up Boss takes the text
Point a BlueBot webhook for message.received at your own endpoint.
Find the person by the sender’s number through Follow Up Boss’s API.
Log the reply on the person so it shows with the rest of their history.
Map the fields
From BlueBot
Into Follow Up Boss
data.from
The phone number to find the person by in Follow Up Boss. It’s in E.164 (+15555550123); search by the last 10 digits if Follow Up Boss stores numbers another way.
data.text
The words, for a note, a row or a message. Null when the person sent only a picture.
data.received_at
When it came in, in UTC.
data.files
Pictures and voice memos. Each url works for an hour, so copy a file you want to keep.
data.chat_id
Set when the text came in a group chat; null for a one-to-one text.
Test it
Run bluebot listen --forward-to http://localhost:3000/webhooks, then text your BlueBot number from another phone. The CLI forwards the event to your handler, signed. BlueBot copies texts from people you’ve texted through it, unless you set Which chats to copy to Everything.
Start a Zap with Follow Up Boss’s trigger for a new person.
Add BlueBot’s Send Text action with your own number in To.
Put the lead’s name, phone and source in Text.
Map the fields
BlueBot field
Map it to
To
The person’s mobile number from Follow Up Boss. US numbers can leave off the +1.
Text
New lead: {{name}}, {{phone}}, from {{source}}.
{{name}} in the text
Follow Up Boss’s name field.
{{phone}} in the text
Follow Up Boss’s phone field.
{{source}} in the text
Follow Up Boss’s source field.
Metadata
source set to follow-up-boss, and record_id set to the record’s id, so the status and reply webhooks for this text can find the record again.
Service
Auto, the default: iMessage when the person uses it, otherwise SMS through your iPhone.
Test it
Put your own number in To and press Test step. A text arrives on your phone from your own number, and Zapier shows the message BlueBot returned with state: "queued". Then map Follow Up Boss’s field back into To and turn the Zap on.
Before you turn it on
Text only people who asked to hear from you. Anyone who replies STOP goes on your stop list, and BlueBot cancels texts to them. Stop words
A text that can’t go yet waits with a hold rather than failing: quiet hours, your Mac away, a daily limit. Holds