Integrations: webhooks, connection keys and your CRM

Integrations

FirstFiveMin works fully with nothing connected. Integrations is where you add what you already use: a CRM, Zapier or Make, your own scripts, or any HTTPS endpoint that wants your events.

Follow Up Boss

Paste your Follow Up Boss API key (created in FUB under Admin → API) and press Connect. The key is stored encrypted and never shown again. Once connected, three toggles push new leads, AI call logs and appointments into FUB; an account-owner key also enables inbound lead sync. Inbound FUB leads appear on your dashboard but are never AI-called: AI calling always requires the lead's own consent captured through FirstFiveMin. Disconnect removes the connection.

Webhooks (events out)

Send signed events to any HTTPS endpoint: type the URL, tick the events you want (new lead, opt-out, call analyzed, appointment confirmed or cancelled, and help struggle), and press Add endpoint. The signing secret is shown once; store it. Each delivery carries an X-STL-Signature header (t=…,v1=…, HMAC-SHA256 of the body) so your side can verify it. Test queues a test delivery; Delete removes the endpoint. Up to 25 endpoints, and each Zap that uses a FirstFiveMin trigger counts as one. An endpoint that keeps failing is disabled with the reason shown.

Times in webhook events are in UTC, for example 2026-09-25T16:00:00Z. Call events also say whether a transfer to you was tried and answered, whether the caller asked for a callback, and whether they asked not to be recorded. Appointment events say whether the booking came from one of our calls, and when the lead gave consent and to which version of the consent wording. They also say where the booking was made: on a call, in the Night Window, or from the waitlist (blank when that is not known, such as for bookings made before it was recorded).

Connections (leads in, or events out)

A connection key lets an automation send leads in (Send leads in) or subscribe to your events (Subscribe to events), never both unless you grant both. Name the connection, tick the permissions, and press Create connection key; copy it now, it is shown only once. Create one key per automation so you can Revoke a single one without breaking the others. The Step-by-step recipes link leads to tested recipes for Zapier, Make, webhooks, n8n, Housecall Pro and Jobber.

If a connection shows "replay protection degraded", your automation is sending an idempotency key that matched a different person. It should send a per-submission id, never a customer or record id.

Consent through integrations

A lead sent in with a complete consent block (where they agreed, the record that proves it, and when) becomes callable. A lead sent in without one is captured and visible but never AI-dialed. Only fill in consent when the person actually agreed and you can produce the record.

Common problems

• "Follow Up Boss rejected that key": create a fresh key in FUB and paste it again.
• "Endpoint limit reached (5)": delete one first.
• A webhook is disabled: the reason is shown next to it; fix the endpoint and add it again.

Lead sources

The Lead sources card shows each way leads reach you (your website form, your lead page and QR code, a signed webhook, Zapier, Make and n8n, Follow Up Boss): when the last lead arrived, how many arrived in the last 7 days, and anything we turned away, with the reason in plain words (for example, a post from a website that is not on your allowed list, or a signature that did not match). Turned-away posts are counted, never silently dropped.

Send a test lead puts a lead marked Test on your dashboard through the same path a real lead takes. A test lead is never called and never texted. We send you a push notification, and a text to your cell if you have verified it in Settings. You can send up to 20 test leads a day.

To test from Zapier, Make or n8n, add "test": true to the data you send; remove it before you go live. If your platform has its own id for each lead, send it as external_lead_id: if the platform delivers the same lead again, even days later, we recognize it and do not create a second lead or a second call.

For Follow Up Boss, if we could not fetch a new lead (Follow Up Boss was unavailable), the card says so and offers Retry now. Follow Up Boss also retries on its own.

Voice health

The Voice health card at the top of Integrations answers, at a glance, whether calls are flowing: when the last call completed, when the last call event arrived from the voice provider, the last error FirstFiveMin recorded for your account (with the time), and how many calls ran in the last seven days (and how many were screened as spam). "Never" on a new account is expected. If the last call event is hours older than your last completed call, or an error keeps appearing, tell your FirstFiveMin operator; nothing on this card is something you need to fix yourself.