Post: How to Automate New Hire Onboarding with Keap: A Step-by-Step Workflow Guide

By Published On: August 14, 2025

How to Automate New Hire Onboarding with Keap: A Step-by-Step Workflow Guide

Onboarding is the first proof point that your hiring process delivers on its promise. When it’s manual, inconsistent, and admin-heavy, new hires notice — and early attrition follows. SHRM research consistently identifies poor onboarding as one of the primary drivers of first-year turnover, and Harvard Business Review has documented the compounding cost of losing an employee before they reach full productivity. The fix isn’t more HR headcount. It’s a Keap workflow that runs the routine delivery automatically so your team can focus on the human moments that matter.

This guide is the operational complement to Fix 10 Keap Automation Mistakes in HR & Recruiting — specifically the structural errors that cause onboarding workflows to break at the trigger or stall mid-sequence. Follow these steps in order. Skipping stage-setting (Steps 1–2) and jumping straight to content (Steps 3–5) is the most common build mistake we see.


Before You Start

Gather these before opening Keap’s campaign builder:

  • Role/department list: Every hire category that will have a distinct onboarding track (e.g., Sales, Engineering, Operations, Finance).
  • Content inventory: Welcome video links, policy document URLs, benefits enrollment links, culture resources — organized by role where they differ.
  • Internal stakeholder emails: IT, payroll, facilities, and any department that needs advance notice of a new hire’s start date and requirements.
  • Custom fields confirmed: At minimum — Department, Start Date, Manager Name, Location. These feed your decision branches and notification emails.
  • Time budget: A single-role workflow takes 4–8 hours to build and test. A multi-role workflow needs 2–3 build sessions plus a week of test-mode observation.
  • Risk flag: If your organization requires legally compliant document signing (I-9, W-4, NDA), do not route those through Keap email alone. Connect a compliant e-signature tool and store confirmation back on the Keap contact record via custom field.

Step 1 — Define Your Trigger Tag and Apply It Consistently at Offer Acceptance

The trigger tag is the single most important decision in your entire onboarding build. Everything downstream depends on it firing reliably at the right moment.

Create a tag named Onboarding – Pending Start (or your equivalent naming convention). This tag should be applied the moment an offer is verbally or formally accepted — not on the first day, not after paperwork, not when IT is ready. Apply it at acceptance.

Configure your Keap campaign to use this tag as the campaign goal trigger. Set the campaign to start immediately upon tag application. Do not use a manual “Add to Campaign” step as your primary entry point — manual steps fail when HR is busy, which is exactly when onboarding volume peaks.

Action: Open Keap → Campaign Builder → Create New Campaign → Set Goal = “Contact is Tagged” → Select “Onboarding – Pending Start.”

If you’re sourcing hires from an ATS or applicant tracking spreadsheet, connect your automation platform to apply this tag automatically when an offer status field changes. This eliminates the manual tag-apply step entirely. For more on building reliable tag architecture, see our guide on Keap tag strategy for HR and recruiters.

One additional tag to set now: Apply a Remove from Recruitment Sequences stop action simultaneously. New hires still sitting in candidate nurture campaigns receive jarring, tone-deaf emails. Stop all recruitment sequences at the moment the onboarding tag fires.


Step 2 — Segment by Role Before Building Any Content Steps

A single generic onboarding sequence applied to every hire is the most common structural failure in Keap onboarding builds. Asana’s Anatomy of Work research shows that employees who receive irrelevant communication disengage from information streams quickly — the same effect applies internally. A developer receiving sales process training stops opening the emails. When they stop opening onboarding emails, they miss the content that does apply to them.

Immediately after your trigger goal, insert a decision diamond in the campaign that reads the “Department” custom field and branches into separate sequence tracks.

Build one branch per hire category. At minimum:

  • Branch A: Sales / Business Development
  • Branch B: Engineering / Technical
  • Branch C: Operations / Finance / Admin
  • Branch D: Leadership / Management (if applicable)

Each branch feeds into its own sequence of content steps. The trigger logic, internal notifications, and check-in timing are shared across all branches — only the content emails differ.

Action: In Campaign Builder, drag a Decision Diamond after your trigger goal. Set the condition to “Custom Field: Department equals [value]” for each branch. Connect each branch to its dedicated sequence.

This architecture also supports segmenting your talent pool with Keap automation upstream in recruitment — making the transition from candidate to new hire a seamless data handoff rather than a re-entry exercise.


Step 3 — Build the Internal Notification Layer

