Skip to content

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.

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
  • 159actionsin one signed file
  • 71readlook, never change
  • 64writecreate and update
  • 24wait for a yesdestructive, 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_keyFollow Up Boss API key (Admin > API)
    • x_system_keyFollow Up Boss system key (X-System-Key), issued when the integration is registered with Follow Up Boss
    • x_systemYour Follow Up Boss x system
    • x_system_keyYour 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 callcheck { 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_keyx_system_key
Setup fields
x_systemx_system_key
Limits we pace to
250 calls per 10 seconds, per connection
API covered
Follow Up Boss CRM API API v1api.followupboss.com/v1
Built from
Follow Up Boss's documentation, read 20 September 2026docs.followupboss.comdocs.followupboss.comdocs.followupboss.com
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.

  • 71readlook, never change
  • 64writecreate and update
  • 24destructivewait 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.

ActionWhat it doesEffectSame name in
followupboss.people.listSearch for peopleSearch for people. Paged (offset/limit); each page is one upstream call.readcrm.contact.list177 connectors
followupboss.deals.listSearch for dealsSearch for deals. Paged (offset/limit); each page is one upstream call.readcrm.deal.list43 connectors
followupboss.users.listSearch for usersSearch for users. Paged (offset/limit); each page is one upstream call.readidentity.user.list474 connectors
followupboss.people.createManually add a new personManually add a new person.writecrm.contact.create161 connectors
followupboss.appointments.listSearch for appointmentsSearch for appointments. Paged (offset/limit); each page is one upstream call.readcomm.event.list61 connectors
followupboss.calls.listSearch for callsSearch for calls. Paged (offset/limit); each page is one upstream call.readcomm.call.list44 connectors
followupboss.tasks.listGet a list of tasksGet a list of tasks. Paged (offset/limit); each page is one upstream call.readwork.task.list122 connectors
followupboss.deals.createAdd a dealAdd a deal.writecrm.deal.create43 connectors
followupboss.people.deleteDelete a person by idDelete a person by id.destructivecrm.contact.delete147 connectors
followupboss.text_messages.listList text messages for a person or phone numberList text messages for a person or phone number. Paged (offset/limit); each page is one upstream call.readcomm.sms.list19 connectors
followupboss.groups.listList groupsList groups. Paged (offset/limit); each page is one upstream call.readidentity.group.list262 connectors
followupboss.appointments.createCreate an appointmentCreate an appointment.writecomm.event.create52 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. Readread

    Which Follow Up Boss deals are due to close this month, and what are they worth in total?

    callsfollowupboss.deals.list

  2. Planwrite

    Close out an appointment and book the follow-up in Follow Up Boss.

    callsfollowupboss.appointments.getfollowupboss.appointment_outcomes.getfollowupboss.appointments.updatefollowupboss.calls.createfollowupboss.notes.create+1 more

  3. Planwrite

    Advance a deal to a new stage with sign-off in Follow Up Boss. Ask me before anything is sent or changed.

    callsfollowupboss.deals.getfollowupboss.stages.getfollowupboss.deals.updatefollowupboss.notes.createfollowupboss.tasks.create

  4. Writewrite

    Manually add a new person in Follow Up Boss. Show me exactly what you will send before you save it.

    callsfollowupboss.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 decidesSend "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 decidesMove 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 decidesRepoint 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 decidesDelete 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 idfollowupboss.people.delete
  • Delete a dealfollowupboss.deals.delete
  • Delete a user (administrators only)followupboss.users.delete
  • Delete an appointmentfollowupboss.appointments.delete
  • Delete a taskfollowupboss.tasks.delete
  • Delete a notefollowupboss.notes.delete
  • Delete a team by id, optionally moving its members to another teamfollowupboss.teams.delete
  • Delete a group (admin accounts only)followupboss.groups.delete
  • Delete a stagefollowupboss.stages.delete
  • Delete a pipelinefollowupboss.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 assignTofollowupboss.ponds.delete
  • Delete an email template; 403 while an Action Plan still uses itfollowupboss.email_templates.delete
  • Delete a text message template; 403 while an Action Plan still uses itfollowupboss.text_message_templates.delete
  • Delete an attachment by IDfollowupboss.person_attachments.delete
  • Delete a webhook (account owner or the registered system that created it)followupboss.webhooks.delete
  • Delete a deal attachmentfollowupboss.deal_attachments.delete
  • Deactivates an installation of your Inbox Appfollowupboss.inbox_apps.deactivate
  • Deletes an Inbox App conversation participantfollowupboss.inbox_apps.remove_participant
  • Delete a reactionfollowupboss.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 typefollowupboss.appointment_types.delete
  • Delete an appointment outcomefollowupboss.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.

dofollowupboss.people.deleteconfirm_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: "[email protected]" },    { match: "followupboss.deals.delete", approver: "[email protected]" },    { match: "followupboss.users.delete", approver: "[email protected]" }  ]}
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.

  • 1upstream call per actionall 159 Follow Up Boss actions
  • 159actions pageeach page of a long list is one call
  • 71reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Follow Up Boss action.

