Resources · Make integration

Follow Up Boss Make integrationAutomate Follow Up Boss with Make.

What happens in your CRM the moment a new lead lands? The Follow Up Boss Make integration gives you 35 modules, including 7 instant triggers, to answer that without code. This page shows how to link your account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Follow Up Boss Make integration do for you?

The integration links your Follow Up Boss account to Make so that contacts, deals, notes, tasks and calls can move to and from your other tools. You build a scenario, which is the automation itself: a chain of modules, where each module is one brick such as a trigger, an action or a search.

A lead that never waits. Watch New Contact starts the scenario as soon as someone lands in Follow Up Boss, and Create a Task puts the first follow-up on the right person’s list. Add Apply an Action Plan to a Contact and the nurturing sequence starts on its own.

A pipeline your other tools can see. Watch Deal Stage Updated fires when a deal moves forward, so you can post the change to your team chat or update a row in a spreadsheet. If you already keep records in Airtable, the Airtable Make integration covers the other side of that flow.

Leads from outside, filed cleanly. Create an Inquiry or a Website Event sends a lead from a form or a landing page into Follow Up Boss, with Search Contacts first to avoid a duplicate.

One caveat: Make’s documentation page for Follow Up Boss says its content is AI-generated from the vendor’s own documentation, so check important details with Follow Up Boss directly. If you are weighing both automation tools, read n8n vs Make, and our Make review covers the platform as a whole.

Connect

How do you connect Follow Up Boss to Make?

  1. 01

    Generate an API key in Follow Up Boss

    Make signs in with an API key. In Follow Up Boss, open the Admin menu, go to the API section, click Generate and copy the key shown on screen. You need an active Follow Up Boss account with API access.

  2. 02

    Add a Follow Up Boss module and create the connection

    In your scenario, add any Follow Up Boss module and click Create a connection. A connection is your account linked to Make once and reused by every Follow Up Boss module. The Connection name field is optional, but a clear name helps when you have several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then save. From now on, Make can list your Follow Up Boss data inside the module fields, so you pick from real values instead of typing them.

First scenario

Your first scenario with Follow Up Boss

GoalWhen a new contact is created in Follow Up Boss, Make adds a follow-up task for that contact.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.

  2. 02

    Add Watch New Contact

    Search for Follow Up Boss, pick Watch New Contact, click Create a webhook, then Create a connection with your API key. This trigger is instant, so Follow Up Boss will call Make itself.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger and pick Create a Task. Map the contact from the previous module, so each new contact gets its own task.

  4. 04

    Test with Run once

    Click Run once, then add a test contact in Follow Up Boss. Open the bubble above each module to read the bundle it received, meaning the item passed along, here one contact.

  5. 05

    Switch it on

    Once the test task shows up in Follow Up Boss, switch the scenario on. Every new contact now runs the flow, and each module execution counts as one operation on your Make plan.

Triggers

What can start a Follow Up Boss scenario?

7 modules start a scenario when something happens in Follow Up Boss. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Follow Up Boss as soon as it happens.

Follow Up Boss1Watch Appointment Created

Watch Appointment Created

Instant trigger

In MakeTriggers when an appointment has been created.

This trigger gives you a scenario that runs every time an appointment is booked in Follow Up Boss, so the rest of your stack learns about the meeting without anyone copying it over.

How it fires
instant. Follow Up Boss calls Make through a webhook as soon as the appointment exists.
When to use it
you want the booking to reach a shared calendar, a prep checklist or a message to the person who will attend.
Watch out
the module is documented for newly created appointments, so do not count on it to catch a reschedule.
Follow Up Boss2Watch Contact Stage Updated

Watch Contact Stage Updated

Instant trigger

In MakeTriggers when a contact stage has been updated.

You get a scenario that reacts when a contact moves to another stage, which turns your stage changes into signals for the rest of your tools.

How it fires
instant. Follow Up Boss notifies Make through a webhook the moment the stage changes.
When to use it
a lead becomes active or closes, and you want a welcome email, a report line or a handoff to another team to follow.
Watch out
add a filter after the trigger when only one stage matters, otherwise every stage change spends operations.
Follow Up Boss3Watch Deal Stage Updated

Watch Deal Stage Updated

Instant trigger

In MakeTriggers when a deal stage has been updated.

With this trigger, each step forward in your pipeline can kick off work elsewhere, from a team announcement to an updated forecast sheet.

How it fires
instant. Follow Up Boss sends the change to Make through a webhook as soon as the deal stage is updated.
When to use it
a deal reaches a stage that needs paperwork, a notification or a record in another system.
Watch out
it covers stage changes only; for newly created deals, pick Watch New Deal instead.
Follow Up Boss4Watch New Contact

