How to Integrate Keap SMS & Chat Automation with Make.com for Recruiting

Email alone is not enough. Candidates read texts within minutes and often ignore recruiting emails for days. This guide shows you exactly how to connect Keap to SMS gateways and chat platforms using Make.com™ — building automated touchpoints that fire at every meaningful pipeline stage without manual recruiter effort. For the foundational pipeline architecture this SMS layer sits on top of, start with the complete guide to Keap and Make.com™ recruiting automation.

Before You Start

This integration assumes a working Keap CRM with defined pipeline stages, at minimum one active tag-based automation, and a Make.com™ account at the Core plan or above (webhooks are required). You will also need an active account with an SMS gateway — Twilio is recommended for its two-way messaging support and native Make.com™ module. Budget 30–60 minutes of setup time per scenario for a first build.

  • Tools required: Keap (any paid tier), Make.com™ (Core or above), SMS gateway account (Twilio or ClickSend), optional: chat platform with outbound webhook support
  • Keap prerequisites: Defined pipeline tags for each candidate stage (e.g., “Application Received,” “Interview Scheduled,” “Offer Extended”), at least one native Keap automation per stage that can fire a webhook
  • Compliance prerequisite: SMS opt-in consent stored as a Keap custom field or tag for every contact before any SMS scenario runs — TCPA compliance is non-negotiable
  • Estimated time: 3–5 hours for a three-scenario basic stack; 8–15 hours for a full multi-channel build
  • Risk: A misconfigured filter step can send SMS messages to unintended contacts — always test on a sandbox contact before activating in production

Step 1 — Map Your Pipeline Events to SMS and Chat Triggers

Before touching Make.com™ or your SMS gateway, document every candidate-facing event in your Keap pipeline that warrants a real-time outreach. These become the trigger points for your scenarios.

Open a spreadsheet and list each pipeline stage in column A. In column B, write the Keap tag that signals entry into that stage. In column C, write the message the candidate should receive — specific, not generic. In column D, note whether the message should be SMS, chat, or both.

A minimal recruiting pipeline typically yields five to eight trigger points worth automating:

  • Application Received → SMS: “Thanks [First Name] — we received your application for [Role]. Expect to hear from us by [Date].”
  • Interview Scheduled → SMS: “Your interview is confirmed for [Date/Time]. Reply YES to confirm or RESCHEDULE to request a new time.”
  • 24-Hour Interview Reminder → SMS: Triggered by a time-delay automation in Keap, not a tag change
  • Application Under Review → SMS or chat follow-up if no engagement after 72 hours
  • Offer Extended → SMS: Personalized congratulatory message with next-step link
  • Application Closed (Not Selected) → SMS: Respectful close with optional talent community invite

Rank these by candidate drop-off risk. Application confirmation and interview reminders have the highest ROI because they directly reduce no-shows and ghosting. Build those first.

Step 2 — Configure Keap Webhooks to Signal Make.com™

Make.com™ cannot poll Keap efficiently at scale. The correct architecture uses Keap’s native automation builder to fire an outbound webhook the moment a pipeline event occurs. For a deeper walkthrough of this trigger pattern, see the guide on Keap webhook triggers with Make.com™.

  1. In Make.com™, create a new scenario. Add a Webhooks → Custom Webhook module as the trigger. Copy the generated webhook URL.
  2. In Keap, open Automation → Campaign Builder. Create or edit the automation for your first trigger event (e.g., tag “Interview Scheduled” applied).
  3. Add a Send HTTP Post action to the automation sequence. Paste the Make.com™ webhook URL into the endpoint field.
  4. Map the Keap merge fields you need in the SMS — at minimum: Contact ID, First Name, Email, Phone, and any stage-specific fields like Interview Date/Time. Send these as JSON in the POST body.
  5. Save and activate the Keap automation. Back in Make.com™, run the webhook module and apply the tag to a test contact in Keap to capture a sample payload. Make.com™ will auto-map the incoming fields.

Repeat this process for each pipeline trigger you mapped in Step 1. You will end up with one webhook URL per scenario — do not share webhook endpoints across multiple scenario types, as mixing payloads creates mapping errors that are hard to debug.

Step 3 — Build the SMS Sending Scenario in Make.com™