159 actions by area: the id your agent calls, what it does, and its effect.

People27
  • followupboss.people.check_duplicateCheck whether a person exists in Follow Up Bossread
  • followupboss.people.claimClaim a leadwrite
  • followupboss.people.createManually add a new personwrite
  • followupboss.people.create_rawCreate a person from a raw JSON body, including custom fields (keys prefixed `custom`)write
  • followupboss.people.deleteDelete a person by iddestructive
  • followupboss.people.getRetrieve a person by idread
  • followupboss.people.ignore_unclaimedIgnore a leadwrite
  • followupboss.people.listSearch for peopleread
  • followupboss.people.list_unclaimedGet unclaimed leadsread
  • followupboss.people.updateUpdate a person by idwrite
  • followupboss.people.update_rawUpdate a person from a raw JSON body, including custom fields (keys prefixed `custom`)write
  • followupboss.people_relationships.createCreate a new relationship for a personwrite
  • followupboss.people_relationships.deleteDelete a relationship (needs access to the parent person)destructive
  • followupboss.people_relationships.getGet a specific relationshipread
  • followupboss.people_relationships.listGet relationships between people in Follow Up Bossread
  • followupboss.people_relationships.updateUpdate a relationshipwrite
  • followupboss.person_attachments.createAttach a file to a personwrite
  • followupboss.person_attachments.deleteDelete an attachment by IDdestructive
  • followupboss.person_attachments.getRetrieve an attachment by IDread
  • followupboss.person_attachments.updateUpdate an attachment by IDwrite
  • followupboss.smart_lists.getRetrieve a Smart List by idread
  • followupboss.smart_lists.listGet a list of Smart Listsread
  • followupboss.stages.createCreate a new stagewrite
  • followupboss.stages.deleteDelete a stagedestructive
  • followupboss.stages.getGet a stage by idread
  • followupboss.stages.listRetrieve a list of stagesread
  • followupboss.stages.updateUpdate a stagewrite
Team22
  • followupboss.groups.createCreate a new groupwrite
  • followupboss.groups.deleteDelete a group (admin accounts only)destructive
  • followupboss.groups.getRetrieve a group by id (not accessible to lender accounts)read
  • followupboss.groups.listList groupsread
  • followupboss.groups.list_round_robinLists groups and includes round-robin dataread
  • followupboss.groups.updateUpdate a group (admin accounts only)write
  • followupboss.identity.getGet identity and authentication informationread
  • followupboss.me.getRetrieve information about the currently authenticated userread
  • followupboss.ponds.createCreate a pondwrite
  • followupboss.ponds.deleteDelete a pond by id; its remaining contacts are re-assigned to assignTodestructive
  • followupboss.ponds.getGet a pond by idread
  • followupboss.ponds.listGet a list of pondsread
  • followupboss.ponds.updateUpdate a pond by idwrite
  • followupboss.team_inboxes.listGet a list of Team Inboxesread
  • followupboss.teams.createCreate a new teamwrite
  • followupboss.teams.deleteDelete a team by id, optionally moving its members to another teamdestructive
  • followupboss.teams.getGet a team by idread
  • followupboss.teams.listGet a list of teamsread
  • followupboss.teams.updateUpdate a team by idwrite
  • followupboss.users.deleteDelete a user (administrators only)destructive
  • followupboss.users.getRetrieve a user by idread
  • followupboss.users.listSearch for usersread
