How to Connect Zapier to Follow Up Boss

Zapier lets you connect Follow Up Boss to hundreds of other apps — Google Sheets, Slack, Gmail, transaction management tools, marketing platforms, and more — without writing any code. This guide walks through every step from generating your API key to verifying that your first Zap is processing real leads correctly.

What you need before you start

• A Follow Up Boss account with admin or owner access (API key generation requires this level)
• A Zapier account (free tier works for two-step Zaps; paid plan required for multi-step Zaps)
• About 15 minutes and a test contact in Follow Up Boss to verify the connection

Step 1: Get your Follow Up Boss API key

1. Log in to Follow Up Boss and click the gear icon or go to Settings in the left navigation.
2. Scroll to the API section (sometimes listed under "Integrations" or "Developer" depending on your account view).
3. Click Create New API Key or copy the existing key if one has already been generated for your account.
4. Label the key clearly — something like "Zapier Integration 2026" — so you can identify it later if you need to revoke it.
5. Copy the key to your clipboard. You will paste it into Zapier in the next step.

Note: The API key authenticates as the account, not as an individual user. Keep it private — anyone with this key can read and write your FUB data.

Step 2: Create a new Zap in Zapier

1. Log in to Zapier and click + Create Zap in the top left.
2. In the trigger search box, type Follow Up Boss and select it from the results. You should see the official Follow Up Boss app with the FUB logo.
3. Click Connect a new account when prompted. Zapier will ask for your Follow Up Boss API key.
4. Paste your API key and click Yes, Continue. Zapier will verify the key against the FUB API and confirm the connection.
5. You will see your account name appear under "My Connections." Select it.

Step 3: Choose your trigger event

Zapier polls Follow Up Boss for new data every few minutes (the interval depends on your Zapier plan tier). The available trigger events for Follow Up Boss are:

• New Contact — fires when a contact is created in FUB
• New Event — fires when a call, text, email, or note is logged on a contact
• New or Updated Contact / Updated Contact — fires when any field on a contact changes
• New Task — fires when a task is created

For your first Zap, New Contact is the easiest to test because you can create a test contact and watch the Zap fire within the poll interval (typically 1–15 minutes depending on your Zapier plan).

Should I use webhooks instead of polling?

If you need true real-time response (seconds, not minutes), use Follow Up Boss's outbound webhook feature to push events to a Zapier "Catch Hook" trigger step instead of relying on Zapier's polling. This is more advanced but delivers much lower latency. See How Event-Driven Integration Works in Follow Up Boss for the full explainer.

Step 4: Pull a sample record

1. After selecting your trigger event, Zapier will ask you to test the trigger by finding recent data. Click Test Trigger.
2. Zapier will pull the most recent matching records from FUB. You should see a list of recent contacts (or events, or tasks, depending on your trigger).
3. Select a record that has all the fields populated that you plan to use in your action step. If the sample is missing a field (it shows as blank or "(no data)"), that field may not reliably be available — plan for the empty case in your action.
4. Click Continue with selected record.

Step 5: Configure the action step

The action is what Zapier does when the trigger fires. Common first Zaps for Follow Up Boss include:

1. Search for the destination app in the action step search box.
2. Authenticate the destination app if this is your first time using it in Zapier.
3. Select the action event (e.g., "Send Channel Message" for Slack, "Create Spreadsheet Row" for Google Sheets).
4. Map the fields from your FUB trigger sample to the action fields. Use the FUB Contact Name, Email, Phone, and any custom fields your Zap needs.
5. Click Test action to confirm the mapping works with real data before going live.

Step 6: Test with a real contact, then turn the Zap on

1. Create a test contact in Follow Up Boss with a recognizable name (e.g., "Zapier Test Contact").
2. Wait for the Zapier poll interval to pass (a few seconds for real-time webhooks; up to 15 minutes for polling Zaps on some plans). The Zap should appear in your Zap History.
3. Inspect the Zap History entry: click on it to see the input payload from FUB and the output sent to your action app.
4. Verify the destination app received the correct data (check the Slack channel, the Google Sheet row, the Dotloop loop, etc.).
5. Delete or archive the test contact in FUB.
6. If everything looks correct, the Zap is already live (it turned on when you completed the setup). If you turned it off for testing, toggle it back on.

How do I add a filter to avoid firing on every contact update?

If you used "Updated Contact" as your trigger and your Zap should only fire for a specific stage change:

1. Between the trigger step and action step, click the + icon to add a step.
2. Choose Filter by Zapier.
3. Set the condition: "Stage" + "Text Exactly Matches" + your stage name (e.g., "Under Contract").
4. Test the filter with a record that matches and one that does not. Confirm the filter passes and blocks correctly.

Common connection errors and fixes

• "Authentication failed" — The API key was not copied correctly. Go back to FUB Settings → API, copy the key again, and reconnect in Zapier.
• "Could not find account" — The key belongs to a different FUB account than the one you are looking at. Confirm you copied from the right FUB account.
• Zap never fires after going live — If using polling, wait the full poll interval. If it still does not fire, create a new contact and watch the Zap History. If there are no entries at all, re-authenticate the FUB connection in Zapier.
• Zap fires but action fails — Inspect the error in Zap History. Common causes: a required field in the action is blank (add a default value), or the destination app token expired (re-authenticate).

What can Follow Up Ace add on top of a Zapier setup?

Follow Up Ace writes its free predictive fields — Ace Win Score and Ace Churn Risk — directly to FUB contact records without consuming Zapier tasks. Once Ace is running, you can build Zapier Zaps that react to those enriched fields — for example, routing high-Win-Score leads to a dedicated high-urgency Slack channel, or logging a Sheets row every time an Ace Win Score crosses a threshold.

This pattern gives you the best of both systems: Ace handles the AI scoring in real time, and Zapier handles the downstream routing to tools outside FUB. The agentic interface adds a conversational layer where you can ask for a pipeline summary or run a lead nurture analysis without building a separate Zap for each query.

Once your first Zap is live, use the Zapier integration checklist to verify every component before relying on it for production leads. For advanced integration patterns, see 5 Zapier Workflows for Follow Up Boss.