---
title: "Onboard from the first day to six months"
description: "One Start of Onboarding automation carries every new starter from day one through week one, 30 days, 90 days and a six-month check-in, with a probation nudge, and nobody remembers to send anything."
sidebar:
  order: 1
area: use-cases
appPath: /flows/home
lastVerified: 2026-11-13
version: "2026-11-13"
audience: admin
related:
  - getting-started/tutorial-launch-first-day-onboarding
  - flows/steps/schedule-a-step
  - flows/automations/publish-an-automation
  - flows/automations/change-the-mode
---

Every new starter gets a welcome on day one, a pulse at the end of week one, the handbook at 30 days, a check-in at 90 and another at six months, from one automation timed off their start date. **For:** admins and owners. **Time:** about 30 minutes with the content written; about 10 to extend a 90-day flow you already run.

![The finished automation: the Start of Onboarding trigger and six steps from day one to six months, with the probation nudge to the manager at 150 days.](https://support.pyn.ai/media/use-cases/onboarding-to-six-months/use-cases-onboarding-to-six-months-automation.png)

## What you'll need

- **Start Date** synced from your HRIS; every source provides it. For a probation nudge timed off the HRIS date, **Probation End Date**, which HiBob supplies; see [HRIS fields](https://support.pyn.ai/integrations/hris-fields/).
- An email sender, or Slack connected for direct messages; see [Add an email sender](https://support.pyn.ai/settings/senders/add-an-email-sender/) and [Slack](https://support.pyn.ai/integrations/slack/).
- The handbook and benefits guide published in **Library** > **Content**; see [Publish content](https://support.pyn.ai/library/content/publish-content/).
- Optional: the **Start of Onboarding** template from the catalogue. It gives you the trigger; you add the steps.

## Build it

1. Create an automation with the **Start of Onboarding** trigger under **Employee Lifecycle**, set **This flow starts** to **on the day of** and leave the recurrence at **just once**, so the start date is the reference date for every step; see [Configure a date trigger](https://support.pyn.ai/flows/automations/configure-a-date-trigger/).

2. On the **Audience** tab keep **Current** and **Joiner**, so someone enrols before their first day if the trigger fires early; see [Launch first-day onboarding end to end](https://support.pyn.ai/getting-started/tutorial-launch-first-day-onboarding/).

3. Add a **Send Email to Employee** welcome **on the day of** at 09:00 in the **Recipient Time Zone**, then a step **7 days after** that embeds a one-question poll on how the first week went; see [Schedule a step](https://support.pyn.ai/flows/steps/schedule-a-step/) and [Run a quick poll](https://support.pyn.ai/flows/polls/run-a-quick-poll/).

4. Add steps **30 days after** and **90 days after**, each with a **Link to Library Content** button to the handbook or benefits guide; see [Link to content from a message](https://support.pyn.ai/library/content/use-content-in-a-step/).

5. Add a six-month check-in **180 days after** and a probation nudge with **To** set to **Manager** at **Custom** 150 **Days** **After**; see [Schedule a step](https://support.pyn.ai/flows/steps/schedule-a-step/) and [Choose recipients and Cc](https://support.pyn.ai/flows/steps/choose-recipients-and-cc/).

6. Publish, then set the mode to **Verification** so the first cohort waits in **Needs Review**, and switch to **Automated** after a week or two of clean reviews; see [Publish an automation](https://support.pyn.ai/flows/automations/publish-an-automation/) and [Change the mode of an automation](https://support.pyn.ai/flows/automations/change-the-mode/).

7. Enrol yourself with **Flag as Test** and a **Reference Date** a few days out, and read each message as it arrives; see [Manually enroll employees](https://support.pyn.ai/flows/automations/manually-enroll-employees/).

## Variations

**Slack**

Swap the later steps for **Send Direct Message** so the poll and the check-ins land where people chat, as in [Add a direct message step](https://support.pyn.ai/flows/steps/add-a-direct-message-step/). Keep the day-one welcome on email: a recipient whose Slack account is not matched gets a **Bounced** delivery with the reason **Recipient Not Available In Slack**. On the Slack steps, tick **Send by email if the recipient is not in Slack** on the **Advanced** tab so anyone without a Slack account gets the message by email; see [Send a direct message by email when someone is not in Slack](https://support.pyn.ai/flows/steps/send-by-email-when-not-in-slack/).

**Email**

Keep every step as **Send Email to Employee** and set **From** to your People team's mailbox so a reply reaches a person; see [Add an email step](https://support.pyn.ai/flows/steps/add-an-email-step/). In email the poll is a button to a page with the same row of answers.

**Probation from the HRIS date.** Where **Probation End Date** is synced, build a second automation on it under **Employee Properties** with **This flow starts** at **2 weeks before**; see [Configure an employee property trigger](https://support.pyn.ai/flows/automations/configure-an-employee-property-trigger/). For 90 days only, the catalogue's **90-day check-in** template shifts the reference date 90 days after the start and fires **2 weeks before** it; see [Trigger catalogue](https://support.pyn.ai/flows/automations/trigger-catalogue/).

## Watch out for

- In **Verification** nothing sends until you open **Needs Review**, select **Verify** and **Unpause** each enrollment; the Automations table shows **Verify** as the status, and a flow left there looks published but is silent; see [Review and unpause enrollments](https://support.pyn.ai/activity/enrollments/review-and-unpause-enrollments/).
- Extending a running 90-day flow to six months reaches people already enrolled only if you tick them in **Update Enrollments** after publishing, or later from **Update Active Enrollments** on the mode menu; anything already sent is left alone; see the [FAQ](https://support.pyn.ai/faq/) and [Publish an automation](https://support.pyn.ai/flows/automations/publish-an-automation/).
- A person added to the HRIS after their start date enrols late and every step already due sends at once; turn on **Skip if overdue at enrollment** on the welcome, or decide per person in **Verification**; see [Handle late enrollments](https://support.pyn.ai/flows/automations/handle-late-enrollments/).
- Answering the poll never marks the delivery **Actioned**, so do not add reminders to that step expecting them to stop; see [Run a quick poll](https://support.pyn.ai/flows/polls/run-a-quick-poll/).
- **every year** and the other recurrences are for anniversaries, in their own automation; onboarding stays at **just once**; see [Configure a date trigger](https://support.pyn.ai/flows/automations/configure-a-date-trigger/).

## Check it worked

Each new starter appears under [Enrollments](https://support.pyn.ai/activity/enrollments/) with their start date as **Reference** and six steps dated from day one to day 180. In **Verification** the row sits in **Needs Review** with a **Verify** button; once unpaused, the welcome shows as delivered and the rest as **Scheduled**. The poll's **Activity** drawer in **Flows** > **Polls** lists each answer by name, and [Track actions](https://support.pyn.ai/activity/actions/track-actions/) shows who opened the handbook.

## Related

- [Launch first-day onboarding end to end](https://support.pyn.ai/getting-started/tutorial-launch-first-day-onboarding/) to build the first three steps in one sitting.
- [Reach new starters before day one](https://support.pyn.ai/use-cases/pre-boarding/) for the week before the start date, to a personal address.
- [Give managers a new-hire checklist](https://support.pyn.ai/use-cases/manager-checklist-for-a-new-hire/) for the manager's steps inside this automation.
- [Schedule a step](https://support.pyn.ai/flows/steps/schedule-a-step/) for the offsets, custom days and delivery days.