Deals21
  • followupboss.deal_attachments.createAdd an attachment to a dealwrite
  • followupboss.deal_attachments.deleteDelete a deal attachmentdestructive
  • followupboss.deal_attachments.getGet a deal attachment by idread
  • followupboss.deal_attachments.updateUpdate a deal attachmentwrite
  • followupboss.deal_custom_fields.createCreate a deals custom fieldwrite
  • followupboss.deal_custom_fields.deleteDelete a deals custom field (owner only)destructive
  • followupboss.deal_custom_fields.getGet a deals custom field by IDread
  • followupboss.deal_custom_fields.listList all deals custom fields available in your accountread
  • followupboss.deal_custom_fields.updateUpdate a deals custom field (owner only)write
  • followupboss.deals.createAdd a dealwrite
  • followupboss.deals.create_rawCreate a deal from a raw JSON body, including custom fields (keys prefixed `custom`)write
  • followupboss.deals.deleteDelete a dealdestructive
  • followupboss.deals.getRetrieve a deal by idread
  • followupboss.deals.listSearch for dealsread
  • followupboss.deals.updateUpdate a dealwrite
  • followupboss.deals.update_rawUpdate a deal from a raw JSON body, including custom fields (keys prefixed `custom`)write
  • followupboss.pipelines.createAdd a pipelinewrite
  • followupboss.pipelines.deleteDelete a pipelinedestructive
  • followupboss.pipelines.getRetrieve a pipeline by idread
  • followupboss.pipelines.listSearch for pipelinesread
  • followupboss.pipelines.updateUpdate a pipelinewrite
Activity20
  • followupboss.calls.createAdd a callwrite
  • followupboss.calls.getRetrieve a call by idread
  • followupboss.calls.listSearch for callsread
  • followupboss.calls.updateUpdate a callwrite
  • followupboss.notes.createAdd a notewrite
  • followupboss.notes.deleteDelete a notedestructive
  • followupboss.notes.getRetrieve a note by idread
  • followupboss.notes.updateEdit a notewrite
  • followupboss.reactions.createAdd a reaction to a corresponding reference data object, e.gwrite
  • followupboss.reactions.deleteDelete a reactiondestructive
  • followupboss.reactions.getFetch a reactionread
  • followupboss.tasks.createCreate a new taskwrite
  • followupboss.tasks.deleteDelete a taskdestructive
  • followupboss.tasks.getGet a task by idread
  • followupboss.tasks.listGet a list of tasksread
  • followupboss.tasks.updateUpdate a taskwrite
  • followupboss.text_messages.createCreate a record of an externally sent text messagewrite
  • followupboss.text_messages.getRetrieve a text message by idread
  • followupboss.text_messages.listList text messages for a person or phone numberread
  • followupboss.threaded_replies.getFetches a threaded replyread
Integrations18
  • followupboss.inbox_apps.add_messageAdds a message to an existing or new Inbox App conversationwrite
  • followupboss.inbox_apps.add_noteAdds a note to an Inbox App conversationwrite
  • followupboss.inbox_apps.add_participantAdds a participant to an Inbox App conversationwrite
  • followupboss.inbox_apps.add_system_messageAdds a system confirmation message to an existing or new Inbox App conversationwrite
  • followupboss.inbox_apps.deactivateDeactivates an installation of your Inbox Appdestructive
  • followupboss.inbox_apps.installInstalls your Inbox App for an accountwrite
  • followupboss.inbox_apps.list_installedLists Inbox App installation(s) and ID(s) for your Published Inbox App on the current FUB accountread
  • followupboss.inbox_apps.list_participantsRetrieves participants in an Inbox App conversationread
  • followupboss.inbox_apps.remove_participantDeletes an Inbox App conversation participantdestructive
  • followupboss.inbox_apps.update_conversationUpdates an Inbox App conversationwrite
  • followupboss.rate_limit.get_limitsCurrently-configured rate limits for the calling partner systemread
  • followupboss.rate_limit.get_usage24-hour request volume, rate-limit hits, and currently-configured limits for the calling partner systemread
  • followupboss.webhook_events.getGet a list of events for a given webhookread
  • followupboss.webhooks.createSubscribe to a new webhookwrite
  • followupboss.webhooks.deleteDelete a webhook (account owner or the registered system that created it)destructive
  • followupboss.webhooks.getGet details of a specific webhook (account owner or the registered system that created it)read
  • followupboss.webhooks.listGet a list of webhooksread
  • followupboss.webhooks.updateUpdate a webhook (account owner or the registered system that created it)write
