<\/span><\/h2>\nYou\u2019re running recruiting ops (or you\u2019re the recruiter who also owns ops). You want automations that can branch, retry, and keep your ATS\/CRM clean without babysitting every run. This is for ops-minded recruiters who want more control than basic linear automations provide.<\/p>\n
Scope: Make scenarios for enrichment, dedupe, and scheduled refresh using Heartbeat.ai<\/strong> via the API<\/strong>, with explicit consent<\/strong> and opt-out<\/strong> gates.<\/p>\n<\/span>Quick Answer<\/span><\/h2>\n\n- Core Answer<\/dt>\n
- Build three Make scenarios: enrich via API, dedupe using NPI\/license matching, and schedule refresh runs with retries and suppression gates.<\/dd>\n
- Key Insight<\/dt>\n
- Make is a good fit when you need conditional routing, error handling, and scheduled refresh so recruiters stop working stale or duplicated records.<\/dd>\n
- Best For<\/dt>\n
- Ops-minded recruiters who want more control than basic linear automations provide.<\/dd>\n<\/dl>\n
\nCompliance & Safety<\/strong><\/p>\nThis method is for legitimate recruiting outreach only. Always respect candidate privacy, opt-out requests, and local data laws. Heartbeat does not provide medical advice or legal counsel.<\/p>\n<\/blockquote>\n
<\/span>Framework: The \u201cPower User\u201d Automation: Branching workflows without code<\/span><\/h2>\nRecruiting automation fails for predictable reasons: duplicates, stale contact fields, and \u201cone-size-fits-all\u201d write-backs that overwrite good data. The fix is routing: different actions for different confidence levels, plus suppression before anything downstream.<\/p>\n
The \u201cPower User\u201d loop:<\/p>\n
\n- Access<\/strong>: pull the minimum identifiers you need to match the right person.<\/li>\n
- Refresh<\/strong>: re-check on a schedule so contactability doesn\u2019t decay.<\/li>\n
- Verify<\/strong>: only overwrite fields when the match is strong (NPI\/license).<\/li>\n
- Suppress<\/strong>: enforce consent\/opt-out before any downstream action.<\/li>\n<\/ul>\n
The trade-off is\u2026 you spend more time designing match rules and branches up front, but you stop paying the hidden tax of recruiter cleanup and duplicate outreach.<\/p>\n
<\/span>Step-by-step method<\/span><\/h2>\nBelow are three Make scenarios (a set of three scenarios) that cover the workflows most recruiting teams actually need: enrichment, dedupe, and refresh. Each includes branch conditions and retry logic, plus where to place suppression checks.<\/p>\n
<\/span>Step 0: Decide your identifiers and your \u201cgolden record\u201d rules<\/span><\/h3>\n\n- Primary match keys<\/strong>: NPI<\/strong> and license matching<\/strong> (state + license number) when available.<\/li>\n
- Fallback match keys<\/strong>: normalized full name + specialty + city\/state (only when NPI\/license is missing).<\/li>\n
- Golden record<\/strong>: define which system wins on conflicts (ATS vs CRM vs upload). Write it down.<\/li>\n
- Suppression source of truth<\/strong>: decide where consent<\/strong> and opt-out<\/strong> live and which field(s) Make must check every time.<\/li>\n<\/ul>\n
<\/span>Field mapping (minimum viable)<\/span><\/h3>\nThis is the simplest mapping that keeps your workflow debuggable and safe.<\/p>\n
\n- Inputs to the API lookup<\/strong> (send what you have, prefer stable identifiers): NPI; license state + license number; full name; specialty; city\/state.<\/li>\n
- Outputs to store in ATS\/CRM<\/strong> (for audit and routing): match method (NPI, license, name-only); match timestamp; last checked; last verified (if you maintain it); automation outcome (enriched_high_confidence, enriched_review, suppressed, refresh_updated, refresh_no_change, refresh_failed).<\/li>\n
- Write-back rule<\/strong>: overwrite contact fields only on NPI\/license match; otherwise append and create a review task.<\/li>\n
- Suppression fields<\/strong>: opt-out boolean and consent status must be readable by Make before any write-back or outreach action.<\/li>\n<\/ul>\n
<\/span>Scenario 1: Enrichment + routing + suppression gate<\/span><\/h3>\nGoal:<\/strong> When a recruiter creates or updates a lead, enrich it via API, then route based on match confidence and compliance.<\/p>\nTrigger<\/strong><\/p>\n\n- ATS\/CRM \u201cNew lead\u201d or \u201cUpdated lead\u201d event, or a Make webhook.<\/li>\n<\/ul>\n
Modules and logic<\/strong><\/p>\n\n- Normalize input<\/strong>: standardize state abbreviations, trim whitespace, split full name if needed.<\/li>\n
- Suppression gate (hard stop)<\/strong>: if opt-out is true or consent is missing per your policy, route to \u201cSuppressed\u201d and stop.<\/li>\n
- Heartbeat.ai API lookup<\/strong>: search using best available identifiers (prefer NPI\/license; fall back to name + location).<\/li>\n
- Router: match confidence<\/strong>\n
\n- Branch A (High confidence)<\/strong>: NPI match OR license match AND name aligns \u2192 write enriched fields back to ATS\/CRM.<\/li>\n
- Branch B (Medium confidence)<\/strong>: no NPI\/license, but strong name + specialty + geography alignment \u2192 write limited fields + create a \u201cReview needed\u201d task.<\/li>\n
- Branch C (Low confidence)<\/strong>: multiple possible matches or missing key fields \u2192 create a review task only; do not overwrite existing data.<\/li>\n<\/ul>\n<\/li>\n
- Audit log<\/strong>: store match method (NPI\/license\/name-only), timestamp, and which fields were updated.<\/li>\n<\/ol>\n
Example Router condition<\/strong>: If NPI is present AND match method equals NPI, route to Branch A. If match method equals name-only, route to Branch B or C depending on how many candidates were returned.<\/p>\nRetry logic<\/strong><\/p>\n\n- On transient API failures (timeouts\/5xx), retry with backoff (increase delay each attempt) and then route to an ops queue after the final attempt.<\/li>\n
- On \u201cno match,\u201d do not loop retries immediately. Instead, let Scenario 3 re-check after you collect better identifiers.<\/li>\n<\/ul>\n
<\/span>Scenario 2: Dedupe workflow using NPI\/license matching<\/span><\/h3>\nGoal:<\/strong> Prevent duplicate records across ATS\/CRM\/uploads so recruiters don\u2019t double-contact the same clinician and your opt-out rules don\u2019t get missed.<\/p>\nTrigger<\/strong><\/p>\n\n- Scheduled run (nightly) and\/or \u201cNew record created\u201d event.<\/li>\n<\/ul>\n
Modules and logic<\/strong><\/p>\n\n- Pull candidate set<\/strong>: fetch records created\/updated in your chosen window.<\/li>\n
- Compute dedupe keys<\/strong>:\n
\n- Key 1: NPI<\/li>\n
- Key 2: license state + license number<\/li>\n
- Key 3 (fallback): normalized full name + city\/state + specialty<\/li>\n<\/ul>\n<\/li>\n
- Router: dedupe decision<\/strong>\n
\n- Branch A<\/strong>: same NPI across multiple records \u2192 merge\/link per your system\u2019s capabilities; keep the most recently verified contact fields.<\/li>\n
- Branch B<\/strong>: same license match across multiple records \u2192 merge\/link; preserve license fields as authoritative.<\/li>\n
- Branch C<\/strong>: name-only collisions \u2192 do not auto-merge; create a review task with both record links.<\/li>\n<\/ul>\n<\/li>\n
- Write back + audit<\/strong>: update a \u201cdedupe status\u201d field and attach an audit note (what matched, what changed, when).<\/li>\n
- Suppression propagation<\/strong>: if any merged record is opt-out, propagate opt-out to the surviving record.<\/li>\n<\/ol>\n
Retry logic<\/strong><\/p>\n\n- If merge\/link fails (permissions, locked record, API error), route to a manual merge queue with the dedupe keys and record URLs.<\/li>\n
- Do not repeatedly retry locked records; tag them and notify ops.<\/li>\n<\/ul>\n
<\/span>Scenario 3: Scheduled refresh workflow (keep contactability current)<\/span><\/h3>\nGoal:<\/strong> Refresh key fields on a schedule so recruiters aren\u2019t calling dead numbers or emailing stale addresses.<\/p>\nTrigger<\/strong><\/p>\n\n- Scheduled run (daily\/weekly) segmented by priority (hot pipeline vs long-term nurture).<\/li>\n<\/ul>\n
Modules and logic<\/strong><\/p>\n\n- Select refresh cohort<\/strong>: records where \u201clast verified\u201d is older than your threshold, excluding opt-outs.<\/li>\n
- Heartbeat.ai API refresh<\/strong>: request updated contact fields and verification metadata.<\/li>\n
- Router: change detection<\/strong>\n
\n- Branch A<\/strong>: contact fields changed \u2192 update ATS\/CRM + log \u201crefreshed.\u201d<\/li>\n
- Branch B<\/strong>: no change \u2192 update \u201clast checked\u201d only.<\/li>\n
- Branch C<\/strong>: conflicting identity signals \u2192 create a review task; do not overwrite.<\/li>\n<\/ul>\n<\/li>\n
- Suppression enforcement<\/strong>: re-check consent\/opt-out before any downstream action that could trigger outreach.<\/li>\n<\/ol>\n
Retry logic<\/strong><\/p>\n\n- Retry transient failures with backoff; after the final failure, tag the record \u201crefresh_failed\u201d and re-queue for the next run.<\/li>\n
- Rate-limit the scenario to avoid bursts that trip vendor limits.<\/li>\n<\/ul>\n
<\/span>Implementation Notes<\/span><\/h2>\nThis section is here so ops can build and maintain the scenarios without guessing.<\/p>\n
\n- Use a Router for branching<\/strong>: route by match confidence (NPI\/license\/name-only) and by suppression status.<\/li>\n
- Use an Error handler for retries<\/strong>: catch API timeouts\/5xx, apply increasing delays, then route to an ops queue with the record URL and error summary.<\/li>\n
- Use scheduling for refresh<\/strong>: run refresh by cohort (hot vs nurture) instead of trying to refresh everything at once.<\/li>\n
- Monitoring & alerts<\/strong>: define what \u201cfailure\u201d means (refresh_failed, merge_failed, API_error) and route those items to the place ops actually works (ticket queue or email). Keep the payload minimal (record URL, error code, scenario step, timestamp).<\/li>\n
- Keep an audit field<\/strong>: store match method, timestamps, and which fields were updated. Avoid copying sensitive payloads into free-text notes.<\/li>\n
- Reference<\/strong>: Make\u2019s official docs cover scheduling and error handling patterns in the Make help center<\/a>.<\/li>\n<\/ul>\n
<\/span>Diagnostic Table:<\/span><\/h2>\n
![\"54304\"](\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/make-automation-for-recruiting-f606adcd.png.webp\")
<\/p>\n