Prepare new-hire onboarding emails from Gmail

Onboarding emails go out late or not at all when HR is busy. An Orkeste agent runs every morning, reads your list of new hires and their start dates in Airtable or Notion, and prepares the email that is due for each one: welcome, first-day logistics, first-week check-in. In Gmail the emails become drafts HR sends; from Outlook they are sent once approved.

The problem

A new hire forms an opinion of the company in the first two weeks. A missed welcome email or first-day instructions sent the night before leave a mark.

How the workflow runs

Runs: Every day at the hour you set.

  1. Read the new hires: The agent reads the new-hire records in Airtable or Notion: name, role, manager, start date.
  2. Find what is due: From the start date, it works out which email of your sequence is due today.
  3. Write the email: It personalises your template with the role, the manager and the location.
  4. Approve: Each email waits in Validations for HR.
  5. Draft or send: In Gmail the approved email becomes a draft HR sends; from Outlook it is sent.
  6. Log the step: It updates the new hire's record with the step completed.

Every email waits in Validations, and in Gmail HR still presses send.

Who does what

What this workflow does not do

Works with your stack

Questions about this workflow

Why drafts in Gmail?

Gmail approvals create drafts by design, so the email always leaves by a person's hand. With Outlook, approved emails are sent directly.

Where does the agent find the new hires?

In an Airtable table or a Notion database with the name, role, manager and start date. Agents do not connect to an HR system today.

Can each role get different emails?

Yes. Put your templates in the briefing or in a Notion page, with the variations by role or location.

Related workflows

Keep reading