With the webhook trigger live and payload captured, build the rest of the scenario. The structure is: Webhook → Opt-In Check → Router → SMS Send → Tag Update → Error Handler.

  1. Add a Keap “Get a Contact” module after the webhook trigger, using the Contact ID from the webhook payload. This pulls the full, current contact record including custom fields and tags — do not rely solely on the webhook payload data, which reflects the state at fire time.
  2. Add a Router module. The first route checks the SMS opt-in field: if the opt-in flag is false or empty, route to a “Log No SMS — No Consent” path that updates a Keap note and stops. Never proceed past this check without confirmed consent.
  3. On the opted-in route, add a Twilio “Send an SMS” module (or your gateway’s equivalent). Map the recipient phone number from the Keap contact record. Build the message body using the mapped fields from the webhook payload — First Name, Role, Date/Time — to produce a genuinely personalized message, not a generic blast.
  4. Add a Keap “Apply Tag” module after the SMS send step. Apply a tag like “SMS Sent — Interview Reminder” to the contact. This tag acts as a state flag that prevents duplicate sends if the scenario runs again for the same contact.
  5. Add a Keap “Create a Note” module to log the SMS content and timestamp on the contact record. This preserves the full communication history in Keap regardless of what happens in external platforms.
  6. Add an error handler to the SMS module. If the gateway returns a failure (invalid number, carrier block), route to a Keap note update flagging the contact for manual recruiter review.

Save, then run a full test using a real phone number you control before activating the scenario.

Step 4 — Enable Two-Way SMS: Route Inbound Replies Back to Keap

One-way SMS is useful. Two-way SMS is transformative. When a candidate replies “RESCHEDULE” to an interview reminder, that signal must update Keap and notify the recruiter immediately — not sit in a gateway inbox until someone checks it.

  1. In your SMS gateway (e.g., Twilio), configure the inbound message webhook to point to a new Make.com™ scenario. This is a separate scenario from your outbound sends.
  2. In Make.com™, create a new scenario with a Webhooks → Custom Webhook trigger. Configure Twilio’s messaging webhook URL to send inbound messages here.
  3. Add a Keap “Search Contacts” module. Search by the sender’s phone number from the Twilio payload. This matches the inbound reply to the correct candidate record.
  4. Add a Router module branching on the reply content:
    • “YES” or “CONFIRM” → Apply “Interview Confirmed” tag in Keap, send a confirmation SMS back to the candidate, notify the recruiter via their preferred channel.
    • “RESCHEDULE” → Apply “Reschedule Requested” tag, pause the interview confirmation sequence in Keap (remove from active automation), send a reply SMS with reschedule link, alert the recruiter immediately.
    • Any other reply → Log the full message as a Keap note, apply an “Unrecognized Reply — Review” tag, and alert the recruiter to follow up manually.
  5. Log every inbound message as a Keap note with the message body, timestamp, and phone number — even if the reply is unrecognized. The recruiter should never be in the dark about a candidate-initiated conversation.

This pattern — described in more detail in the section on automated interview scheduling with Keap and Make.com™ — is where two-way SMS pays for itself. A single prevented no-show recovers more time than the hours spent building the scenario.

Step 5 — Ingest Chat Platform Data into Keap via Make.com™

If you use a website chatbot or social messaging channel for initial candidate intake, those conversations must write back into Keap to keep your pipeline authoritative. A candidate who starts a conversation in a chat widget but never receives an email follow-up because Keap doesn’t know they exist represents a leak in the pipeline.

  1. In your chat platform, locate the outbound webhook or integration event settings. Most platforms fire a webhook on conversation completion or when a lead form inside the chat is submitted. Configure this to send to a new Make.com™ scenario webhook URL.
  2. In Make.com™, map the incoming payload fields — name, email, phone, message summary, job interest — to Keap contact fields. Use a Keap “Create or Update a Contact” module so existing contacts are updated rather than duplicated.
  3. Apply an appropriate pipeline tag to the contact — “Chat Lead — Careers Page” or similar — so Keap’s native automation can immediately enroll them in the correct follow-up sequence.
  4. Add a Keap note logging the chat transcript summary and timestamp. If your chat platform provides a conversation ID, log that too for cross-reference.
  5. Optionally, trigger an immediate SMS confirmation from within the same Make.com™ scenario (if the candidate provided a phone number and opt-in consent was captured in the chat flow): “Hi [First Name] — thanks for reaching out about [Role]. A recruiter will follow up within one business day.”

For guidance on keeping all Keap fields accurate as data flows in from multiple sources, see the how-to on automating Keap tags and custom fields with Make.com™.