Before the new hire receives a single email, your internal stakeholders need to know a hire is confirmed. Parseur’s Manual Data Entry Report documents that manual handoffs between HR, IT, and payroll introduce both delays and transcription errors — the same category of error that created a $27K payroll discrepancy in a real mid-market manufacturing company we worked with (the offer letter said $103K; the HRIS showed $130K after manual re-entry; the employee quit within months).

Immediately inside the campaign, add an internal notification sequence that fires within the first hour of trigger-tag application. Build separate notification emails for:

  • IT: New hire name, role, start date, location, equipment specifications (pulled from custom fields).
  • Payroll/HR Operations: Compensation details (pulled from custom field), start date, direct manager.
  • Hiring Manager: Confirmation that onboarding automation has been triggered, link to their assigned day-1 tasks.
  • Facilities (if applicable): Badge access, desk/office assignment needs, parking.

Action: In your campaign, add an Email step immediately after the trigger goal (before the decision diamond branches, so it fires for all hires). Set recipients using the internal notification fields. Use Keap merge fields to pull contact record data into the email body automatically — no copy-pasting by HR.

Assign a Keap task to the hiring manager with a due date 5 business days before the start date: “Confirm new hire readiness checklist complete.” This closes the loop on the human elements automation cannot handle.


Step 4 — Build the Pre-Start Welcome Sequence (3 Emails Maximum)

The pre-start window — offer acceptance to day one — is where new hire enthusiasm peaks and anxiety spikes simultaneously. Research from RAND Corporation on employee engagement shows that early perceived organizational support is one of the strongest predictors of retention. Your pre-start sequence is delivering that support signal.

Limit pre-start emails to three. More creates anxiety rather than reducing it.

Pre-Start Email 1 — Acceptance Confirmation (Send: Day 0, within 1 hour of trigger)

  • Confirm the offer details: role, start date, location or remote setup.
  • Express genuine welcome — this can be personalized with the hiring manager’s name via merge field.
  • Set expectations: “You’ll hear from us three more times before your first day.”
  • Include one clear next step: a benefits enrollment link or a pre-start paperwork portal link.

Pre-Start Email 2 — First-Week Logistics (Send: 3 days before start date)

  • Day-one schedule: start time, location or video link, who to contact upon arrival.
  • Parking, badge, or access instructions.
  • What to bring (if anything).
  • Do not include policy documents or training materials here — save them for post-start drips.

Pre-Start Email 3 — Personal Welcome (Send: 1 day before start)

  • Shorter and warmer in tone than Email 2.
  • Can include a short video message from the team or hiring manager (linked, not embedded).
  • Reiterate the day-one logistics in two bullet points only.
  • “We’ll see you tomorrow” is sufficient. Don’t add new information.

Action: In each role-segmented branch, add three timed email steps using Keap’s timer nodes. Set Email 1 to send immediately, Email 2 to send based on a date field (“X days before Start Date”), and Email 3 to send 1 day before Start Date. Keap’s date-based timers require the Start Date custom field to be populated at trigger time — confirm this in your process.


Step 5 — Build the Post-Start Content Drip (Days 1–30)

The most damaging onboarding mistake is front-loading. Gartner research on employee experience consistently shows that information overload in the first week correlates with decreased retention of critical policy and process knowledge. McKinsey Global Institute’s work on knowledge worker productivity reinforces that spaced information delivery outperforms batch delivery for retention and application.

Structure your post-start drip as a progressive reveal across 30 days:

Week 1 (Days 1–5): Orientation Essentials

  • Day 1: Systems access confirmation + who’s who org chart.
  • Day 2: Core tools walkthrough (role-specific, linked to short video or doc).
  • Day 3: Benefits enrollment reminder with deadline date.
  • Day 5: End-of-week check-in prompt — one question: “What’s one thing you’re still looking for?”

Week 2 (Days 8–10): Role and Team Immersion

  • Department processes and key contacts.
  • Role-specific performance expectations for the first 90 days.
  • Introduction to cross-functional partners.

Weeks 3–4 (Days 15–30): Culture and Belonging

  • Company values with real examples (link to internal stories or case examples).
  • Employee resource groups or social channels to join.
  • 30-day milestone acknowledgment email at day 28.

Action: Use Keap timer nodes set to specific day offsets from the trigger date. For role-specific content, build separate email sequences in each branch but use the same timer structure. This makes future content updates simple — you change one email in one branch without rebuilding the campaign architecture.

Reference our guide on Keap sequences for candidate nurturing for sequence architecture patterns that translate directly to new-hire content drips.


Step 6 — Configure 30/60/90-Day Check-In Automations

