--- title: "Follow Up Boss MCP server for AI agents - actionlake" description: "Give Claude 159 Follow Up Boss actions through one MCP server: people, team, deals, activity. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/follow-up-boss updated: 2026-10-10 --- Connectors · CRM & sales # Follow Up Boss MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Follow Up Boss and the rest of your systems. It gives your agent 159 Follow Up Boss actions (71 reads, 64 writes and 24 that wait for a confirmation) and holds the Follow Up Boss credential itself, so the agent never does. It paces Follow Up Boss's limits and records every call. [Connect Follow Up Boss free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "followupboss.people.list", intent: "check which Follow Up Boss account is connected" } # Search for people · read · 1 upstream call ``` - 159 actions in one signed file - 71 read look, never change - 64 write create and update - 24 wait for a yes destructive, confirmed first Set up ## Connect Follow Up Boss in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Follow Up Boss. Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `api_key` Follow Up Boss API key (Admin > API) - `x_system_key` Follow Up Boss system key (X-System-Key), issued when the integration is registered with Follow Up Boss - `x_system` Your Follow Up Boss x system - `x_system_key` Your Follow Up Boss x system key ``` account { op: "connections.requirements", service: "followupboss" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "followupboss.people.list" } # search for people · read · 1 upstream call check { action: "followupboss.people.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Follow Up Boss at a glance **Sign-in** Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `api_key` `x_system_key` **Setup fields** `x_system` `x_system_key` **Limits we pace to** 250 calls per 10 seconds, per connection **API covered** Follow Up Boss CRM API API v1`api.followupboss.com/v1` **Built from** Follow Up Boss's documentation, read 20 September 2026[docs.followupboss.com](https://docs.followupboss.com/reference/) [docs.followupboss.com](https://docs.followupboss.com/reference/authentication.md) [docs.followupboss.com](https://docs.followupboss.com/reference/pagination.md) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 71 of 71 reads, for up to an hour; a write clears what it affects **Ready-made plans** 9 in the store **Shared entities** 8, so ask can line Follow Up Boss up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Follow Up Boss. 159 actions in 11 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **71** read look, never change - **64** write create and update - **24** destructive wait for a confirmation 1. ### People 27 11 read · 12 write · 4 destructive Search for people · Manually add a new person · Create a person from a raw JSON body, including custom fields (keys prefixed `custom`) · Retrieve a person by id 2. ### Team 22 12 read · 6 write · 4 destructive Search for users · List groups · Retrieve information about the currently authenticated user · Retrieve a user by id 3. ### Deals 21 7 read · 10 write · 4 destructive Search for deals · Add a deal · Create a deal from a raw JSON body, including custom fields (keys prefixed `custom`) · Retrieve a deal by id 4. ### Activity 20 9 read · 8 write · 3 destructive Search for calls · Get a list of tasks · List text messages for a person or phone number · Add a call 5. ### Integrations 18 7 read · 8 write · 3 destructive Retrieves participants in an Inbox App conversation · Get a list of events for a given webhook · Subscribe to a new webhook · Lists Inbox App installation(s) and ID(s) for your Published Inbox App on the current FUB account 6. ### Calendar 15 6 read · 6 write · 3 destructive Search for appointments · Create an appointment · Retrieve an appointment by id · Update an appointment 7. ### Templates 12 6 read · 4 write · 2 destructive Lists all email templates · Lists all text message templates · Create a new email template · Create a text message template 8. ### Automation 10 6 read · 4 write · 0 destructive Get a list of Action Plans · Get a list of Automations · List Action Plans applied to a particular person or list people on a particular Action Plan · Get a list of pairings of Automations and the People on which they have or will be run **3 more areas · 14 actions** - Settings **6** - Marketing **5** - Leads **3** Top actions ## The Follow Up Boss API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 121 of Follow Up Boss's 124 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `followupboss.people.list` Search for people | Search for people. Paged (offset/limit); each page is one upstream call. | read | `crm.contact.list` 177 connectors | | `followupboss.deals.list` Search for deals | Search for deals. Paged (offset/limit); each page is one upstream call. | read | `crm.deal.list` 43 connectors | | `followupboss.users.list` Search for users | Search for users. Paged (offset/limit); each page is one upstream call. | read | `identity.user.list` 474 connectors | | `followupboss.people.create` Manually add a new person | Manually add a new person. | write | `crm.contact.create` 161 connectors | | `followupboss.appointments.list` Search for appointments | Search for appointments. Paged (offset/limit); each page is one upstream call. | read | `comm.event.list` 61 connectors | | `followupboss.calls.list` Search for calls | Search for calls. Paged (offset/limit); each page is one upstream call. | read | `comm.call.list` 44 connectors | | `followupboss.tasks.list` Get a list of tasks | Get a list of tasks. Paged (offset/limit); each page is one upstream call. | read | `work.task.list` 122 connectors | | `followupboss.deals.create` Add a deal | Add a deal. | write | `crm.deal.create` 43 connectors | | `followupboss.people.delete` Delete a person by id | Delete a person by id. | destructive | `crm.contact.delete` 147 connectors | | `followupboss.text_messages.list` List text messages for a person or phone number | List text messages for a person or phone number. Paged (offset/limit); each page is one upstream call. | read | `comm.sms.list` 19 connectors | | `followupboss.groups.list` List groups | List groups. Paged (offset/limit); each page is one upstream call. | read | `identity.group.list` 262 connectors | | `followupboss.appointments.create` Create an appointment | Create an appointment. | write | `comm.event.create` 52 connectors | Try it ## Prompts to paste into Claude. Each one names the Follow Up Boss actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which Follow Up Boss deals are due to close this month, and what are they worth in total? calls `followupboss.deals.list` 2. Plan write Close out an appointment and book the follow-up in Follow Up Boss. calls `followupboss.appointments.get` `followupboss.appointment_outcomes.get` `followupboss.appointments.update` `followupboss.calls.create` `followupboss.notes.create` +1 more 3. Plan write Advance a deal to a new stage with sign-off in Follow Up Boss. Ask me before anything is sent or changed. calls `followupboss.deals.get` `followupboss.stages.get` `followupboss.deals.update` `followupboss.notes.create` `followupboss.tasks.create` 4. Write write Manually add a new person in Follow Up Boss. Show me exactly what you will send before you save it. calls `followupboss.people.create` The plan store ## Ready-made plans for Follow Up Boss. 9 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design. 1. ### Report open deals and overdue tasks in a pipeline Use it when Someone asks how a pipeline is doing right now and wants deal and task numbers in one answer. **Effect** read **Steps** 5 **Needs** pipeline id **Install** `followupboss-pipeline-health-report` 2. ### Revive leads with no activity since a cutoff Use it when A batch of contacts has gone quiet and each one needs a fresh check-in task rather than being left to rot. **Effect** write **Steps** 3 · loops **Needs** cutoff **Install** `followupboss-stale-lead-revival` 3. ### Intake a new lead and start it on an action plan Use it when A new enquiry has arrived and the lead must be created in Follow Up Boss without duplicating an existing contact. **Effect** write **Steps** 5 **Needs** email, first name, last name and action plan id **Install** `followupboss-new-lead-intake` 4. ### Send a templated text to a filtered set of people Use it when A personalised text needs going out to a filtered group and the wording must be approved before anything sends. A person decides Send "_name_" to _number of items_ people. Sample: _message_ **Effect** write **Steps** 5 · loops **Needs** template id and from number **Install** `followupboss-template-text-blast` 5. ### Claim unclaimed leads and task the new owner Use it when Leads are sitting unclaimed and one agent is taking ownership of the backlog in a single sweep. **Effect** write **Steps** 5 · loops **Install** `followupboss-unclaimed-lead-sweep` 6. ### Advance a deal to a new stage with sign-off Use it when A deal needs moving to a different pipeline stage and the move should be signed off before it is written. A person decides Move deal _name_ to stage _name_ at price _price_. **Effect** write **Steps** 6 **Needs** deal id and stage id **Install** `followupboss-deal-stage-advance` 7. ### Close out an appointment and book the follow-up Use it when An appointment has just happened and the outcome, call log and follow-up task all need recording in one pass. **Effect** write **Steps** 7 **Needs** appointment id, outcome id and person id **Install** `followupboss-appointment-followup` 8. ### Audit webhooks and repoint the broken ones Use it when Webhook deliveries have stopped or look wrong and the registrations need auditing and repointing. A person decides Repoint _number of broken_ non-active webhooks on _account_ to _new url_. **Effect** write **Steps** 7 · loops **Needs** new url **Install** `followupboss-webhook-audit-repair` 9. ### Delete a duplicate contact after sign-off Use it when Two records clearly describe the same person and the spare one should be removed with a human signing off first. A person decides Delete duplicate contact _firstName_ _lastName_ (_id_), losing _number of items_ open tasks. **Effect** destructive **Steps** 6 **Needs** keep id and duplicate id **Install** `followupboss-duplicate-person-cleanup` install a plan ``` account { op: "plans.install", slug: "followupboss-pipeline-health-report" } # then ask for it by name; a schedule can run it on a timetable ``` Governance for Follow Up Boss ## Destructive actions wait for a yes. 24 Follow Up Boss actions are destructive. These are all of them: - Delete a person by id `followupboss.people.delete` - Delete a deal `followupboss.deals.delete` - Delete a user (administrators only) `followupboss.users.delete` - Delete an appointment `followupboss.appointments.delete` - Delete a task `followupboss.tasks.delete` - Delete a note `followupboss.notes.delete` - Delete a team by id, optionally moving its members to another team `followupboss.teams.delete` - Delete a group (admin accounts only) `followupboss.groups.delete` - Delete a stage `followupboss.stages.delete` - Delete a pipeline `followupboss.pipelines.delete` - Delete a relationship (needs access to the parent person) `followupboss.people_relationships.delete` - Delete a pond by id; its remaining contacts are re-assigned to assignTo `followupboss.ponds.delete` - Delete an email template; 403 while an Action Plan still uses it `followupboss.email_templates.delete` - Delete a text message template; 403 while an Action Plan still uses it `followupboss.text_message_templates.delete` - Delete an attachment by ID `followupboss.person_attachments.delete` - Delete a webhook (account owner or the registered system that created it) `followupboss.webhooks.delete` - Delete a deal attachment `followupboss.deal_attachments.delete` - Deactivates an installation of your Inbox App `followupboss.inbox_apps.deactivate` - Deletes an Inbox App conversation participant `followupboss.inbox_apps.remove_participant` - Delete a reaction `followupboss.reactions.delete` - Delete a custom field (account owners only) `followupboss.custom_fields.delete` - Delete a deals custom field (owner only) `followupboss.deal_custom_fields.delete` - Delete an appointment type `followupboss.appointment_types.delete` - Delete an appointment outcome `followupboss.appointment_outcomes.delete` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do followupboss.people.delete confirm_policy: **human** Delete a person by id? **intent:** the user asked me to delete a person by id run suspended · waiting for a named person · key _followupboss-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "followupboss-agent", allowed_actions: ["followupboss.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "followupboss.people.delete", approver: "lead@example.com" }, { match: "followupboss.deals.delete", approver: "lead@example.com" }, { match: "followupboss.users.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Follow Up Boss only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Follow Up Boss costs on actionlake. Every Follow Up Boss action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Follow Up Boss refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 159 Follow Up Boss actions - 159 actions page each page of a long list is one call - 71 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Follow Up Boss action. 159 actions by area: the id your agent calls, what it does, and its effect. **People 27** - `followupboss.people.check_duplicate` Check whether a person exists in Follow Up Boss read - `followupboss.people.claim` Claim a lead write - `followupboss.people.create` Manually add a new person write - `followupboss.people.create_raw` Create a person from a raw JSON body, including custom fields (keys prefixed `custom`) write - `followupboss.people.delete` Delete a person by id destructive - `followupboss.people.get` Retrieve a person by id read - `followupboss.people.ignore_unclaimed` Ignore a lead write - `followupboss.people.list` Search for people read - `followupboss.people.list_unclaimed` Get unclaimed leads read - `followupboss.people.update` Update a person by id write - `followupboss.people.update_raw` Update a person from a raw JSON body, including custom fields (keys prefixed `custom`) write - `followupboss.people_relationships.create` Create a new relationship for a person write - `followupboss.people_relationships.delete` Delete a relationship (needs access to the parent person) destructive - `followupboss.people_relationships.get` Get a specific relationship read - `followupboss.people_relationships.list` Get relationships between people in Follow Up Boss read - `followupboss.people_relationships.update` Update a relationship write - `followupboss.person_attachments.create` Attach a file to a person write - `followupboss.person_attachments.delete` Delete an attachment by ID destructive - `followupboss.person_attachments.get` Retrieve an attachment by ID read - `followupboss.person_attachments.update` Update an attachment by ID write - `followupboss.smart_lists.get` Retrieve a Smart List by id read - `followupboss.smart_lists.list` Get a list of Smart Lists read - `followupboss.stages.create` Create a new stage write - `followupboss.stages.delete` Delete a stage destructive - `followupboss.stages.get` Get a stage by id read - `followupboss.stages.list` Retrieve a list of stages read - `followupboss.stages.update` Update a stage write **Team 22** - `followupboss.groups.create` Create a new group write - `followupboss.groups.delete` Delete a group (admin accounts only) destructive - `followupboss.groups.get` Retrieve a group by id (not accessible to lender accounts) read - `followupboss.groups.list` List groups read - `followupboss.groups.list_round_robin` Lists groups and includes round-robin data read - `followupboss.groups.update` Update a group (admin accounts only) write - `followupboss.identity.get` Get identity and authentication information read - `followupboss.me.get` Retrieve information about the currently authenticated user read - `followupboss.ponds.create` Create a pond write - `followupboss.ponds.delete` Delete a pond by id; its remaining contacts are re-assigned to assignTo destructive - `followupboss.ponds.get` Get a pond by id read - `followupboss.ponds.list` Get a list of ponds read - `followupboss.ponds.update` Update a pond by id write - `followupboss.team_inboxes.list` Get a list of Team Inboxes read - `followupboss.teams.create` Create a new team write - `followupboss.teams.delete` Delete a team by id, optionally moving its members to another team destructive - `followupboss.teams.get` Get a team by id read - `followupboss.teams.list` Get a list of teams read - `followupboss.teams.update` Update a team by id write - `followupboss.users.delete` Delete a user (administrators only) destructive - `followupboss.users.get` Retrieve a user by id read - `followupboss.users.list` Search for users read **Deals 21** - `followupboss.deal_attachments.create` Add an attachment to a deal write - `followupboss.deal_attachments.delete` Delete a deal attachment destructive - `followupboss.deal_attachments.get` Get a deal attachment by id read - `followupboss.deal_attachments.update` Update a deal attachment write - `followupboss.deal_custom_fields.create` Create a deals custom field write - `followupboss.deal_custom_fields.delete` Delete a deals custom field (owner only) destructive - `followupboss.deal_custom_fields.get` Get a deals custom field by ID read - `followupboss.deal_custom_fields.list` List all deals custom fields available in your account read - `followupboss.deal_custom_fields.update` Update a deals custom field (owner only) write - `followupboss.deals.create` Add a deal write - `followupboss.deals.create_raw` Create a deal from a raw JSON body, including custom fields (keys prefixed `custom`) write - `followupboss.deals.delete` Delete a deal destructive - `followupboss.deals.get` Retrieve a deal by id read - `followupboss.deals.list` Search for deals read - `followupboss.deals.update` Update a deal write - `followupboss.deals.update_raw` Update a deal from a raw JSON body, including custom fields (keys prefixed `custom`) write - `followupboss.pipelines.create` Add a pipeline write - `followupboss.pipelines.delete` Delete a pipeline destructive - `followupboss.pipelines.get` Retrieve a pipeline by id read - `followupboss.pipelines.list` Search for pipelines read - `followupboss.pipelines.update` Update a pipeline write **Activity 20** - `followupboss.calls.create` Add a call write - `followupboss.calls.get` Retrieve a call by id read - `followupboss.calls.list` Search for calls read - `followupboss.calls.update` Update a call write - `followupboss.notes.create` Add a note write - `followupboss.notes.delete` Delete a note destructive - `followupboss.notes.get` Retrieve a note by id read - `followupboss.notes.update` Edit a note write - `followupboss.reactions.create` Add a reaction to a corresponding reference data object, e.g write - `followupboss.reactions.delete` Delete a reaction destructive - `followupboss.reactions.get` Fetch a reaction read - `followupboss.tasks.create` Create a new task write - `followupboss.tasks.delete` Delete a task destructive - `followupboss.tasks.get` Get a task by id read - `followupboss.tasks.list` Get a list of tasks read - `followupboss.tasks.update` Update a task write - `followupboss.text_messages.create` Create a record of an externally sent text message write - `followupboss.text_messages.get` Retrieve a text message by id read - `followupboss.text_messages.list` List text messages for a person or phone number read - `followupboss.threaded_replies.get` Fetches a threaded reply read **Integrations 18** - `followupboss.inbox_apps.add_message` Adds a message to an existing or new Inbox App conversation write - `followupboss.inbox_apps.add_note` Adds a note to an Inbox App conversation write - `followupboss.inbox_apps.add_participant` Adds a participant to an Inbox App conversation write - `followupboss.inbox_apps.add_system_message` Adds a system confirmation message to an existing or new Inbox App conversation write - `followupboss.inbox_apps.deactivate` Deactivates an installation of your Inbox App destructive - `followupboss.inbox_apps.install` Installs your Inbox App for an account write - `followupboss.inbox_apps.list_installed` Lists Inbox App installation(s) and ID(s) for your Published Inbox App on the current FUB account read - `followupboss.inbox_apps.list_participants` Retrieves participants in an Inbox App conversation read - `followupboss.inbox_apps.remove_participant` Deletes an Inbox App conversation participant destructive - `followupboss.inbox_apps.update_conversation` Updates an Inbox App conversation write - `followupboss.rate_limit.get_limits` Currently-configured rate limits for the calling partner system read - `followupboss.rate_limit.get_usage` 24-hour request volume, rate-limit hits, and currently-configured limits for the calling partner system read - `followupboss.webhook_events.get` Get a list of events for a given webhook read - `followupboss.webhooks.create` Subscribe to a new webhook write - `followupboss.webhooks.delete` Delete a webhook (account owner or the registered system that created it) destructive - `followupboss.webhooks.get` Get details of a specific webhook (account owner or the registered system that created it) read - `followupboss.webhooks.list` Get a list of webhooks read - `followupboss.webhooks.update` Update a webhook (account owner or the registered system that created it) write **Calendar 15** - `followupboss.appointment_outcomes.create` Create an appointment outcome write - `followupboss.appointment_outcomes.delete` Delete an appointment outcome destructive - `followupboss.appointment_outcomes.get` Retrieve an appointment outcome by ID read - `followupboss.appointment_outcomes.list` List appointment outcomes read - `followupboss.appointment_outcomes.update` Update an appointment outcome write - `followupboss.appointment_types.create` Create an appointment type write - `followupboss.appointment_types.delete` Delete an appointment type destructive - `followupboss.appointment_types.get` Retrieve an appointment type by ID read - `followupboss.appointment_types.list` List appointment types read - `followupboss.appointment_types.update` Update an appointment type write - `followupboss.appointments.create` Create an appointment write - `followupboss.appointments.delete` Delete an appointment destructive - `followupboss.appointments.get` Retrieve an appointment by id read - `followupboss.appointments.list` Search for appointments read - `followupboss.appointments.update` Update an appointment write **Templates 12** - `followupboss.email_templates.create` Create a new email template write - `followupboss.email_templates.delete` Delete an email template; 403 while an Action Plan still uses it destructive - `followupboss.email_templates.get` Retrieve an email template by id, including the Action Plans using it read - `followupboss.email_templates.list` Lists all email templates read - `followupboss.email_templates.merge` Merge an email template with multiple recipients read - `followupboss.email_templates.update` Update an email template write - `followupboss.text_message_templates.create` Create a text message template write - `followupboss.text_message_templates.delete` Delete a text message template; 403 while an Action Plan still uses it destructive - `followupboss.text_message_templates.get` Retrieve a text message template by id read - `followupboss.text_message_templates.list` Lists all text message templates read - `followupboss.text_message_templates.merge` Merge a text message template with multiple recipients read - `followupboss.text_message_templates.update` Update a text message template write **Automation 10** - `followupboss.action_plans.list` Get a list of Action Plans read - `followupboss.action_plans_people.create` Apply an Action Plan to a person write - `followupboss.action_plans_people.list` List Action Plans applied to a particular person or list people on a particular Action Plan read - `followupboss.action_plans_people.update` Update the status of an Action Plan to Person relationship (planned for deprecation under Automations 2.0) write - `followupboss.automations.get` Retrieve an Automation by ID read - `followupboss.automations.list` Get a list of Automations read - `followupboss.automations_people.create` Manually trigger an Automation for a specified Person write - `followupboss.automations_people.get` Retrieve an Automation-Person pairing read - `followupboss.automations_people.list` Get a list of pairings of Automations and the People on which they have or will be run read - `followupboss.automations_people.update` Pause or unpause an Automation for a Person write **Settings 6** - `followupboss.custom_fields.create` Create a custom field write - `followupboss.custom_fields.delete` Delete a custom field (account owners only) destructive - `followupboss.custom_fields.get` Get a custom field by id read - `followupboss.custom_fields.list` List all custom fields read - `followupboss.custom_fields.update` Update a custom field (account owners only) write - `followupboss.timeframes.list` Get a list of timeframes read **Marketing 5** - `followupboss.em_campaigns.create` Create an email marketing campaign write - `followupboss.em_campaigns.list` List email marketing campaigns read - `followupboss.em_campaigns.update` Update an email marketing campaign (owners and admins) write - `followupboss.em_events.create` Notify Follow Up Boss about marketing emails sent, opens, clicks, bounces, unsubscribes and spam reports write - `followupboss.em_events.list` List email marketing events read **Leads 3** - `followupboss.events.create` Send in a lead or an event related to a lead write - `followupboss.events.get` Retrieve a single event by id read - `followupboss.events.list` Search for events read Questions ## The Follow Up Boss MCP server, answered. **Is there a Follow Up Boss MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 159 Follow Up Boss actions across people, team, deals and activity, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Follow Up Boss. **What do I need to connect Follow Up Boss?** Follow Up Boss API key (Admin > API) and Follow Up Boss system key (X-System-Key), issued when the integration is registered with Follow Up Boss. Plus your x system and your x system key. The free call account { op: "connections.requirements", service: "followupboss" } lists exactly what to paste. **Can an AI agent delete or change things in Follow Up Boss?** Only if its key allows it, and only with an explicit confirmation. 24 Follow Up Boss actions are destructive, including delete a person by id, delete a deal and delete a user (administrators only). Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Follow Up Boss API limit?** actionlake paces every call to the limits in the Follow Up Boss service file: 250 calls per 10 seconds per connection. Repeated reads are answered from cache (71 Follow Up Boss actions can be), which never reaches Follow Up Boss. **What does a Follow Up Boss action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (159 Follow Up Boss actions page). Cache hits, searches, dry runs and calls Follow Up Boss refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Follow Up Boss API does it cover?** The Follow Up Boss CRM API API v1 at api.followupboss.com/v1. It is built from Follow Up Boss's documentation as read on 20 September 2026. 159 actions in 11 areas, each one in the signed service file (version 1.0.0). **Does actionlake keep my Follow Up Boss data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Follow Up Boss credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Follow Up Boss Shares the most action names with - [Close 72](https://actionlake.com/connectors/close) - [Pipedrive 57](https://actionlake.com/connectors/pipedrive) - [ActiveCampaign 44](https://actionlake.com/connectors/activecampaign) - [HubSpot Deals 43](https://actionlake.com/connectors/hubspot-deals) - [Recruit CRM 37](https://actionlake.com/connectors/recruit-crm) - [Salesloft 33](https://actionlake.com/connectors/salesloft) Joins with, on shared entities - [HaloPSA 5](https://actionlake.com/connectors/halopsa) - [Odoo 5](https://actionlake.com/connectors/odoo) - [ERPNext (Frappe) 5](https://actionlake.com/connectors/erpnext-frappe) - [ScalePad 5](https://actionlake.com/connectors/scalepad) - [Planning Center 4](https://actionlake.com/connectors/planning-center) - [Unified.to 4](https://actionlake.com/connectors/unified-to) Browse - [All CRM & sales connectors](https://actionlake.com/connectors/category/crm-and-sales) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Follow Up Boss; the name is the vendor's own. Counts are from the Follow Up Boss service file, version 1.0.0. ## Give your agent Follow Up Boss today. [Connect Follow Up Boss free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/follow-up-boss More: https://actionlake.com/llms.txt