Step 6 — Add Deduplication and State Flag Logic

Multi-channel automation creates a new failure mode: sending the same message twice to the same candidate via two different triggers. Prevent this with explicit state flags at the Make.com™ scenario level and at the Keap tag level.

  • Before every SMS send step, check for the presence of the “already sent” tag for that stage (e.g., “SMS Sent — Application Confirmed”). If the tag exists, route to a no-op branch and exit the scenario without sending.
  • Apply the state flag tag immediately after a confirmed send, not at the end of the scenario — if a later module errors, the tag is already set and protects against a retry loop resending the SMS.
  • Use Keap’s duplicate contact detection settings to prevent the same candidate from entering the pipeline twice under different email addresses. Duplicate contacts mean two separate SMS sends to the same person — a fast way to opt them out permanently.
  • Set scenario run frequency in Make.com™ to match the pace of your pipeline — high-volume agencies may need near-real-time (1–5 minute polling or instant webhooks); lower-volume teams can run hourly without meaningful impact on candidate experience.

For a complete rundown of the most common errors in this type of integration and how to resolve them before they reach production, see troubleshooting Make.com™ and Keap integration errors.

How to Know It Worked

Run a structured post-activation check over the first 48–72 hours of live operation:

  • Keap contact records for any candidate who moved through a tagged pipeline stage should show: the SMS Sent tag applied, a note with the message body and timestamp, and — for two-way scenarios — any inbound reply logged as a subsequent note.
  • Make.com™ scenario run history should show 100% successful executions or, for failures, clear error messages pointing to the specific module and field that failed. Any scenario with a >2% error rate needs investigation before scaling.
  • SMS gateway dashboard should confirm delivery status for every outbound message. Undelivered messages (carrier blocks, invalid numbers) must route to a Keap flag, not disappear silently.
  • Recruiter feedback after two weeks: the most meaningful signal is whether recruiters are still manually chasing confirmations or whether candidates are arriving at interviews prepared, confirmed, and on time. A measurable drop in no-show rate and fewer manual follow-up tasks per recruiter are the real KPIs.

McKinsey Global Institute research finds that workers spend an average of 28% of the workweek on email and communication management. Shifting confirmations, reminders, and status updates to automated SMS and chat sequences pulls recruiting bandwidth back toward higher-value candidate conversations — the work Asana’s Anatomy of Work research consistently identifies as the activity workers find most meaningful and most frequently crowded out by coordination overhead.

Common Mistakes and How to Avoid Them

Skipping the opt-in check

The most damaging error is sending SMS to contacts without confirmed opt-in consent. Build the Router check in Step 3 before any other logic. A single TCPA complaint outweighs every efficiency gain from the automation.

Using webhook payload data instead of a fresh Keap pull

Webhook payloads capture the contact’s state at the moment the event fires. If another automation applied a tag or updated a field a second earlier, the payload may be stale. Always use “Get a Contact” to pull the live record before making decisions or sending messages.

Building all scenarios into one Make.com™ scenario

A single monolithic scenario handling every pipeline stage becomes impossible to debug. One scenario per trigger event, clearly named (“Keap → SMS: Interview Reminder 24hr”), is far easier to isolate when something breaks.

Not logging outbound SMS in Keap

If the only record of a candidate conversation lives in a third-party SMS gateway, a recruiter without gateway access has no visibility. Every outbound and inbound SMS must appear as a Keap note. This is not optional for teams with multiple recruiters. For more on keeping candidate data in sync, see personalizing the candidate experience with Keap automation.

Sending SMS at email-cadence frequency

Email sequences can run daily without friction. SMS at that frequency will generate opt-outs fast. Limit SMS to genuine pipeline events — confirmation, reminder, status update — and use email for nurture content between stages. Gartner research on communication channel fatigue consistently shows that over-messaging on high-attention channels degrades response rates rather than improving them.

Next Steps: Build the Full Multi-Channel Recruiting Stack

SMS and chat automation is one layer of a complete recruiting pipeline. The scenarios built in this guide become significantly more powerful when they sit on top of structured interview scheduling, pre-screening qualification sequences, and data-driven pipeline reporting. Explore how to extend this foundation:

The goal is not to automate for automation’s sake. It is to ensure every candidate receives a fast, personal, consistent response at every pipeline stage — without that consistency depending on a recruiter manually remembering to send a message. SMS and chat, triggered by Keap events and orchestrated by Make.com™, deliver exactly that.