Watch New Contact

Instant trigger

In MakeTriggers when a contact has been created.

This is the trigger that makes lead handling automatic: the scenario starts with the fresh contact in hand, ready to be routed, tagged or copied elsewhere.

How it fires
instant. Follow Up Boss calls Make through a webhook as soon as the contact is created.
When to use it
the first reply to a lead matters, and you want a task, an action plan or an alert set up right away.
Watch out
if your scenario also creates contacts in Follow Up Boss, you can end up restarting it yourself, so keep the two flows apart.
Follow Up Boss5Watch New Deal

Watch New Deal

Instant trigger

In MakeTriggers when a new deal has been created.

Opening a deal becomes an event your other tools hear about, which helps when finance, operations or a manager needs to know early.

How it fires
instant. Follow Up Boss notifies Make through a webhook as soon as a new deal is created.
When to use it
every new deal needs a folder, a row in a tracking sheet or a message in a shared channel.
Watch out
the trigger sees the deal as it is at creation; later stage moves belong to Watch Deal Stage Updated.
Follow Up Boss6Watch New Website Event

Watch New Website Event

Instant trigger

In MakeTriggers when people perform an action on your IDX website.

You learn what visitors do on your IDX website and can act on it, for example by alerting the agent who owns that lead.

How it fires
instant. Follow Up Boss calls Make through a webhook as soon as someone performs an action on the site.
When to use it
a visitor’s activity is a buying signal and you want a task or a note to reflect it.
Watch out
busy sites send many events; filter on the actions that matter before any costly module, because each run uses operations.
Follow Up Boss7Watch Tags Added to a Contact

Watch Tags Added to a Contact

Instant trigger

In MakeTriggers when tags have been added to a contact.

Tags become switches: add one in Follow Up Boss and the scenario runs the work tied to it, which keeps your team’s habits inside the CRM.

How it fires
instant. Follow Up Boss sends the tagging to Make through a webhook as soon as it happens.
When to use it
an agent tags a contact “send brochure” or “needs callback” and expects the rest to happen.
Watch out
if the same scenario runs Add Tags to a Contact, it can trigger itself again; filter on the tag you watch.
Modules

What can Make do in Follow Up Boss?

Follow Up Boss gives you 28 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Follow Up Boss1

Add Tags to a Contact

Action

In MakeAdds tags to a contact.

Your contacts get labeled by the scenario, so segments stay accurate without manual tagging after each form or call.

When to use it
a lead comes from a known source and you want that origin visible on the contact card.
Watch out
a scenario started by Watch Tags Added to a Contact can loop if it tags the same contact again.
Follow Up Boss2

Apply an Action Plan to a Contact

Action

In MakeApplies a selected action plan to a contact.

This module starts one of your existing action plans on a contact, so the nurturing sequence you already designed kicks in without a click.

When to use it
right after Watch New Contact, when every new lead of a given source should get the same follow-up.
Watch out
the plan must already exist in Follow Up Boss; the module applies it, it does not build it.
Follow Up Boss3

Create a Contact

Action

In MakeCreates a new contact.

People from other tools arrive in Follow Up Boss as real contacts, ready for your team to work, instead of sitting in a spreadsheet.

When to use it
you collect names through an event list or a partner file and want them in the CRM.
Watch out
run Search Contacts first so you update an existing person instead of creating a duplicate.
Follow Up Boss4

Create a Deal

Action

In MakeCreates a new deal.

A deal opens in your pipeline from an outside signal, so the numbers your team reviews match what actually happened.

When to use it
a signed form or an accepted offer in another tool should become a tracked deal.
Watch out
keep the deal tied to the right contact by mapping it from a trigger or a search, not from free text.
Follow Up Boss5

Create an Inquiry or a Website Event

Action

In MakeSends in a lead or event related to a lead.

This module sends a lead, or an event about a lead, into Follow Up Boss the way a lead source would, so it enters your usual routing.

When to use it
leads come from a landing page, an ad form or a chatbot that Follow Up Boss does not read natively.
Watch out
choose it over Create a Contact when you want the entry handled as an incoming inquiry rather than a plain record.
Follow Up Boss6

Create a Note

Action

In MakeCreates a note on a contact.

Context from other tools lands on the contact’s timeline, so the agent opening the card sees the full story in one place.

When to use it
a survey answer, a support ticket or an email summary should stay attached to the person.
Watch out
a note is for reading; if someone must act, pair it with Create a Task so the action is not buried.
Follow Up Boss7

Create a Task

Action

In MakeCreates a task for a contact.

Follow-ups appear on your team’s to-do list the moment they are needed, which is how a new lead gets a call instead of a delay.

