Follow Up Boss integration. Manage Persons, Organizations, Leads, Deals, Pipelines, Activities and more. Use when the user wants to interact with Follow Up Boss data.
Follow Up Boss is a CRM platform designed for real estate professionals. It helps agents and teams manage leads, automate follow-up communication, and track deal progress. Real estate agents, brokers, and teams use it to streamline their sales processes and improve client relationships.
Official docs: https://developers.followupboss.com/
Use action names and parameters as needed.
This skill uses the Membrane CLI to interact with Follow Up Boss. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/cli
membrane login --tenant
A browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete <code>.
membrane search follow-up-boss --elementType=connector --json
output.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --json
When you are not sure if connection already exists:
membrane connection list --json
connectionIdWhen you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
This will return action objects with id and inputSchema in it, so you will know how to run it.
| Name | Key | Description |
|---|---|---|
| List People | list-people | List people/contacts from Follow Up Boss with optional filtering |
| List Deals | list-deals | List deals from Follow Up Boss |
| List Tasks | list-tasks | List tasks from Follow Up Boss |
| List Appointments | list-appointments | List appointments from Follow Up Boss |
| List Users | list-users | List all users in the Follow Up Boss account |
| Get Person | get-person | Get a person/contact by ID from Follow Up Boss |
| Get Deal | get-deal | Get a deal by ID |
| Get Task | get-task | Get a task by ID |
| Get Appointment | get-appointment | Get an appointment by ID |
| Create Person | create-person | Manually add a new person/contact to Follow Up Boss. |
| Create Deal | create-deal | Create a new deal in Follow Up Boss |
| Create Task | create-task | Create a new task in Follow Up Boss |
| Create Appointment | create-appointment | Create a new appointment in Follow Up Boss |
| Update Person | update-person | Update an existing person/contact in Follow Up Boss |
| Update Deal | update-deal | Update an existing deal |
| Update Task | update-task | Update an existing task |
| Update Appointment | update-appointment | Update an existing appointment |
| Delete Person | delete-person | Delete a person/contact from Follow Up Boss |
| Delete Deal | delete-deal | Delete a deal |
| Delete Task | delete-task | Delete a task |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
To pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
When the available actions don't cover your use case, you can send requests directly to the Follow Up Boss API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpoint
Common options:
| Flag | Description | |
|---|---|---|
-X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET | |
-H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" | |
-d, --data | Request body (string) | |
--json | Shorthand to send a JSON body and set Content-Type: application/json | |
--rawData | Send the body as-is without any processing | |
--query | Query-string parameter (repeatable), e.g. --query "limit=10" | |
--pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.