The onboarding relationship doesn’t end after the first-week flurry. SHRM data indicates that most early-attrition decisions are made between weeks 6 and 12 — well after most organizations have stopped deliberate onboarding touchpoints. Your Keap workflow needs to extend into that window automatically.

Day 30 — Pulse Survey

Send an automated email with a one-question survey (link to Keap form or external survey tool): “How would you rate your onboarding experience so far?” Capture responses back into a Keap custom field. Flag any response below a threshold score for immediate manager follow-up via an automatic task assignment.

Day 60 — Manager Check-In Task

Trigger a Keap task assigned to the hiring manager: “Schedule 30-minute structured feedback conversation with [New Hire Name].” Include a link to a simple agenda template. This is a task, not an email to the new hire — it prompts the human conversation that automation cannot replace.

Day 90 — Milestone Recognition and Tag Transition

Send a milestone recognition email to the new hire. Then apply the tag Onboarding – Complete and remove the Onboarding – Pending Start tag. Simultaneously, enroll the contact in your standard employee communication campaigns. This clean tag transition prevents new hires from receiving onboarding content indefinitely and ensures they move into the correct ongoing communication track.

Action: Set three timed sequences off the original trigger: one at +30 days, one at +60 days, one at +90 days. Each fires its respective email or task. The day-90 step includes a tag-apply and tag-remove action pair to execute the clean handoff.

For guidance on measuring whether these check-in touchpoints are driving retention outcomes, see measuring HR automation ROI in Keap.


How to Know It Worked

A functioning Keap onboarding workflow produces measurable signals within the first two hiring cycles:

  • Email open rates: Day-0 and Day-1 emails should open above 70%. Pre-start logistics emails should open above 85%. If they’re below 50%, the send timing or subject line is wrong — not the content.
  • Task completion rates: Manager check-in tasks at day 60 should complete within 5 business days of assignment. If completion lags, add a task reminder email to the manager (Keap supports automated task reminders).
  • Tag progression: Every contact tagged Onboarding – Pending Start should receive the Onboarding – Complete tag within 90–95 days. Contacts stuck in pending status indefinitely indicate a broken sequence step — audit those contacts first.
  • Pulse survey scores: Establish a baseline in cycle one. Any score decline between cycles indicates a content or timing problem in the workflow, not a hiring problem.
  • Time-to-productivity proxy: If your hiring manager conducts 60-day check-ins (triggered by Keap task), track self-reported confidence scores. Improvement over multiple cohorts indicates the drip content is landing.

Common Mistakes and Troubleshooting

Mistake 1: The trigger tag fires but the campaign doesn’t start

Check that the campaign’s goal is set to “Contact is Tagged” — not “Tag Applied via Action Set.” These behave differently in some Keap configurations. Also confirm the campaign is published, not in draft mode. Draft campaigns do not process contacts.

Mistake 2: New hires still receive recruitment emails after onboarding starts

You need an explicit campaign stop on all recruitment sequences. Apply a stop-campaign action or remove the recruitment tag simultaneously with the onboarding tag. Keap does not automatically suppress parallel sequences — you must configure the stop.

Mistake 3: The decision diamond routes everyone to the wrong branch

The custom field value in the contact record must exactly match the condition in the decision diamond — including capitalization and spacing. “Sales” and “sales” are different values. Standardize field values upstream in your offer workflow and test with a sample contact before going live.

Mistake 4: Date-based timer emails send on wrong dates

Keap’s date-based timers require the reference date (Start Date) to be populated before the contact enters the sequence. If the field is empty at trigger time, the timer defaults to campaign entry date, not start date. Confirm your intake process populates Start Date before or at the moment the trigger tag is applied.

Mistake 5: The workflow runs fine for one hire but breaks at scale

This is almost always a custom field conflict — two records with incomplete data entering the decision diamond simultaneously. Audit your offer intake form to enforce required fields before the trigger tag can be applied. Keap forms can be configured to require field completion before submission.

If you are also working to optimize the upstream interview-to-offer handoff, the companion guide on how to automate interview scheduling with Keap covers the trigger architecture that feeds cleanly into this onboarding workflow.


A reliable Keap onboarding workflow is the final mile of your talent acquisition investment. The recruiting sequences, job postings, and interview processes documented in the essential Keap automation workflows for recruiters guide all culminate here. If the onboarding workflow breaks, you lose the hire — and the cost of that loss, per SHRM and Forbes composite data, can reach multiples of annual salary. Build the trigger right, segment early, and let the automation handle delivery so your team handles the relationship. That’s the architecture that retains people.

For organizations operating across jurisdictions, also review Keap GDPR compliance for HR before deploying automated onboarding communications to employees in covered regions.