When to use it
after Watch New Contact or Watch Appointment Created, when a person has to do something next.
Watch out
map the contact from the trigger; a task without the right contact is hard to act on.
Follow Up Boss8

Delete a Contact

Action

In MakeDeletes a contact specified by ID.

This module removes a contact, found by its ID, which helps you keep test entries or known junk out of your CRM automatically.

When to use it
a scenario identifies a spam signup and you want it gone before anyone works it.
Watch out
the ID must point to the right person; check it with Get a Contact during your Run once test before switching the scenario on.
Follow Up Boss9

Delete a Deal

Action

In MakeDeletes a deal specified by ID.

You can clear a deal from the pipeline by its ID, keeping reports free of entries that should never have been there.

When to use it
a duplicate deal was opened by another scenario and you want to clean it as part of the same flow.
Watch out
when a deal simply stalls, Update a Deal keeps its history; deletion suits only real mistakes.
Follow Up Boss10

Delete a Note

Action

In MakeDeletes a note specified by ID.

This module takes a note off a contact, by its ID, so a scenario can tidy up what another automation wrote.

When to use it
a note carried outdated or wrong information and a correction flow should remove it.
Watch out
to fix a note rather than remove it, Update a Note is the gentler choice; find the ID with Search Notes.
Follow Up Boss11

Delete a Task

Action

In MakeDeletes a task specified by ID.

Tasks that no longer make sense disappear from your team’s list, identified by their ID, so nobody calls a lead that already closed.

When to use it
Watch Deal Stage Updated shows a closed deal and pending follow-ups should go.
Watch out
Search Tasks returns several bundles; delete only those that match your filter, not every result.
Follow Up Boss12

Get a Call

Action

In MakeRetrieves a call details specified by ID.

You pull the full details of one call, by its ID, so a later module can report on it or copy it into another tool.

When to use it
you already hold a call ID from Search Calls or Log a Call and need the whole record.
Watch out
it needs the ID; to find calls by other criteria, start with Search Calls.
Follow Up Boss13

Get a Contact

Action

In MakeRetrieves a contact details specified by ID.

This module fetches one contact’s complete record from its ID, which gives later modules every detail the trigger may not carry.

When to use it
a deal or a task trigger gives you a contact ID and you need the full record before writing elsewhere.
Watch out
it returns one contact only; when you have a name rather than an ID, use Search Contacts.
Follow Up Boss14

Get a Deal

Action

In MakeRetrieves details of a deal specified by ID.

You read one deal in full from its ID, so a message or a spreadsheet row can include its current details.

When to use it
Watch Deal Stage Updated fired and you want the complete deal before notifying finance.
Watch out
it reads a single deal; to list deals matching a condition, Search Deals is the right brick.
Follow Up Boss15

Get a Note

Action

In MakeRetrieves details of a note specified by ID.

This module returns the content of one note by its ID, useful when another tool should receive what an agent wrote.

When to use it
a note ID comes from Search Notes or a previous step and you need its text.
Watch out
without an ID, go through Search Notes first; this module cannot look notes up by content.
Follow Up Boss16

Get a Task

Action

In MakeRetrieves a task details specified by ID.

You fetch one task with its details, from its ID, to check its state before deciding what the scenario does next.

When to use it
a flow must confirm a follow-up is still open before sending a reminder.
Watch out
map the ID from Create a Task or Search Tasks instead of typing it by hand, since a typed ID breaks the moment the task changes.
Follow Up Boss17

Log a Call

Action

In MakeLogs a call on a contact.

Calls made outside Follow Up Boss end up on the contact’s history, so your call count reflects the real work.

When to use it
your phone or dialer tool records calls elsewhere and you want them on the contact card.
Watch out
map the contact carefully, ideally from Search Contacts, so the call lands on the right person.
Follow Up Boss18

Make an API Call

Action

In MakePerforms an arbitrary API call.

This module reaches any endpoint of the Follow Up Boss API with the same connection, so you are not stuck when a listed module does not cover your need.

When to use it
none of the listed actions or searches does what you want, such as an object the modules never touch.
Watch out
you write the request yourself, so keep the Follow Up Boss API documentation open while you set it up.
Follow Up Boss19

Update a Contact

Action

In MakeUpdates a client specified by ID.

Contact details stay current across tools: when something changes elsewhere, the scenario writes it onto the existing record by its ID.

When to use it
a customer edits their details in a form or a billing tool and Follow Up Boss should follow.
Watch out
find the ID with Search Contacts first; updating is safer than creating a second record.
Follow Up Boss20

Update a Deal

Action

In MakeUpdates a deal specified by ID.

Your pipeline moves with events from other tools, since this module changes an existing deal found by its ID.

