{"id":54305,"date":"2026-02-01T12:57:25","date_gmt":"2026-02-01T18:57:25","guid":{"rendered":"https:\/\/heartbeat.ai\/healthcare\/make-automation-for-recruiting\/"},"modified":"2026-10-19T14:05:03","modified_gmt":"2026-10-19T19:05:03","slug":"make-automation-for-recruiting","status":"publish","type":"post","link":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/","title":{"rendered":"Make automation for recruiting: 3 branching scenarios (enrichment, dedupe, refresh) with retries + suppression"},"content":{"rendered":"<section class=\"aeo-key-takeaways\">\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_89 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\r\n<div class=\"ez-toc-title-container\">\r\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">What\u2019s on this page:<\/p>\r\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\r\n<nav><ul class='ez-toc-list ez-toc-list-level-1' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Key_takeaways\" >Key takeaways<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Who_this_is_for\" >Who this is for<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Quick_Answer\" >Quick Answer<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Framework_branching_workflows_without_code\" >Framework: branching workflows without code<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Step-by-step_method\" >Step-by-step method<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Step_0_Decide_your_identifiers_and_your_%E2%80%9Cgolden_record%E2%80%9D_rules\" >Step 0: Decide your identifiers and your &#8220;golden record&#8221; rules<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Field_mapping_minimum_viable\" >Field mapping (minimum viable)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Scenario_1_Enrichment_routing_suppression_gate\" >Scenario 1: Enrichment + routing + suppression gate<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Scenario_2_Dedupe_workflow_using_NPIlicense_matching\" >Scenario 2: Dedupe workflow using NPI\/license matching<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Scenario_3_Scheduled_refresh_workflow\" >Scenario 3: Scheduled refresh workflow<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Implementation_notes\" >Implementation notes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Diagnostic_table\" >Diagnostic table<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Weighted_checklist\" >Weighted checklist<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Outreach_templates\" >Outreach templates<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Template_1_Review_task_mediumlow_confidence_match\" >Template 1: Review task (medium\/low confidence match)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Template_2_Suppression_stop_notice\" >Template 2: Suppression stop notice<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Template_3_Recruiter-ready_enrichment_summary_high_confidence\" >Template 3: Recruiter-ready enrichment summary (high confidence)<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Common_pitfalls\" >Common pitfalls<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#How_to_improve_results\" >How to improve results<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Measurement_instructions\" >Measurement instructions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Workflow_upgrades_that_usually_pay_off\" >Workflow upgrades that usually pay off<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Legal_and_ethical_use\" >Legal and ethical use<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Evidence_and_trust_notes\" >Evidence and trust notes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-24\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#FAQs\" >FAQs<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-25\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#What_should_I_automate_first_in_Make_for_recruiting_ops\" >What should I automate first in Make for recruiting ops?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#What_identifiers_work_best_for_dedupe_in_clinician_recruiting\" >What identifiers work best for dedupe in clinician recruiting?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-27\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#How_do_I_prevent_enrichment_from_overwriting_good_ATS_data\" >How do I prevent enrichment from overwriting good ATS data?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-28\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#How_do_I_handle_API_failures_and_rate_limits_in_Make\" >How do I handle API failures and rate limits in Make?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-29\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Where_should_consent_and_opt-out_checks_live_in_the_scenario\" >Where should consent and opt-out checks live in the scenario?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-30\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#Next_steps\" >Next steps<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-31\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#About_the_Author\" >About the Author<\/a><\/li><\/ul><\/nav><\/div>\r\n<h2><span class=\"ez-toc-section\" id=\"Key_takeaways\"><\/span>Key takeaways<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li>The guide outlines three Make scenarios for recruiting: API enrichment, NPI\/license deduplication, and scheduled record refresh.<\/li>\n<li>Check consent and opt-out status before write-backs or any action that could trigger outreach.<\/li>\n<li>Use NPI or license matches for higher-confidence decisions; route ambiguous name-only matches to human review.<\/li>\n<li>Use retries with backoff for transient failures and route unresolved errors to an operations queue.<\/li>\n<li>Track match methods, timestamps, changes, and workflow outcomes to support auditing and troubleshooting.<\/li>\n<\/ul>\n<\/section>\n<p class=\"article-last-updated\"><strong>Last updated:<\/strong> August 31, 2026<\/p>\n<p><img decoding=\"async\" loading=\"false\" class=\"aligncenter\" src=\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/make-automation-for-recruiting-f606adcd.png.webp\" alt=\"54304\" \/><\/p>\n<p><strong>Ben Argeband, Founder &amp; CEO of Heartbeat.ai<\/strong> \u2014 simple, stepwise, no jargon.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Who_this_is_for\"><\/span>Who this is for<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This guide is for recruiting operations teams\u2014or recruiters who also manage operations\u2014who want Make automations with conditional routing, retries, and safeguards for ATS\/CRM records.<\/p>\n<p>It covers three Make scenarios using Heartbeat.ai&#8217;s API for enrichment, deduplication, and scheduled refresh, with consent and opt-out checks included in the workflows.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Quick_Answer\"><\/span>Quick Answer<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<dl>\n<dt>Core Answer<\/dt>\n<dd>Build three Make scenarios: enrich via API, dedupe using NPI\/license matching, and schedule refresh runs with retries and suppression gates.<\/dd>\n<dt>Key Insight<\/dt>\n<dd>Make earns its complexity when you need conditional routing, error handling, and scheduled refresh so recruiters stop working stale or duplicated records.<\/dd>\n<dt>Best For<\/dt>\n<dd>Ops-minded recruiters who want more control than basic linear automations provide.<\/dd>\n<\/dl>\n<blockquote>\n<p><strong>Compliance &amp; Safety<\/strong><\/p>\n<p>This 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<h2><span class=\"ez-toc-section\" id=\"Framework_branching_workflows_without_code\"><\/span>Framework: branching workflows without code<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Recruiting automations can create duplicate records, leave contact fields stale, or overwrite reliable data with weak matches. Use conditional routes to choose an action based on match confidence, and check suppression status before downstream actions.<\/p>\n<p>Use this four-part loop to structure the workflows:<\/p>\n<ul>\n<li><strong>Access<\/strong>: pull the minimum identifiers needed to match the right person.<\/li>\n<li><strong>Refresh<\/strong>: re-check on a schedule so contactability doesn&#8217;t decay.<\/li>\n<li><strong>Verify<\/strong>: only overwrite fields when the match is strong (NPI\/license).<\/li>\n<li><strong>Suppress<\/strong>: enforce consent\/opt-out before any downstream action.<\/li>\n<\/ul>\n<p>The trade-off is more upfront work to define match rules and branches. In return, these safeguards can reduce manual record cleanup and duplicate outreach.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Step-by-step_method\"><\/span>Step-by-step method<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The three scenarios below cover enrichment, deduplication, and scheduled refresh. Each includes branch conditions, retry handling, and suppression checkpoints.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_0_Decide_your_identifiers_and_your_%E2%80%9Cgolden_record%E2%80%9D_rules\"><\/span>Step 0: Decide your identifiers and your &#8220;golden record&#8221; rules<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Primary match keys<\/strong>: NPI and license matching (state + license number) when available.<\/li>\n<li><strong>Fallback match keys<\/strong>: normalized full name + specialty + city\/state, used only when NPI\/license is missing.<\/li>\n<li><strong>Golden record<\/strong>: define which system wins on conflicts \u2014 ATS, CRM, or upload \u2014 and write it down.<\/li>\n<li><strong>Suppression source of truth<\/strong>: decide where consent and opt-out status live, and which field(s) Make checks on every run.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Field_mapping_minimum_viable\"><\/span>Field mapping (minimum viable)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use this minimum field mapping to make the workflow easier to troubleshoot and maintain.<\/p>\n<ul>\n<li><strong>Inputs to the API lookup<\/strong>: send what you have, preferring stable identifiers \u2014 NPI, license state + number, full name, specialty, city\/state.<\/li>\n<li><strong>Outputs to store in ATS\/CRM<\/strong>: match method (NPI, license, name-only), match timestamp, last checked, last verified, and automation outcome (enriched_high_confidence, enriched_review, suppressed, refresh_updated, refresh_no_change, refresh_failed).<\/li>\n<li><strong>Write-back rule<\/strong>: overwrite contact fields only on NPI\/license match; otherwise append and create a review task.<\/li>\n<li><strong>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<h3><span class=\"ez-toc-section\" id=\"Scenario_1_Enrichment_routing_suppression_gate\"><\/span>Scenario 1: Enrichment + routing + suppression gate<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Goal:<\/strong> when a recruiter creates or updates a lead, enrich it via API, then route based on match confidence and compliance status.<\/p>\n<p><strong>Trigger:<\/strong> ATS\/CRM &#8220;new lead&#8221; or &#8220;updated lead&#8221; event, or a Make webhook.<\/p>\n<p><strong>Modules and logic<\/strong><\/p>\n<ol>\n<li><strong>Normalize input<\/strong>: standardize state abbreviations, trim whitespace, split full name if needed.<\/li>\n<li><strong>Suppression gate (hard stop)<\/strong>: if opt-out is true or consent is missing per your policy, route to &#8220;Suppressed&#8221; and stop.<\/li>\n<li><strong>Heartbeat.ai API lookup<\/strong>: search using the best available identifiers, preferring NPI\/license and falling back to name + location.<\/li>\n<li><strong>Router: match confidence<\/strong> \u2014 Branch A (high confidence): NPI or license match with name alignment writes enriched fields back. Branch B (medium confidence): strong name + specialty + geography alignment without NPI\/license writes limited fields and creates a review task. Branch C (low confidence): multiple possible matches or missing key fields creates a review task only, with no overwrite.<\/li>\n<li><strong>Audit log<\/strong>: store match method, timestamp, and which fields were updated.<\/li>\n<\/ol>\n<p><strong>Example router condition:<\/strong> if NPI is present and the match method equals NPI, route to Branch A. If match method equals name-only, route to B or C depending on how many candidates were returned.<\/p>\n<p><strong>Retry logic:<\/strong> on transient API failures (timeouts, 5xx errors), retry with increasing backoff, then route to an ops queue after the final attempt. On &#8220;no match,&#8221; don&#8217;t loop retries immediately \u2014 let Scenario 3 re-check once you&#8217;ve collected better identifiers.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Scenario_2_Dedupe_workflow_using_NPIlicense_matching\"><\/span>Scenario 2: Dedupe workflow using NPI\/license matching<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Goal:<\/strong> prevent duplicate records across ATS\/CRM\/uploads so recruiters don&#8217;t double-contact the same clinician and opt-out rules don&#8217;t get missed.<\/p>\n<p><strong>Trigger:<\/strong> scheduled nightly run and\/or a &#8220;new record created&#8221; event.<\/p>\n<p><strong>Modules and logic<\/strong><\/p>\n<ol>\n<li><strong>Pull candidate set<\/strong>: fetch records created or updated within your chosen window.<\/li>\n<li><strong>Compute dedupe keys<\/strong>: NPI (key 1), license state + number (key 2), normalized full name + city\/state + specialty as fallback (key 3).<\/li>\n<li><strong>Router: dedupe decision<\/strong> \u2014 Branch A: matching NPI across records merges\/links, keeping the most recently verified contact fields. Branch B: matching license merges\/links, treating license fields as authoritative. Branch C: name-only collisions do not auto-merge; a review task links both records.<\/li>\n<li><strong>Write back + audit<\/strong>: update a &#8220;dedupe status&#8221; field and attach a note describing what matched, what changed, and when.<\/li>\n<li><strong>Suppression propagation<\/strong>: if any merged record is opt-out, propagate that status to the surviving record.<\/li>\n<\/ol>\n<p><strong>Retry logic:<\/strong> if a merge fails due to permissions, locked records, or API error, route to a manual merge queue with the dedupe keys and record URLs. Don&#8217;t repeatedly retry locked records \u2014 tag them and notify ops instead.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Scenario_3_Scheduled_refresh_workflow\"><\/span>Scenario 3: Scheduled refresh workflow<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Goal:<\/strong> refresh key fields on a schedule so recruiters aren&#8217;t calling dead numbers or emailing stale addresses.<\/p>\n<p><strong>Trigger:<\/strong> scheduled daily or weekly run, segmented by priority (hot pipeline vs long-term nurture).<\/p>\n<p><strong>Modules and logic<\/strong><\/p>\n<ol>\n<li><strong>Select refresh cohort<\/strong>: records where &#8220;last verified&#8221; exceeds your threshold, excluding opt-outs.<\/li>\n<li><strong>Heartbeat.ai API refresh<\/strong>: request updated contact fields and verification metadata.<\/li>\n<li><strong>Router: change detection<\/strong> \u2014 Branch A: contact fields changed, so update ATS\/CRM and log &#8220;refreshed.&#8221; Branch B: no change, so update &#8220;last checked&#8221; only. Branch C: conflicting identity signals create a review task without overwriting.<\/li>\n<li><strong>Suppression enforcement<\/strong>: re-check consent\/opt-out before any downstream action that could trigger outreach.<\/li>\n<\/ol>\n<p><strong>Retry logic:<\/strong> retry transient failures with backoff; after the final failure, tag the record &#8220;refresh_failed&#8221; and re-queue for the next run. Rate-limit the scenario to avoid bursts that trip vendor limits.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Implementation_notes\"><\/span>Implementation notes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Use these implementation notes as a checklist when building and maintaining the scenarios.<\/p>\n<ul>\n<li><strong>Use a router for branching<\/strong>: route by match confidence (NPI\/license\/name-only) and by suppression status.<\/li>\n<li><strong>Use an error handler for retries<\/strong>: catch API timeouts and 5xx errors, apply increasing delays, then route to an ops queue with the record URL and error summary.<\/li>\n<li><strong>Use scheduling for refresh<\/strong>: run refresh by cohort \u2014 hot vs nurture \u2014 instead of refreshing everything at once.<\/li>\n<li><strong>Set up monitoring and alerts<\/strong>: define what &#8220;failure&#8221; means (refresh_failed, merge_failed, API_error) and route those items to wherever ops actually works. Keep the payload minimal: record URL, error code, scenario step, timestamp.<\/li>\n<li><strong>Keep an audit field<\/strong>: store match method, timestamps, and which fields were updated. Avoid copying sensitive payloads into free-text notes.<\/li>\n<li><strong>Reference<\/strong>: Make&#8217;s official docs cover scheduling and error handling patterns in the <a href=\"https:\/\/www.make.com\/en\/help\">Make help center<\/a>.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Diagnostic_table\"><\/span>Diagnostic table<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<div class=\"table-scroll\" style=\"overflow:auto;-webkit-overflow-scrolling:touch;width:100%\">\n<table class=\"separated-content\">\n<thead>\n<tr>\n<th>Ops problem<\/th>\n<th>What breaks in recruiting<\/th>\n<th>Make pattern to use<\/th>\n<th>Data\/Heartbeat.ai note<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Duplicates across ATS + uploads<\/td>\n<td>Two recruiters work the same clinician; notes split; opt-out missed<\/td>\n<td>Scheduled dedupe with router: NPI \u2192 merge\/link; license \u2192 merge\/link; name-only \u2192 review task<\/td>\n<td>Prefer NPI and license matching; propagate opt-out on merge<\/td>\n<\/tr>\n<tr>\n<td>Enrichment overwrites good fields<\/td>\n<td>Weak match replaces verified phone\/email; recruiters lose trust<\/td>\n<td>Confidence branches: overwrite only on NPI\/license; otherwise append + task<\/td>\n<td>Log match method and timestamp; keep a &#8220;last verified&#8221; field<\/td>\n<\/tr>\n<tr>\n<td>Stale contactability<\/td>\n<td>Bounces, wrong numbers, wasted call blocks<\/td>\n<td>Scheduled refresh cohorts + change-detection branches<\/td>\n<td>Schedule refresh workflows; separate &#8220;last checked&#8221; vs &#8220;last verified&#8221;<\/td>\n<\/tr>\n<tr>\n<td>Silent failures<\/td>\n<td>Scenario fails quietly; recruiters blame the system<\/td>\n<td>Error handler routes: retry with backoff \u2192 ops queue with record link<\/td>\n<td>Store request IDs and error summaries for traceability<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2><span class=\"ez-toc-section\" id=\"Weighted_checklist\"><\/span>Weighted checklist<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Score each item from 0 to 2. A higher score suggests that Make&#8217;s branching and scheduling features may justify the setup effort.<\/p>\n<ul>\n<li><strong>(2)<\/strong> You need branching based on match confidence (NPI\/license vs name-only).<\/li>\n<li><strong>(2)<\/strong> You need scheduled refresh runs, not just event triggers.<\/li>\n<li><strong>(2)<\/strong> You need retries and error routing with audit notes.<\/li>\n<li><strong>(2)<\/strong> You must enforce consent and opt-out before any downstream action.<\/li>\n<li><strong>(1)<\/strong> You need to write back to multiple systems (ATS + CRM + upload).<\/li>\n<li><strong>(1)<\/strong> You need dedupe logic that treats NPI\/license as authoritative.<\/li>\n<li><strong>(1)<\/strong> You can define a golden record rule for conflicts.<\/li>\n<li><strong>(1)<\/strong> You have an ops owner who will maintain fields and mappings.<\/li>\n<\/ul>\n<p><strong>Interpretation<\/strong><\/p>\n<ul>\n<li><strong>0\u20135<\/strong>: Start with Scenario 1 only \u2014 enrichment, suppression, audit.<\/li>\n<li><strong>6\u201310<\/strong>: Add Scenario 2 (dedupe) once your identifiers are consistently captured.<\/li>\n<li><strong>11\u201314<\/strong>: Add Scenario 3 (refresh) and formalize monitoring and alerts.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Outreach_templates\"><\/span>Outreach templates<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Use these short templates for review tasks, suppression stops, and recruiter-ready summaries generated by the automation.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_1_Review_task_mediumlow_confidence_match\"><\/span>Template 1: Review task (medium\/low confidence match)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Title:<\/strong> Verify identity before outreach (missing or conflicting identifiers)<\/p>\n<p><strong>Body:<\/strong> Automation found possible matches but did not overwrite fields. Verify using NPI or license matching if available. If confirmed, mark &#8220;Verified&#8221; and re-run enrichment.<\/p>\n<ul>\n<li>Record link: [ATS\/CRM URL]<\/li>\n<li>Match method attempted: [NPI | license | name-only]<\/li>\n<li>Next identifier to collect: [NPI | license state\/number]<\/li>\n<li>Compliance: confirm consent and check opt-out before outreach<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Template_2_Suppression_stop_notice\"><\/span>Template 2: Suppression stop notice<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Title:<\/strong> Outreach blocked (suppression rule)<\/p>\n<p><strong>Body:<\/strong> This record is suppressed due to opt-out or missing consent per our policy. Do not contact. If you believe this is incorrect, escalate to ops with documentation.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_3_Recruiter-ready_enrichment_summary_high_confidence\"><\/span>Template 3: Recruiter-ready enrichment summary (high confidence)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Title:<\/strong> Enrichment complete (verified identifiers)<\/p>\n<p><strong>Body:<\/strong> Record updated using NPI\/license match. Changes logged. Proceed only if not suppressed.<\/p>\n<ul>\n<li>Verified by: [NPI | license]<\/li>\n<li>Last checked: [timestamp]<\/li>\n<li>Audit note field: [field name]<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Common_pitfalls\"><\/span>Common pitfalls<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li><strong>Overwriting on weak matches<\/strong>: without confidence branching, you&#8217;ll corrupt your ATS. Only overwrite on NPI\/license matches; otherwise append and review.<\/li>\n<li><strong>Suppression checked too late<\/strong>: put opt-out\/consent checks at the top of the scenario and again before any downstream action that could trigger outreach.<\/li>\n<li><strong>No audit trail<\/strong>: if you can&#8217;t answer &#8220;what changed and why,&#8221; ops will lose trust and shut the scenario off.<\/li>\n<li><strong>Retry storms<\/strong>: blind retries can create duplicate updates. Use backoff and route to an ops queue after the final attempt.<\/li>\n<li><strong>One scenario doing everything<\/strong>: separate enrichment, dedupe, and refresh so you can debug and ship changes without breaking the whole pipeline.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"How_to_improve_results\"><\/span>How to improve results<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Evaluate the automation by tracking outcomes at each branch and comparing them with outreach results and recruiter time spent on cleanup.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Measurement_instructions\"><\/span>Measurement instructions<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ol>\n<li><strong>Instrument every branch<\/strong>: write a field like &#8220;automation_outcome&#8221; with values such as enriched_high_confidence, enriched_review, suppressed, refresh_updated, refresh_no_change, refresh_failed.<\/li>\n<li><strong>Track outreach performance separately from automation health<\/strong>: Deliverability Rate (delivered\/sent emails), Bounce Rate (bounced\/sent emails), Connect Rate (connected calls\/total dials), Answer Rate (human answers\/connected calls), Reply Rate (replies\/delivered emails).<\/li>\n<li><strong>Definition \u2014 automation branching<\/strong>: routing a workflow into different paths based on conditions (for example, NPI match vs license match vs name-only), with different actions per path.<\/li>\n<li><strong>Run a controlled comparison<\/strong>: have one team run refresh + dedupe for a set period while another stays manual. Compare bounce\/connect\/reply rates and recruiter time spent on cleanup.<\/li>\n<li><strong>Review the review queue weekly<\/strong>: if too many records land there, tighten match rules or collect NPI\/license earlier in intake.<\/li>\n<\/ol>\n<h3><span class=\"ez-toc-section\" id=\"Workflow_upgrades_that_usually_pay_off\"><\/span>Workflow upgrades that usually pay off<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Identifier-first intake<\/strong>: add NPI\/license fields to intake and make them required when possible.<\/li>\n<li><strong>Segment refresh cadence<\/strong>: hot pipeline refreshes more often than long-term nurture.<\/li>\n<li><strong>Centralize suppression<\/strong>: keep opt-out in one source of truth and have every scenario check it.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Legal_and_ethical_use\"><\/span>Legal and ethical use<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Build consent and opt-out checks into the workflow rather than relying on memory. Consult qualified counsel about requirements that apply in your jurisdictions.<\/p>\n<ul>\n<li><strong>Consent and opt-out<\/strong>: store them in explicit fields and check them before write-back and before any outreach action.<\/li>\n<li><strong>Data minimization<\/strong>: store only what you need for the recruiting workflow; avoid copying sensitive data into free-text notes.<\/li>\n<li><strong>Auditability<\/strong>: log match method, timestamps, and what fields changed.<\/li>\n<li><strong>Human review for ambiguity<\/strong>: route low-confidence matches to a task instead of forcing an automated merge.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Evidence_and_trust_notes\"><\/span>Evidence and trust notes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>For how we think about data quality, verification, and responsible outreach, see our <a href=\"http:\/\/heartbeat.ai\/resources\/resources\/trust-methodology\/\">trust methodology for recruiting data<\/a>.<\/p>\n<p>Make implementation behavior \u2014 scheduling, error handling, modules \u2014 is documented in the <a href=\"https:\/\/www.make.com\/en\/help\">Make help center<\/a>.<\/p>\n<p>If you&#8217;re implementing via Heartbeat.ai, start with the <a href=\"https:\/\/heartbeat.ai\/api\">Heartbeat.ai API documentation<\/a>. Keep suppression rules explicit in your system of record and enforce them in every scenario.<\/p>\n<section class=\"aeo-faq\">\n<h2><span class=\"ez-toc-section\" id=\"FAQs\"><\/span>FAQs<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"What_should_I_automate_first_in_Make_for_recruiting_ops\"><\/span>What should I automate first in Make for recruiting ops?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Start with enrichment + suppression + audit logging (Scenario 1). It gives recruiters cleaner records without risking duplicate merges or noisy refresh runs.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_identifiers_work_best_for_dedupe_in_clinician_recruiting\"><\/span>What identifiers work best for dedupe in clinician recruiting?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use NPI first, then license matching (state + license number). Use name-only matching only as a fallback and route collisions to review.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_prevent_enrichment_from_overwriting_good_ATS_data\"><\/span>How do I prevent enrichment from overwriting good ATS data?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Branch by confidence and only overwrite on NPI\/license matches. For medium confidence, append fields and create a review task. Always log what changed.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_handle_API_failures_and_rate_limits_in_Make\"><\/span>How do I handle API failures and rate limits in Make?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use an error handler with backoff retries for transient failures, then route to an ops queue after the final attempt. Rate-limit scheduled refresh runs by cohort instead of refreshing everything at once.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Where_should_consent_and_opt-out_checks_live_in_the_scenario\"><\/span>Where should consent and opt-out checks live in the scenario?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>At the top of the scenario (hard stop) and again before any downstream action that could trigger outreach. Treat suppression as a shared service so every workflow enforces the same rules.<\/p>\n<\/section>\n<h2><span class=\"ez-toc-section\" id=\"Next_steps\"><\/span>Next steps<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li>If you&#8217;re starting from a spreadsheet, use <a href=\"https:\/\/heartbeat.ai\/upload-file\">upload a file<\/a> to structure inputs before you automate.<\/li>\n<li>For ATS-specific patterns, see <a href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/ats-enrichment-workflows\/\">ATS enrichment workflows<\/a>.<\/li>\n<li>When you&#8217;re ready to wire this into your stack, <a href=\"https:\/\/heartbeat.ai\/signup\">start free search &amp; preview data<\/a> and connect it to your Make scenarios.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"About_the_Author\"><\/span><b>About the Author<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><a href=\"http:\/\/heartbeat.ai\/resources\/author\/ben-argeband\"><span style=\"font-weight: 400;\">Ben Argeband<\/span><\/a><span style=\"font-weight: 400;\"> is the Founder and CEO of Swordfish.ai and Heartbeat.ai. With deep expertise in data and SaaS, he has built two successful platforms trusted by over 50,000 sales and recruitment professionals. Ben&#8217;s mission is to help teams find direct contact information for hard-to-reach professionals and decision-makers, providing the shortest route to their next win. Connect with Ben on <\/span><a href=\"https:\/\/www.linkedin.com\/in\/ben-m-argeband-2427a8a3\/\"><span style=\"font-weight: 400;\">LinkedIn<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><br \/>\n<script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"Article\",\"articleSection\":\"Resources\",\"author\":{\"@type\":\"Person\",\"name\":\"Ben Argeband\"},\"headline\":\"Make automation for recruiting: 3 branching scenarios (enrichment, dedupe, refresh) with retries + suppression\",\"inLanguage\":\"en\",\"keywords\":[\"Make automation for recruiting\",\"Make recruiting automation\",\"Make scenario API\",\"dedupe workflow NPI\"],\"mainEntityOfPage\":{\"@id\":\"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/\",\"@type\":\"WebPage\"},\"publisher\":{\"@type\":\"Organization\",\"name\":\"Heartbeat.ai\"}}<\/script><\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Start with enrichment + suppression + audit logging (Scenario 1). It gives recruiters cleaner records without risking duplicate merges or noisy refresh runs.\"},\"name\":\"What should I automate first in Make for recruiting ops?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Use NPI first, then license matching (state + license number). Use name-only matching only as a fallback and route collisions to review.\"},\"name\":\"What identifiers work best for dedupe in clinician recruiting?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Branch by confidence and only overwrite on NPI\/license matches. For medium confidence, append fields and create a review task. Always log what changed.\"},\"name\":\"How do I prevent enrichment from overwriting good ATS data?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Use an error handler with backoff retries for transient failures, then route to an ops queue after the final attempt. Rate-limit scheduled refresh runs by cohort instead of refreshing everything at once.\"},\"name\":\"How do I handle API failures and rate limits in Make?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"At the top of the scenario (hard stop) and again before any downstream action that could trigger outreach. Treat suppression as a shared service so every workflow enforces the same rules.\"},\"name\":\"Where should consent and opt-out checks live in the scenario?\"}]}<\/script><\/p>","protected":false},"excerpt":{"rendered":"<p>Build three Make scenarios for recruiting: API enrichment, NPI\/license dedupe, and scheduled refresh\u2014with retries and suppression gates.<\/p>","protected":false},"author":5,"featured_media":54304,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_custom_permalink":"integrations-automation\/make-automation-for-recruiting","footnotes":""},"categories":[1],"tags":[],"class_list":["post-54305","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\r\n<title>Make automation for recruiting: 3 branching scenarios + retries<\/title>\r\n<meta name=\"description\" content=\"Make automation for recruiting: copy 3 scenarios\u2014enrichment + routing, dedupe using NPI\/license matching, and scheduled refresh workflows with suppression gates, retries, and measurement.\" \/>\r\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\r\n<link rel=\"canonical\" href=\"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/\" \/>\r\n<meta property=\"og:locale\" content=\"en_US\" \/>\r\n<meta property=\"og:type\" content=\"article\" \/>\r\n<meta property=\"og:title\" content=\"Make automation for recruiting: 3 branching scenarios + retries\" \/>\r\n<meta property=\"og:description\" content=\"Make automation for recruiting: copy 3 scenarios\u2014enrichment + routing, dedupe using NPI\/license matching, and scheduled refresh workflows with suppression gates, retries, and measurement.\" \/>\r\n<meta property=\"og:url\" content=\"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/\" \/>\r\n<meta property=\"og:site_name\" content=\"Heartbeat.ai\" \/>\r\n<meta property=\"article:published_time\" content=\"2026-02-01T18:57:25+00:00\" \/>\r\n<meta property=\"article:modified_time\" content=\"2026-10-19T19:05:03+00:00\" \/>\r\n<meta property=\"og:image\" content=\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/make-automation-for-recruiting-f606adcd.png\" \/>\r\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\r\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\r\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\r\n<meta name=\"author\" content=\"Ben Argeband\" \/>\r\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\r\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ben Argeband\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 minutes\" \/>\r\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/\"},\"author\":{\"name\":\"Ben Argeband\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/person\\\/e9bcffa7dc47cac9f2379e4449e98207\"},\"headline\":\"Make automation for recruiting: 3 branching scenarios (enrichment, dedupe, refresh) with retries + suppression\",\"datePublished\":\"2026-02-01T18:57:25+00:00\",\"dateModified\":\"2026-10-19T19:05:03+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/\"},\"wordCount\":2466,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/make-automation-for-recruiting-f606adcd.png\",\"articleSection\":[\"News\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/\",\"url\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/\",\"name\":\"Make automation for recruiting: 3 branching scenarios + retries\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/make-automation-for-recruiting-f606adcd.png\",\"datePublished\":\"2026-02-01T18:57:25+00:00\",\"dateModified\":\"2026-10-19T19:05:03+00:00\",\"description\":\"Make automation for recruiting: copy 3 scenarios\u2014enrichment + routing, dedupe using NPI\\\/license matching, and scheduled refresh workflows with suppression gates, retries, and measurement.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/#primaryimage\",\"url\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/make-automation-for-recruiting-f606adcd.png\",\"contentUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/make-automation-for-recruiting-f606adcd.png\",\"width\":1024,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/make-automation-for-recruiting\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Make automation for recruiting: 3 branching scenarios (enrichment, dedupe, refresh) with retries + suppression\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#website\",\"url\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/\",\"name\":\"Heartbeat.ai\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\",\"name\":\"Heartbeat.ai\",\"url\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/Heartbeat.ai-logo.png\",\"contentUrl\":\"https:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/Heartbeat.ai-logo.png\",\"width\":704,\"height\":126,\"caption\":\"Heartbeat.ai\"},\"image\":{\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/person\\\/e9bcffa7dc47cac9f2379e4449e98207\",\"name\":\"Ben Argeband\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g\",\"caption\":\"Ben Argeband\"},\"url\":\"https:\\\/\\\/heartbeat.ai\\\/resources\\\/author\\\/ben-argeband\\\/\"}]}<\/script>\r\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Make automation for recruiting: 3 branching scenarios + retries","description":"Make automation for recruiting: copy 3 scenarios\u2014enrichment + routing, dedupe using NPI\/license matching, and scheduled refresh workflows with suppression gates, retries, and measurement.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/","og_locale":"en_US","og_type":"article","og_title":"Make automation for recruiting: 3 branching scenarios + retries","og_description":"Make automation for recruiting: copy 3 scenarios\u2014enrichment + routing, dedupe using NPI\/license matching, and scheduled refresh workflows with suppression gates, retries, and measurement.","og_url":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/","og_site_name":"Heartbeat.ai","article_published_time":"2026-02-01T18:57:25+00:00","article_modified_time":"2026-10-19T19:05:03+00:00","og_image":[{"width":1024,"height":1024,"url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/make-automation-for-recruiting-f606adcd.png","type":"image\/png"}],"author":"Ben Argeband","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ben Argeband","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#article","isPartOf":{"@id":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/"},"author":{"name":"Ben Argeband","@id":"https:\/\/heartbeat.ai\/resources\/#\/schema\/person\/e9bcffa7dc47cac9f2379e4449e98207"},"headline":"Make automation for recruiting: 3 branching scenarios (enrichment, dedupe, refresh) with retries + suppression","datePublished":"2026-02-01T18:57:25+00:00","dateModified":"2026-10-19T19:05:03+00:00","mainEntityOfPage":{"@id":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/"},"wordCount":2466,"commentCount":0,"publisher":{"@id":"https:\/\/heartbeat.ai\/resources\/#organization"},"image":{"@id":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#primaryimage"},"thumbnailUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/make-automation-for-recruiting-f606adcd.png","articleSection":["News"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/","url":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/","name":"Make automation for recruiting: 3 branching scenarios + retries","isPartOf":{"@id":"https:\/\/heartbeat.ai\/resources\/#website"},"primaryImageOfPage":{"@id":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#primaryimage"},"image":{"@id":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#primaryimage"},"thumbnailUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/make-automation-for-recruiting-f606adcd.png","datePublished":"2026-02-01T18:57:25+00:00","dateModified":"2026-10-19T19:05:03+00:00","description":"Make automation for recruiting: copy 3 scenarios\u2014enrichment + routing, dedupe using NPI\/license matching, and scheduled refresh workflows with suppression gates, retries, and measurement.","breadcrumb":{"@id":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#primaryimage","url":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/make-automation-for-recruiting-f606adcd.png","contentUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/make-automation-for-recruiting-f606adcd.png","width":1024,"height":1024},{"@type":"BreadcrumbList","@id":"https:\/\/heartbeat.ai\/resources\/integrations-automation\/make-automation-for-recruiting\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/heartbeat.ai\/resources\/"},{"@type":"ListItem","position":2,"name":"Make automation for recruiting: 3 branching scenarios (enrichment, dedupe, refresh) with retries + suppression"}]},{"@type":"WebSite","@id":"https:\/\/heartbeat.ai\/resources\/#website","url":"https:\/\/heartbeat.ai\/resources\/","name":"Heartbeat.ai","description":"","publisher":{"@id":"https:\/\/heartbeat.ai\/resources\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/heartbeat.ai\/resources\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/heartbeat.ai\/resources\/#organization","name":"Heartbeat.ai","url":"https:\/\/heartbeat.ai\/resources\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/","url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png","contentUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png","width":704,"height":126,"caption":"Heartbeat.ai"},"image":{"@id":"https:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/heartbeat.ai\/resources\/#\/schema\/person\/e9bcffa7dc47cac9f2379e4449e98207","name":"Ben Argeband","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g","caption":"Ben Argeband"},"url":"https:\/\/heartbeat.ai\/resources\/author\/ben-argeband\/"}]}},"permalink_manager":null,"_links":{"self":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54305","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/comments?post=54305"}],"version-history":[{"count":3,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54305\/revisions"}],"predecessor-version":[{"id":66957,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54305\/revisions\/66957"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media\/54304"}],"wp:attachment":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media?parent=54305"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/categories?post=54305"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/tags?post=54305"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}