{"id":54303,"date":"2026-02-01T12:57:06","date_gmt":"2026-02-01T18:57:06","guid":{"rendered":"https:\/\/heartbeat.ai\/healthcare\/zapier-for-healthcare-recruiters\/"},"modified":"2026-02-27T13:34:17","modified_gmt":"2026-02-27T19:34:17","slug":"zapier-for-healthcare-recruiters","status":"publish","type":"post","link":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/","title":{"rendered":"Zapier for healthcare recruiters: 5 recipes + governance, failure handling, and metrics"},"content":{"rendered":"<p><img decoding=\"async\" loading=\"false\" class=\"aligncenter\" src=\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/zapier-for-healthcare-recruiters-1e039507.png.webp\" alt=\"54302\" \/><\/p>\n<h1>Zapier for healthcare recruiters<\/h1>\n<p><strong>Ben Argeband, Founder &amp; CEO of Heartbeat.ai<\/strong> \u2014 Extremely simple.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 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\/zapier-for-healthcare-recruiters\/#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-2\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#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-3\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Framework_The_%E2%80%9CSet_It_and_Forget_It%E2%80%9D_Recipes_Build_once_save_hours\" >Framework: The \u201cSet It and Forget It\u201d Recipes: Build once, save hours<\/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\/zapier-for-healthcare-recruiters\/#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-5\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Step_1_Define_your_system_of_record_so_you_dont_create_duplicates\" >Step 1: Define your system of record (so you don\u2019t create duplicates)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Step_2_Standardize_a_minimal_field_map_so_your_recipes_are_reusable\" >Step 2: Standardize a minimal field map (so your recipes are reusable)<\/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\/zapier-for-healthcare-recruiters\/#Step_3_Choose_how_Zapier_will_talk_to_Heartbeatai\" >Step 3: Choose how Zapier will talk to Heartbeat.ai<\/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\/zapier-for-healthcare-recruiters\/#Common_Zapier_steps_youll_use_for_faster_build_easier_troubleshooting\" >Common Zapier steps you\u2019ll use (for faster build + easier troubleshooting)<\/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\/zapier-for-healthcare-recruiters\/#Step_4_Build_the_RECIPE_PACK_5_named_recipes_with_plain-English_setup\" >Step 4: Build the RECIPE_PACK (5 named recipes with plain-English setup)<\/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\/zapier-for-healthcare-recruiters\/#Recipe_1_%E2%80%9CUpload_%E2%86%92_Enrich_%E2%86%92_Push_to_ATSCRM%E2%80%9D_the_intake_conveyor\" >Recipe 1: \u201cUpload \u2192 Enrich \u2192 Push to ATS\/CRM\u201d (the intake conveyor)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Recipe_2_%E2%80%9CNew_Lead_Form_%E2%86%92_Instant_Enrich_%E2%86%92_Assign_Owner%E2%80%9D_speed-to-first-touch\" >Recipe 2: \u201cNew Lead Form \u2192 Instant Enrich \u2192 Assign Owner\u201d (speed-to-first-touch)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Recipe_3_%E2%80%9CStage_Change_%E2%86%92_Refresh_Contact_Data%E2%80%9D_trigger-based_refresh\" >Recipe 3: \u201cStage Change \u2192 Refresh Contact Data\u201d (trigger-based refresh)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Recipe_4_%E2%80%9COpt-out_Anywhere_%E2%86%92_Suppress_Everywhere%E2%80%9D_compliance-first_suppression\" >Recipe 4: \u201cOpt-out Anywhere \u2192 Suppress Everywhere\u201d (compliance-first suppression)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Recipe_5_%E2%80%9CDaily_Hot_List_Digest%E2%80%9D_ops_visibility_without_meetings\" >Recipe 5: \u201cDaily Hot List Digest\u201d (ops visibility without meetings)<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Implementation_Notes\" >Implementation Notes<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Governance_who_owns_the_Zaps_how_changes_happen\" >Governance (who owns the Zaps, how changes happen)<\/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\/zapier-for-healthcare-recruiters\/#Failure_handling_required\" >Failure handling (required)<\/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\/zapier-for-healthcare-recruiters\/#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-19\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#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-20\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#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-21\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Template_1_Recruiter-to-Ops_request_build_the_right_Zap\" >Template 1: Recruiter-to-Ops request (build the right Zap)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Template_2_Candidate_note_for_ATSCRM_audit_trail\" >Template 2: Candidate note for ATS\/CRM (audit trail)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Template_3_Internal_Slack_digest_daily_hot_list\" >Template 3: Internal Slack digest (daily hot list)<\/a><\/li><\/ul><\/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\/zapier-for-healthcare-recruiters\/#Common_pitfalls\" >Common pitfalls<\/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\/zapier-for-healthcare-recruiters\/#1_Automating_before_you_define_an_automation_workflow\" >1) Automating before you define an automation workflow<\/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\/zapier-for-healthcare-recruiters\/#2_Treating_enrichment_as_a_one-time_event\" >2) Treating enrichment as a one-time event<\/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\/zapier-for-healthcare-recruiters\/#3_Not_centralizing_opt-out\" >3) Not centralizing opt-out<\/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\/zapier-for-healthcare-recruiters\/#4_Over-notifying_recruiters\" >4) Over-notifying recruiters<\/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\/zapier-for-healthcare-recruiters\/#5_RECIPE_PACK_mini-case_field_drift_breaks_stable_automations\" >5) RECIPE_PACK mini-case: field drift breaks stable automations<\/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\/zapier-for-healthcare-recruiters\/#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-31\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Measurement_instructions_required\" >Measurement instructions (required)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-32\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Week_1_validation_checklist_no_dashboards_required\" >Week 1 validation checklist (no dashboards required)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-33\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#What_to_track_definitions_included\" >What to track (definitions included)<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-34\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#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-35\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#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-36\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#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-37\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Do_I_need_engineering_to_use_Zapier_for_healthcare_recruiters\" >Do I need engineering to use Zapier for healthcare recruiters?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-38\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Whats_the_safest_first_automation_to_build\" >What\u2019s the safest first automation to build?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-39\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#How_do_I_prevent_duplicates_when_pushing_enriched_candidates_into_my_ATSCRM\" >How do I prevent duplicates when pushing enriched candidates into my ATS\/CRM?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-40\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Can_I_route_candidates_by_specialty_or_state_automatically\" >Can I route candidates by specialty or state automatically?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-41\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#Where_should_I_store_consent_and_opt-out\" >Where should I store consent and opt-out?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-42\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#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-43\" href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#About_the_Author\" >About the Author<\/a><\/li><\/ul><\/nav><\/div>\r\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>Recruiters and ops teams wanting fast automations without engineering\u2014especially if you\u2019re juggling an ATS\/CRM, spreadsheets, and compliance steps like <strong>consent<\/strong> and <strong>opt-out<\/strong> tracking.<\/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>Use Zapier to automate intake, enrichment, refresh, and suppression so candidate records stay current and opt-outs are enforced across your ATS\/CRM and outreach tools.<\/dd>\n<dt>Key Insight<\/dt>\n<dd>Trigger-based refresh reduces decay: re-check contact data when a record hits a re-engage stage, then write updates back to the same ATS\/CRM record.<\/dd>\n<dt>Best For<\/dt>\n<dd>Recruiters and ops teams wanting fast automations without engineering.<\/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<p><strong>TL;DR recipe index<\/strong><\/p>\n<ul>\n<li><strong>Recipe 1:<\/strong> Upload \u2192 Enrich \u2192 Push to ATS\/CRM (turn lists into recruiter-ready records)<\/li>\n<li><strong>Recipe 2:<\/strong> New Lead Form \u2192 Instant Enrich \u2192 Assign Owner (speed-to-first-touch)<\/li>\n<li><strong>Recipe 3:<\/strong> Stage Change \u2192 Refresh Contact Data (reduce decay when it matters)<\/li>\n<li><strong>Recipe 4:<\/strong> Opt-out Anywhere \u2192 Suppress Everywhere (centralize suppression)<\/li>\n<li><strong>Recipe 5:<\/strong> Daily Hot List Digest (ops visibility without meetings)<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Framework_The_%E2%80%9CSet_It_and_Forget_It%E2%80%9D_Recipes_Build_once_save_hours\"><\/span>Framework: The \u201cSet It and Forget It\u201d Recipes: Build once, save hours<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>In healthcare recruiting, speed comes from removing repeat admin work while keeping compliance tight. The framework is:<\/p>\n<ul>\n<li><strong>One trigger<\/strong> (new row, form submission, stage change).<\/li>\n<li><strong>One enrichment step<\/strong> (Heartbeat.ai via Zapier Webhooks or the <a href=\"https:\/\/heartbeat.ai\/api\">API<\/a>).<\/li>\n<li><strong>One write-back<\/strong> (update the ATS\/CRM record so recruiters work from one place).<\/li>\n<li><strong>One safety net<\/strong> (failure handling + suppression so opt-outs don\u2019t get re-contacted).<\/li>\n<\/ul>\n<p>The trade-off is\u2026 you\u2019ll spend upfront time deciding where each field is mastered (ATS\/CRM vs spreadsheet) and standardizing names so Zaps don\u2019t drift.<\/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<h3><span class=\"ez-toc-section\" id=\"Step_1_Define_your_system_of_record_so_you_dont_create_duplicates\"><\/span>Step 1: Define your system of record (so you don\u2019t create duplicates)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Before you build Zaps, decide where each item is stored long-term:<\/p>\n<ul>\n<li><strong>Candidate identity:<\/strong> name, specialty, state(s), email, mobile phone.<\/li>\n<li><strong>Workflow:<\/strong> stage, owner, next task.<\/li>\n<li><strong>Compliance:<\/strong> consent status (where required by your policy and local law), opt-out status, timestamp, channel.<\/li>\n<\/ul>\n<p>Most teams use the ATS\/CRM as the system of record and treat spreadsheets as intake queues only.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Standardize_a_minimal_field_map_so_your_recipes_are_reusable\"><\/span>Step 2: Standardize a minimal field map (so your recipes are reusable)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Create these fields (or equivalents) in your ATS\/CRM and keep naming consistent across tools:<\/p>\n<ul>\n<li><strong>Full Name<\/strong><\/li>\n<li><strong>Specialty<\/strong><\/li>\n<li><strong>State(s)<\/strong><\/li>\n<li><strong>Email<\/strong> (and optionally Email 2)<\/li>\n<li><strong>Mobile Phone<\/strong> (and optionally Phone 2)<\/li>\n<li><strong>Source<\/strong> (referral, event, upload, etc.)<\/li>\n<li><strong>Opt-out<\/strong> (true\/false) + <strong>Opt-out timestamp<\/strong> + <strong>Opt-out channel<\/strong><\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Choose_how_Zapier_will_talk_to_Heartbeatai\"><\/span>Step 3: Choose how Zapier will talk to Heartbeat.ai<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Common options:<\/p>\n<ul>\n<li><strong>Webhooks by Zapier:<\/strong> flexible and usually the fastest path for ops teams.<\/li>\n<li><strong>Direct app action:<\/strong> easiest to maintain if available in your Zapier account.<\/li>\n<li><strong>Code step:<\/strong> only if you need custom transforms; most recruiting teams can avoid it.<\/li>\n<\/ul>\n<p>If you\u2019re starting from a file, the simplest on-ramp is file intake via <a href=\"https:\/\/heartbeat.ai\/upload-file\">Upload File<\/a>, then push enriched fields into your ATS\/CRM.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Common_Zapier_steps_youll_use_for_faster_build_easier_troubleshooting\"><\/span>Common Zapier steps you\u2019ll use (for faster build + easier troubleshooting)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Trigger:<\/strong> the event that starts the workflow (new row, new form submission, stage change).<\/li>\n<li><strong>Filter:<\/strong> stop the Zap unless conditions are met (for example, Opt-out is not true).<\/li>\n<li><strong>Paths:<\/strong> route records based on specialty\/state\/source.<\/li>\n<li><strong>Webhooks:<\/strong> send data to Heartbeat.ai endpoints and receive results.<\/li>\n<li><strong>Delay:<\/strong> wait for async processing or schedule a follow-up check.<\/li>\n<li><strong>Create\/Update:<\/strong> write enriched fields back to the ATS\/CRM record.<\/li>\n<li><strong>Error logging:<\/strong> write failures to a log table and alert ops.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_Build_the_RECIPE_PACK_5_named_recipes_with_plain-English_setup\"><\/span>Step 4: Build the RECIPE_PACK (5 named recipes with plain-English setup)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>These five recipes are designed to reduce admin time, keep records current, and enforce opt-outs. Build one, stabilize it, then copy the pattern.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Recipe_1_%E2%80%9CUpload_%E2%86%92_Enrich_%E2%86%92_Push_to_ATSCRM%E2%80%9D_the_intake_conveyor\"><\/span>Recipe 1: \u201cUpload \u2192 Enrich \u2192 Push to ATS\/CRM\u201d (the intake conveyor)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Use when:<\/strong> you receive candidate lists (events, referrals, internal sheets) and want them cleaned\/enriched before recruiters touch them.<\/p>\n<ul>\n<li><strong>Trigger:<\/strong> New file added to a folder (Google Drive\/Dropbox) OR new rows in a Google Sheet.<\/li>\n<li><strong>Action 1:<\/strong> Send the file\/rows to Heartbeat.ai (use <a href=\"https:\/\/heartbeat.ai\/upload-file\">Upload File<\/a> or a webhook to the <a href=\"https:\/\/heartbeat.ai\/api\">API<\/a>).<\/li>\n<li><strong>Action 2:<\/strong> Wait\/poll for completion (Zapier Delay + a follow-up step, or a scheduled Zap that checks status).<\/li>\n<li><strong>Action 3:<\/strong> Create or update the candidate in your ATS\/CRM with enriched fields.<\/li>\n<li><strong>Action 4:<\/strong> Notify the recruiter: \u201cEnriched candidates ready\u201d + link to the ATS\/CRM filtered view.<\/li>\n<\/ul>\n<p><strong>Plain-English setup tip:<\/strong> Start with 5\u201310 rows as a test batch. Confirm the write-back fields in your ATS\/CRM are correct before you run the full file.<\/p>\n<p><strong>ATS\/CRM adaptation note:<\/strong> If you use Bullhorn or Apploi, the pattern is the same: map enriched email\/phone into the candidate\/applicant record, then assign owner and stage. Keep the mapping doc in your ops folder so future edits don\u2019t break the Zap.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Recipe_2_%E2%80%9CNew_Lead_Form_%E2%86%92_Instant_Enrich_%E2%86%92_Assign_Owner%E2%80%9D_speed-to-first-touch\"><\/span>Recipe 2: \u201cNew Lead Form \u2192 Instant Enrich \u2192 Assign Owner\u201d (speed-to-first-touch)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Use when:<\/strong> inbound leads come from a landing page, referral form, or event QR code and you want a recruiter to call fast.<\/p>\n<ul>\n<li><strong>Trigger:<\/strong> New form submission (Typeform\/Google Forms\/Webflow).<\/li>\n<li><strong>Action 1:<\/strong> Create a candidate record in your ATS\/CRM with the raw submission.<\/li>\n<li><strong>Action 2:<\/strong> Enrich via Heartbeat.ai (webhook\/API) and update the same record.<\/li>\n<li><strong>Action 3:<\/strong> Assign owner based on specialty\/state (Zapier Paths).<\/li>\n<li><strong>Action 4:<\/strong> Create a task: \u201cCall during local business hours\u201d and include the best phone field.<\/li>\n<\/ul>\n<p><strong>Ops note:<\/strong> If you create call tasks outside clinic hours, your downstream call performance will drop. Route tasks into a queue that respects local time windows.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Recipe_3_%E2%80%9CStage_Change_%E2%86%92_Refresh_Contact_Data%E2%80%9D_trigger-based_refresh\"><\/span>Recipe 3: \u201cStage Change \u2192 Refresh Contact Data\u201d (trigger-based refresh)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Use when:<\/strong> candidates sit in pipeline stages for weeks and contact info decays.<\/p>\n<ul>\n<li><strong>Trigger:<\/strong> Candidate moved to a stage like \u201cRe-engage,\u201d \u201cCredentialing,\u201d or \u201cOffer Pending.\u201d<\/li>\n<li><strong>Action 1:<\/strong> Request a refresh from Heartbeat.ai.<\/li>\n<li><strong>Action 2:<\/strong> Update ATS\/CRM fields and write a note: \u201cRefreshed on {date} via Zap.\u201d<\/li>\n<li><strong>Action 3:<\/strong> If key fields changed, notify the owner: \u201cContact updated\u2014use latest phone\/email.\u201d<\/li>\n<\/ul>\n<p><strong>Why this matters:<\/strong> You stop burning dials and bounces on stale data, and recruiters stop working from outdated records.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Recipe_4_%E2%80%9COpt-out_Anywhere_%E2%86%92_Suppress_Everywhere%E2%80%9D_compliance-first_suppression\"><\/span>Recipe 4: \u201cOpt-out Anywhere \u2192 Suppress Everywhere\u201d (compliance-first suppression)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Use when:<\/strong> opt-outs arrive via email replies, SMS keywords, call notes, or a web form\u2014and you need one source of truth.<\/p>\n<ul>\n<li><strong>Trigger:<\/strong> New opt-out tag applied in ATS\/CRM OR a new row in an opt-out sheet OR a form submission.<\/li>\n<li><strong>Action 1:<\/strong> Update ATS\/CRM fields: Opt-out=true, timestamp, channel, and optional reason.<\/li>\n<li><strong>Action 2:<\/strong> Add to suppression list(s) in your outreach tools (email\/SMS) if connected; otherwise log suppression in the ATS\/CRM and enforce it there.<\/li>\n<li><strong>Action 3:<\/strong> Notify ops (not recruiters) so the team can audit patterns and sources.<\/li>\n<\/ul>\n<p><strong>Non-negotiable:<\/strong> Log opt-out status in ATS. That\u2019s how you prevent re-contact when lists get re-uploaded, merged, or reassigned.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Recipe_5_%E2%80%9CDaily_Hot_List_Digest%E2%80%9D_ops_visibility_without_meetings\"><\/span>Recipe 5: \u201cDaily Hot List Digest\u201d (ops visibility without meetings)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Use when:<\/strong> you want a daily pulse on what\u2019s moving without pulling reports manually.<\/p>\n<ul>\n<li><strong>Trigger:<\/strong> Schedule (every weekday at a consistent time in your team\u2019s primary time zone).<\/li>\n<li><strong>Action 1:<\/strong> Search ATS\/CRM for candidates added\/updated in the last day, grouped by specialty and owner.<\/li>\n<li><strong>Action 2:<\/strong> Post a digest to Slack\/Email: new candidates, refreshed contacts, opt-outs logged, and any Zap failures.<\/li>\n<\/ul>\n<p><strong>Plain-English setup tip:<\/strong> Keep the digest to counts + links to filtered views. Don\u2019t paste candidate personal data into chat tools.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Implementation_Notes\"><\/span>Implementation Notes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>These are the operational details that keep Zapier automations stable in recruiting ops:<\/p>\n<ul>\n<li><strong>Auth and permissions:<\/strong> if a Zap starts failing after weeks, check whether the connected account token expired or permissions changed. Zapier documents connection and troubleshooting patterns in its help center: <a href=\"https:\/\/zapier.com\/help\">Zapier help center baseline<\/a>.<\/li>\n<li><strong>Task history review:<\/strong> ops should review Zap run history weekly and scan for repeated failures tied to a specific source or field.<\/li>\n<li><strong>Rate limits and batching:<\/strong> large uploads should be processed in batches so you can isolate failures and avoid overwhelming downstream systems.<\/li>\n<li><strong>Write-back discipline:<\/strong> always write enrichment\/refresh results back to the ATS\/CRM record so recruiters don\u2019t hunt across tools.<\/li>\n<li><strong>Suppression guardrail:<\/strong> if Opt-out=true, block any downstream outreach actions in the Zap path.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Governance_who_owns_the_Zaps_how_changes_happen\"><\/span>Governance (who owns the Zaps, how changes happen)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Zap owner:<\/strong> assign one ops owner per workflow (name in your SOP).<\/li>\n<li><strong>Change requests:<\/strong> recruiters request changes via a short form (what trigger, what fields, what notification).<\/li>\n<li><strong>Testing rule:<\/strong> every change must run one test record end-to-end before re-enabling full volume.<\/li>\n<li><strong>Rollback:<\/strong> keep the last working version documented (field map + Zap version name + last test timestamp) so you can revert quickly.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Failure_handling_required\"><\/span>Failure handling (required)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Automations fail for boring reasons: renamed fields, blank required values, expired tokens, or temporary outages. Build a safety net:<\/p>\n<ul>\n<li><strong>Create a \u201cZap Errors\u201d log<\/strong> (Google Sheet\/Airtable) and write a row on any failure path: timestamp, recipe name, candidate ID, error message.<\/li>\n<li><strong>Alert the right channel:<\/strong> ops gets failures; recruiters get only \u201ccandidate ready\u201d notifications.<\/li>\n<li><strong>Retry logic:<\/strong> for transient errors, retry later; for mapping errors, stop and fix the mapping before continuing.<\/li>\n<li><strong>Suppression-first:<\/strong> if a record is opted out, the Zap should end after logging suppression.<\/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>Symptom<\/th>\n<th>Likely cause<\/th>\n<th>Fast fix in Zapier<\/th>\n<th>What to log in ATS\/CRM<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Recruiters say \u201cnumbers don\u2019t work\u201d<\/td>\n<td>Stale contact data; no refresh trigger<\/td>\n<td>Add Recipe 3 stage-based refresh; update fields on stage change<\/td>\n<td>\u201cRefreshed on\u201d date + workflow name<\/td>\n<\/tr>\n<tr>\n<td>Email bounces spike after an upload<\/td>\n<td>Old emails; intake source quality varies<\/td>\n<td>Split flow: enrich first, then push; quarantine rows missing required fields<\/td>\n<td>Email status + last checked date<\/td>\n<\/tr>\n<tr>\n<td>Candidate opted out but got contacted again<\/td>\n<td>Opt-out stored in one tool only<\/td>\n<td>Implement Recipe 4 suppression everywhere; block outreach when Opt-out=true<\/td>\n<td>Opt-out=true + timestamp + channel<\/td>\n<\/tr>\n<tr>\n<td>Duplicates in ATS\/CRM<\/td>\n<td>No matching strategy; inconsistent formatting<\/td>\n<td>Use a dedupe step before create; normalize phone\/email formatting<\/td>\n<td>Merge note + external IDs (if used)<\/td>\n<\/tr>\n<tr>\n<td>Zaps stop unexpectedly<\/td>\n<td>Token expiry or field drift<\/td>\n<td>Add failure logging + alerts; run a monthly field drift check<\/td>\n<td>Ops incident note + resolution<\/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>Use this to pick which recipe to build first. Score each item 0\u20133 (0 = not true, 3 = very true). Build the highest total first.<\/p>\n<ul>\n<li><strong>(Weight 3)<\/strong> We regularly upload lists or copy\/paste leads into the ATS\/CRM.<\/li>\n<li><strong>(Weight 3)<\/strong> Recruiters lose time hunting for the \u201clatest\u201d phone\/email across tools.<\/li>\n<li><strong>(Weight 3)<\/strong> Opt-outs are not consistently logged in the ATS\/CRM.<\/li>\n<li><strong>(Weight 2)<\/strong> We have stage changes that should trigger actions (re-engage, credentialing, offer).<\/li>\n<li><strong>(Weight 2)<\/strong> Ops spends time building daily\/weekly updates manually.<\/li>\n<li><strong>(Weight 2)<\/strong> We don\u2019t have a clear failure-handling process for automations.<\/li>\n<li><strong>(Weight 1)<\/strong> We need routing by specialty\/state\/owner without engineering.<\/li>\n<\/ul>\n<p><strong>Interpretation:<\/strong> If your opt-out score is high, build Recipe 4 first. If your upload score is high, build Recipe 1 first.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Outreach_Templates\"><\/span>Outreach Templates:<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"Template_1_Recruiter-to-Ops_request_build_the_right_Zap\"><\/span>Template 1: Recruiter-to-Ops request (build the right Zap)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Subject:<\/strong> Zap request: {Recipe name} for {specialty\/team}<\/p>\n<p><strong>Message:<\/strong> \u201cWe need a Zapier workflow that triggers when {trigger}. It should send data to Heartbeat.ai for enrichment, then update {ATS\/CRM} fields: {field list}. If Opt-out=true, it must stop and log suppression. Owner routing: {rules}. Notify: {channel}. Failure handling: write errors to {log location} and alert {ops channel}.\u201d<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_2_Candidate_note_for_ATSCRM_audit_trail\"><\/span>Template 2: Candidate note for ATS\/CRM (audit trail)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>\u201cContact data refreshed via Heartbeat.ai on {date}. Source workflow: {Recipe name}. If the candidate requests opt-out, set Opt-out=true and log channel + timestamp.\u201d<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_3_Internal_Slack_digest_daily_hot_list\"><\/span>Template 3: Internal Slack digest (daily hot list)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>\u201cDaily recruiting ops digest: New candidates added: {count}. Refreshed contacts: {count}. Opt-outs logged: {count}. Zap failures: {count}. Links: {ATS view 1}, {ATS view 2}.\u201d<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Common_pitfalls\"><\/span>Common pitfalls<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"1_Automating_before_you_define_an_automation_workflow\"><\/span>1) Automating before you define an automation workflow<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>An <strong>automation workflow<\/strong> is a repeatable, trigger-based sequence with a clear trigger, required inputs, defined outputs (write-backs), and failure handling. If you can\u2019t name the trigger and the write-back field, you don\u2019t have a workflow yet.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"2_Treating_enrichment_as_a_one-time_event\"><\/span>2) Treating enrichment as a one-time event<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Healthcare recruiting cycles stretch. If you enrich once at intake and never refresh, you\u2019ll work stale records later. Use stage-based refresh (Recipe 3) so updates happen when it matters.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"3_Not_centralizing_opt-out\"><\/span>3) Not centralizing opt-out<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If opt-out lives only in an email tool or only in a spreadsheet, it will get missed during re-uploads and reassignment. Centralize it in the ATS\/CRM and suppress downstream outreach.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"4_Over-notifying_recruiters\"><\/span>4) Over-notifying recruiters<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If every Zap posts to Slack, recruiters mute the channel. Send recruiters only \u201ccandidate ready\u201d events; send ops the failures and system noise.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"5_RECIPE_PACK_mini-case_field_drift_breaks_stable_automations\"><\/span>5) RECIPE_PACK mini-case: field drift breaks stable automations<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Common failure pattern: ops renames a field in the ATS\/CRM (for example, \u201cMobile\u201d becomes \u201cCell Phone\u201d), and your write-back step starts failing or writing to the wrong place. Add a monthly \u201cfield drift check\u201d to this RECIPE_PACK:<\/p>\n<ol>\n<li>Open each Zap and confirm the destination fields still exist.<\/li>\n<li>Run one test record end-to-end.<\/li>\n<li>Review the last week of Zap failures in your \u201cZap Errors\u201d log.<\/li>\n<li>Confirm the Opt-out=true suppression path still blocks outreach actions.<\/li>\n<\/ol>\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>Measure this by\u2026 tracking a small set of operational metrics tied to speed, quality, and compliance, then tuning the recipes that drive the biggest waste.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Measurement_instructions_required\"><\/span>Measurement instructions (required)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ol>\n<li><strong>Pick a baseline week:<\/strong> record how long intake-to-ready takes today and where handoffs stall.<\/li>\n<li><strong>Instrument each recipe:<\/strong> every Zap should write a status back to the ATS\/CRM (success\/fail, refreshed date, opt-out logged).<\/li>\n<li><strong>Review weekly:<\/strong> ops reviews Zap run history and the \u201cZap Errors\u201d log; recruiters confirm records arrive complete and usable.<\/li>\n<\/ol>\n<h3><span class=\"ez-toc-section\" id=\"Week_1_validation_checklist_no_dashboards_required\"><\/span>Week 1 validation checklist (no dashboards required)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Write-back check:<\/strong> confirm enriched fields appear on the ATS\/CRM record (not only in Zapier history).<\/li>\n<li><strong>Refresh check:<\/strong> move one record into your re-engage stage and confirm the refresh note is written back.<\/li>\n<li><strong>Suppression check:<\/strong> mark one record Opt-out=true and confirm outreach actions are blocked.<\/li>\n<li><strong>Error check:<\/strong> confirm failures create a row in the \u201cZap Errors\u201d log and alert ops.<\/li>\n<li><strong>Noise check:<\/strong> recruiters receive only \u201ccandidate ready\u201d notifications, not failure spam.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"What_to_track_definitions_included\"><\/span>What to track (definitions included)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Time-to-ready record:<\/strong> minutes from the intake trigger timestamp to the ATS\/CRM \u201ccandidate ready\u201d update timestamp.<\/li>\n<li><strong>Failure rate:<\/strong> failed Zap runs \/ total Zap runs (per 100 runs).<\/li>\n<li><strong>Suppression integrity:<\/strong> outreach attempts blocked because Opt-out=true (count per week) plus any exceptions (should be zero).<\/li>\n<li><strong>Deliverability Rate:<\/strong> delivered emails \/ sent emails (per 100 sent emails).<\/li>\n<li><strong>Bounce Rate:<\/strong> bounced emails \/ sent emails (per 100 sent emails).<\/li>\n<li><strong>Connect Rate:<\/strong> connected calls \/ total dials (per 100 dials).<\/li>\n<li><strong>Answer Rate:<\/strong> human answers \/ connected calls (per 100 connected calls).<\/li>\n<li><strong>Reply Rate:<\/strong> replies \/ delivered emails (per 100 delivered emails).<\/li>\n<\/ul>\n<p><strong>Workflow tuning:<\/strong> If bounce rate worsens after a new intake source, quarantine that source into a separate recipe and require enrichment before it enters your main ATS\/CRM pipeline.<\/p>\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>Use automation to reduce admin work\u2014not to bypass consent, privacy, or opt-out requirements. At minimum:<\/p>\n<ul>\n<li><strong>Respect opt-out immediately<\/strong> across every connected tool.<\/li>\n<li><strong>Minimize data movement:<\/strong> don\u2019t post candidate personal data into chat tools.<\/li>\n<li><strong>Limit access:<\/strong> only the recruiting team should see candidate contact fields.<\/li>\n<li><strong>Document your process:<\/strong> keep an internal SOP for how consent and opt-out are captured and enforced.<\/li>\n<\/ul>\n<p>Heartbeat.ai supports recruiting workflows, but does not provide legal counsel.<\/p>\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>Zapier behavior, triggers, and troubleshooting are documented in the Zapier Help Center. Baseline reference: <a href=\"https:\/\/zapier.com\/help\">Zapier help center baseline<\/a>.<\/p>\n<p>For how Heartbeat.ai approaches data quality, verification, and responsible use, review our <a href=\"http:\/\/heartbeat.ai\/resources\/resources\/trust-methodology\/\">trust methodology and data handling notes<\/a>.<\/p>\n<p>If you\u2019re implementing via API, start with the <a href=\"https:\/\/heartbeat.ai\/api\">Heartbeat.ai API documentation<\/a>. If you\u2019re building file-based intake, use <a href=\"https:\/\/heartbeat.ai\/upload-file\">Upload File<\/a> as the simplest on-ramp.<\/p>\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=\"Do_I_need_engineering_to_use_Zapier_for_healthcare_recruiters\"><\/span>Do I need engineering to use Zapier for healthcare recruiters?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>No. Most teams can build the recipes above with ops plus a recruiter who knows the ATS\/CRM fields. Engineering helps only if you need custom transforms.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Whats_the_safest_first_automation_to_build\"><\/span>What\u2019s the safest first automation to build?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Opt-out suppression (Recipe 4). It reduces compliance risk and prevents accidental re-contact when lists get re-uploaded, merged, or reassigned.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_prevent_duplicates_when_pushing_enriched_candidates_into_my_ATSCRM\"><\/span>How do I prevent duplicates when pushing enriched candidates into my ATS\/CRM?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use a dedupe step before creating a new record: search for an existing candidate by your chosen unique key (often email; sometimes phone), then update if found and create only if not found.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Can_I_route_candidates_by_specialty_or_state_automatically\"><\/span>Can I route candidates by specialty or state automatically?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Yes. Use Zapier Paths (or filters) after enrichment to assign owner and create the right task queue based on specialty\/state rules.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Where_should_I_store_consent_and_opt-out\"><\/span>Where should I store consent and opt-out?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Store it in the ATS\/CRM as the system of record, then sync suppression to downstream outreach tools. Always include timestamp and channel so you can audit later.<\/p>\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><strong>Pick one recipe<\/strong> from the Weighted Checklist and build it end-to-end with a 10-record test batch.<\/li>\n<li><strong>Add failure handling<\/strong> (error log + alerts) before you scale volume.<\/li>\n<li><strong>Connect Heartbeat.ai<\/strong> via the <a href=\"https:\/\/heartbeat.ai\/api\">API<\/a> or <a href=\"https:\/\/heartbeat.ai\/upload-file\">Upload File<\/a>, then write enriched fields back to your ATS\/CRM.<\/li>\n<li><strong>Go live<\/strong> and review your weekly metrics (failure rate, suppression integrity, deliverability\/bounce, connect\/answer, reply).<\/li>\n<li><a href=\"https:\/\/heartbeat.ai\/signup\">Start free search &amp; preview data<\/a> and then wire it into your first Zap.<\/li>\n<li>For a related workflow pattern, see <a href=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/ats-enrichment-workflows\/\">ATS enrichment workflows for recruiting ops<\/a>.<\/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><\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"Article\",\"articleSection\":\"Automation Cluster\",\"author\":{\"@type\":\"Person\",\"jobTitle\":\"Founder & CEO of Heartbeat.ai\",\"name\":\"Ben Argeband\"},\"headline\":\"Zapier for healthcare recruiters: 5 recipes + governance, failure handling, and metrics\",\"isAccessibleForFree\":true,\"keywords\":[\"Zapier for healthcare recruiters\",\"Zapier\",\"Heartbeat.ai\",\"API\",\"consent\",\"opt-out\"],\"mainEntityOfPage\":{\"@id\":\"https:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/\",\"@type\":\"WebPage\"},\"publisher\":{\"@type\":\"Organization\",\"name\":\"Heartbeat.ai\"}}<\/script><br \/>\n<script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No. Most teams can build the recipes above with ops plus a recruiter who knows the ATS\/CRM fields. Engineering helps only if you need custom transforms.\"},\"name\":\"Do I need engineering to use Zapier for healthcare recruiters?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Opt-out suppression (Recipe 4). It reduces compliance risk and prevents accidental re-contact when lists get re-uploaded, merged, or reassigned.\"},\"name\":\"What\u2019s the safest first automation to build?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Use a dedupe step before creating a new record: search for an existing candidate by your chosen unique key (often email; sometimes phone), then update if found and create only if not found.\"},\"name\":\"How do I prevent duplicates when pushing enriched candidates into my ATS\/CRM?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Yes. Use Zapier Paths (or filters) after enrichment to assign owner and create the right task queue based on specialty\/state rules.\"},\"name\":\"Can I route candidates by specialty or state automatically?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Store it in the ATS\/CRM as the system of record, then sync suppression to downstream outreach tools. Always include timestamp and channel so you can audit later.\"},\"name\":\"Where should I store consent and opt-out?\"}]}<\/script><\/p>","protected":false},"excerpt":{"rendered":"<p>A recruiter-ops playbook for Zapier: 5 named recipes (upload\u2192enrich\u2192ATS\/CRM, inbound enrichment, stage refresh, opt-out suppression, daily digest) plus governance, failure handling, and measurement.<\/p>","protected":false},"author":5,"featured_media":54302,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_yoast_wpseo_focuskw":"Zapier for healthcare recruiters","_yoast_wpseo_title":"Zapier for healthcare recruiters: 5 recipes + governance + metrics","_yoast_wpseo_metadesc":"Build 5 practical Zapier recipes for healthcare recruiting ops: upload\u2192enrich\u2192ATS\/CRM, inbound lead enrichment, stage refresh, opt-out suppression, and daily digests\u2014plus governance, failure handling, and metrics.","_custom_permalink":"integrations-automation\/zapier-for-healthcare-recruiters","footnotes":""},"categories":[1],"tags":[],"class_list":["post-54303","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 v27.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\r\n<title>Zapier for healthcare recruiters: 5 recipes + governance + metrics<\/title>\r\n<meta name=\"description\" content=\"Build 5 practical Zapier recipes for healthcare recruiting ops: upload\u2192enrich\u2192ATS\/CRM, inbound lead enrichment, stage refresh, opt-out suppression, and daily digests\u2014plus governance, failure handling, and metrics.\" \/>\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=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/\" \/>\r\n<meta property=\"og:locale\" content=\"en_US\" \/>\r\n<meta property=\"og:type\" content=\"article\" \/>\r\n<meta property=\"og:title\" content=\"Zapier for healthcare recruiters: 5 recipes + governance + metrics\" \/>\r\n<meta property=\"og:description\" content=\"Build 5 practical Zapier recipes for healthcare recruiting ops: upload\u2192enrich\u2192ATS\/CRM, inbound lead enrichment, stage refresh, opt-out suppression, and daily digests\u2014plus governance, failure handling, and metrics.\" \/>\r\n<meta property=\"og:url\" content=\"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/\" \/>\r\n<meta property=\"og:site_name\" content=\"Heartbeat.ai\" \/>\r\n<meta property=\"article:published_time\" content=\"2026-02-01T18:57:06+00:00\" \/>\r\n<meta property=\"article:modified_time\" content=\"2026-02-27T19:34:17+00:00\" \/>\r\n<meta property=\"og:image\" content=\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/zapier-for-healthcare-recruiters-1e039507.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=\"14 minutes\" \/>\r\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/#article\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/\"},\"author\":{\"name\":\"Ben Argeband\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/person\\\/7b323ddce9b211907423482e2f9db173\"},\"headline\":\"Zapier for healthcare recruiters: 5 recipes + governance, failure handling, and metrics\",\"datePublished\":\"2026-02-01T18:57:06+00:00\",\"dateModified\":\"2026-02-27T19:34:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/\"},\"wordCount\":2867,\"commentCount\":0,\"publisher\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\"},\"image\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/zapier-for-healthcare-recruiters-1e039507.png\",\"articleSection\":[\"News\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/\",\"url\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/\",\"name\":\"Zapier for healthcare recruiters: 5 recipes + governance + metrics\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/#primaryimage\"},\"image\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/zapier-for-healthcare-recruiters-1e039507.png\",\"datePublished\":\"2026-02-01T18:57:06+00:00\",\"dateModified\":\"2026-02-27T19:34:17+00:00\",\"description\":\"Build 5 practical Zapier recipes for healthcare recruiting ops: upload\u2192enrich\u2192ATS\\\/CRM, inbound lead enrichment, stage refresh, opt-out suppression, and daily digests\u2014plus governance, failure handling, and metrics.\",\"breadcrumb\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/#primaryimage\",\"url\":\"https:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/zapier-for-healthcare-recruiters-1e039507.png\",\"contentUrl\":\"https:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/zapier-for-healthcare-recruiters-1e039507.png\",\"width\":1024,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/integrations-automation\\\/zapier-for-healthcare-recruiters\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/heartbeat.ai\\\/healthcare\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Zapier for healthcare recruiters: 5 recipes + governance, failure handling, and metrics\"}]},{\"@type\":\"WebSite\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#website\",\"url\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/\",\"name\":\"Heartbeat.ai\",\"description\":\"\",\"publisher\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\",\"name\":\"Heartbeat.ai\",\"url\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\\\/\\\/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\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/person\\\/7b323ddce9b211907423482e2f9db173\",\"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\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/author\\\/ben-argeband\\\/\"}]}<\/script>\r\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Zapier for healthcare recruiters: 5 recipes + governance + metrics","description":"Build 5 practical Zapier recipes for healthcare recruiting ops: upload\u2192enrich\u2192ATS\/CRM, inbound lead enrichment, stage refresh, opt-out suppression, and daily digests\u2014plus governance, failure handling, and metrics.","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":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/","og_locale":"en_US","og_type":"article","og_title":"Zapier for healthcare recruiters: 5 recipes + governance + metrics","og_description":"Build 5 practical Zapier recipes for healthcare recruiting ops: upload\u2192enrich\u2192ATS\/CRM, inbound lead enrichment, stage refresh, opt-out suppression, and daily digests\u2014plus governance, failure handling, and metrics.","og_url":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/","og_site_name":"Heartbeat.ai","article_published_time":"2026-02-01T18:57:06+00:00","article_modified_time":"2026-02-27T19:34:17+00:00","og_image":[{"width":1024,"height":1024,"url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/zapier-for-healthcare-recruiters-1e039507.png","type":"image\/png"}],"author":"Ben Argeband","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ben Argeband","Est. reading time":"14 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#article","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/"},"author":{"name":"Ben Argeband","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173"},"headline":"Zapier for healthcare recruiters: 5 recipes + governance, failure handling, and metrics","datePublished":"2026-02-01T18:57:06+00:00","dateModified":"2026-02-27T19:34:17+00:00","mainEntityOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/"},"wordCount":2867,"commentCount":0,"publisher":{"@id":"http:\/\/heartbeat.ai\/resources\/#organization"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#primaryimage"},"thumbnailUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/zapier-for-healthcare-recruiters-1e039507.png","articleSection":["News"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#respond"]}]},{"@type":"WebPage","@id":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/","url":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/","name":"Zapier for healthcare recruiters: 5 recipes + governance + metrics","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/#website"},"primaryImageOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#primaryimage"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#primaryimage"},"thumbnailUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/zapier-for-healthcare-recruiters-1e039507.png","datePublished":"2026-02-01T18:57:06+00:00","dateModified":"2026-02-27T19:34:17+00:00","description":"Build 5 practical Zapier recipes for healthcare recruiting ops: upload\u2192enrich\u2192ATS\/CRM, inbound lead enrichment, stage refresh, opt-out suppression, and daily digests\u2014plus governance, failure handling, and metrics.","breadcrumb":{"@id":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#primaryimage","url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/zapier-for-healthcare-recruiters-1e039507.png","contentUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/zapier-for-healthcare-recruiters-1e039507.png","width":1024,"height":1024},{"@type":"BreadcrumbList","@id":"http:\/\/heartbeat.ai\/resources\/integrations-automation\/zapier-for-healthcare-recruiters\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/heartbeat.ai\/healthcare\/"},{"@type":"ListItem","position":2,"name":"Zapier for healthcare recruiters: 5 recipes + governance, failure handling, and metrics"}]},{"@type":"WebSite","@id":"http:\/\/heartbeat.ai\/resources\/#website","url":"http:\/\/heartbeat.ai\/resources\/","name":"Heartbeat.ai","description":"","publisher":{"@id":"http:\/\/heartbeat.ai\/resources\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"http:\/\/heartbeat.ai\/resources\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"http:\/\/heartbeat.ai\/resources\/#organization","name":"Heartbeat.ai","url":"http:\/\/heartbeat.ai\/resources\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/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":"http:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173","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":"http:\/\/heartbeat.ai\/resources\/author\/ben-argeband\/"}]}},"_links":{"self":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54303","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=54303"}],"version-history":[{"count":1,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54303\/revisions"}],"predecessor-version":[{"id":54510,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54303\/revisions\/54510"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media\/54302"}],"wp:attachment":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media?parent=54303"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/categories?post=54303"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/tags?post=54303"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}