When to use it
a contract is signed in another tool and the deal should reflect that step.
Watch out
if the same scenario starts on Watch Deal Stage Updated, a stage change here can start it again; add a filter.
Follow Up Boss21

Update an Action Plan for a Contact

Action

In MakeAllows to resume or to pause an action plan for a specific contact.

This module pauses or resumes an action plan already running on a contact, so automated follow-ups stop when a human takes over.

When to use it
a lead books an appointment and the drip sequence should hold while the agent talks to them.
Watch out
it acts on a plan in place; to start a plan, Apply an Action Plan to a Contact is the module you need.
Follow Up Boss22

Update a Note

Action

In MakeUpdates a note specified by ID.

You correct or enrich an existing note by its ID, which keeps one clean note on the contact instead of a trail of versions.

When to use it
a summary note should reflect new information, such as an updated budget from a form.
Watch out
you need the note ID; get it with Search Notes or keep it from the Create a Note step.
Follow Up Boss23

Update a Task

Action

In MakeUpdates a task specified by ID.

Tasks change as the situation does: this module edits an existing task by its ID, so it keeps matching what really happens.

When to use it
an appointment moves and the related follow-up task should follow it.
Watch out
when several tasks come back from Search Tasks, make sure the update targets only the one you mean.
Follow Up Boss24

Search Calls

Search

In MakeSearches for calls.

You get the calls that match your criteria, each returned as its own bundle, ready for a report or a follow-up check.

When to use it
you want to know whether a contact was already called before sending an automatic reminder.
Watch out
a search can return zero, one or many bundles, so plan what the next modules do in each case.
Follow Up Boss25

Search Contacts

Search

In MakeSearches for contacts.

This module finds existing contacts, which is how a scenario avoids duplicates and gets the ID other modules need.

When to use it
before Create a Contact, Update a Contact or Log a Call, to check who is already in the CRM.
Watch out
zero results is normal for a new person; route that case to creation with a filter.
Follow Up Boss26

Search Deals

Search

In MakeSearches for deals.

You retrieve the deals that match a condition, one bundle per deal, to feed a summary or a bulk update.

When to use it
a contact changes and you need every open deal linked to them.
Watch out
every returned deal runs the following modules once, so each result costs operations.
Follow Up Boss27

Search Notes

Search

In MakeSearches for notes.

This module looks up notes and returns each one as a bundle, handy when another tool needs what agents recorded.

When to use it
you want the notes of a contact before building a handoff summary.
Watch out
results come as separate bundles; to merge them into one text, you need an aggregator from Make after it.
Follow Up Boss28

Search Tasks

Search

In MakeSearches for tasks.

You list the tasks that match your criteria, each as a bundle, which lets a scenario review or clean follow-ups in one pass.

When to use it
a deal closes and open tasks for that contact should be updated or removed.
Watch out
check the result count in your Run once test before connecting Delete a Task after it.
Need help

Need help automating Follow Up Boss with Make?

A person reads every message.

FAQ

Follow Up Boss and Make: common questions

01Is the Follow Up Boss Make integration free?
Yes, on the Make side. Follow Up Boss is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations per month. You still need an active Follow Up Boss account with API access.
02What do you need to connect Follow Up Boss to Make?
You need an active Follow Up Boss account with API access and a Make account. In Follow Up Boss, open the Admin menu, go to the API section, click Generate and copy the key. In Make, add a Follow Up Boss module, click Create a connection, give it a name if you like, and paste the key. For an instant module, click Create a webhook before creating the connection. The connection is then reused by every Follow Up Boss module in your scenarios.
03Do Follow Up Boss triggers in Make fire in real time?
Yes. All 7 Follow Up Boss triggers are instant: Follow Up Boss calls Make through a webhook as soon as the event happens, whether it is a new contact, a new deal, a stage change, a new appointment, a tag or a website event. You do not wait for the 15 minute default schedule that applies to scheduled triggers. Each run still counts operations, so a filter right after the trigger keeps busy flows under control.
04What if a Follow Up Boss module is missing in Make?
Use Make an API Call. It calls any endpoint of the Follow Up Boss API with the connection you already have, so it covers what the listed modules do not. You write the request yourself, which means reading the Follow Up Boss API documentation. Keep in mind that Make’s documentation page for this app says its content is AI-generated from the vendor’s docs, so confirm important details with Follow Up Boss before relying on them.
05Should you use Make or n8n for Follow Up Boss?
It depends on the tool your team already uses. In Make, Follow Up Boss comes with 35 modules, including 7 instant triggers and a Make an API Call module, and it runs from the Free plan. The same app often has an n8n node too, so check that the actions you need exist on the side you pick. Neither choice is better by default; compare the modules against your use case before you build.