Calendar15
  • followupboss.appointment_outcomes.createCreate an appointment outcomewrite
  • followupboss.appointment_outcomes.deleteDelete an appointment outcomedestructive
  • followupboss.appointment_outcomes.getRetrieve an appointment outcome by IDread
  • followupboss.appointment_outcomes.listList appointment outcomesread
  • followupboss.appointment_outcomes.updateUpdate an appointment outcomewrite
  • followupboss.appointment_types.createCreate an appointment typewrite
  • followupboss.appointment_types.deleteDelete an appointment typedestructive
  • followupboss.appointment_types.getRetrieve an appointment type by IDread
  • followupboss.appointment_types.listList appointment typesread
  • followupboss.appointment_types.updateUpdate an appointment typewrite
  • followupboss.appointments.createCreate an appointmentwrite
  • followupboss.appointments.deleteDelete an appointmentdestructive
  • followupboss.appointments.getRetrieve an appointment by idread
  • followupboss.appointments.listSearch for appointmentsread
  • followupboss.appointments.updateUpdate an appointmentwrite
Templates12
  • followupboss.email_templates.createCreate a new email templatewrite
  • followupboss.email_templates.deleteDelete an email template; 403 while an Action Plan still uses itdestructive
  • followupboss.email_templates.getRetrieve an email template by id, including the Action Plans using itread
  • followupboss.email_templates.listLists all email templatesread
  • followupboss.email_templates.mergeMerge an email template with multiple recipientsread
  • followupboss.email_templates.updateUpdate an email templatewrite
  • followupboss.text_message_templates.createCreate a text message templatewrite
  • followupboss.text_message_templates.deleteDelete a text message template; 403 while an Action Plan still uses itdestructive
  • followupboss.text_message_templates.getRetrieve a text message template by idread
  • followupboss.text_message_templates.listLists all text message templatesread
  • followupboss.text_message_templates.mergeMerge a text message template with multiple recipientsread
  • followupboss.text_message_templates.updateUpdate a text message templatewrite
Automation10
  • followupboss.action_plans.listGet a list of Action Plansread
  • followupboss.action_plans_people.createApply an Action Plan to a personwrite
  • followupboss.action_plans_people.listList Action Plans applied to a particular person or list people on a particular Action Planread
  • followupboss.action_plans_people.updateUpdate the status of an Action Plan to Person relationship (planned for deprecation under Automations 2.0)write
  • followupboss.automations.getRetrieve an Automation by IDread
  • followupboss.automations.listGet a list of Automationsread
  • followupboss.automations_people.createManually trigger an Automation for a specified Personwrite
  • followupboss.automations_people.getRetrieve an Automation-Person pairingread
  • followupboss.automations_people.listGet a list of pairings of Automations and the People on which they have or will be runread
  • followupboss.automations_people.updatePause or unpause an Automation for a Personwrite
Settings6
  • followupboss.custom_fields.createCreate a custom fieldwrite
  • followupboss.custom_fields.deleteDelete a custom field (account owners only)destructive
  • followupboss.custom_fields.getGet a custom field by idread
  • followupboss.custom_fields.listList all custom fieldsread
  • followupboss.custom_fields.updateUpdate a custom field (account owners only)write
  • followupboss.timeframes.listGet a list of timeframesread
Marketing5
  • followupboss.em_campaigns.createCreate an email marketing campaignwrite
  • followupboss.em_campaigns.listList email marketing campaignsread
  • followupboss.em_campaigns.updateUpdate an email marketing campaign (owners and admins)write
  • followupboss.em_events.createNotify Follow Up Boss about marketing emails sent, opens, clicks, bounces, unsubscribes and spam reportswrite
  • followupboss.em_events.listList email marketing eventsread
Leads3
  • followupboss.events.createSend in a lead or an event related to a leadwrite
  • followupboss.events.getRetrieve a single event by idread
  • followupboss.events.listSearch for eventsread

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.

Give your agent Follow Up Boss today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.