# Personalized onboarding guides for new engineers in Notion

> Every Monday, we find your new engineering hires, write each one a guide to your actual tech stack from current documentation, and send it to them in Slack.

- Workflow type: agent
- Services: Context7, BambooHR, Notion, Slack
- Categories: Engineering, HR & People
- Published: 2026-08-04

## What it does

- Checks your HR system every Monday morning for anyone in an engineering role who started in the last seven days
- Looks up living documentation for each framework and library your team actually builds on, at the version you run in production
- Writes each new hire their own onboarding guide, organized library by library with a short orientation, the key concepts and real code examples
- Publishes the guide to your engineering space in Notion and sends the new starter a friendly welcome message in Slack pointing them to it

## What you'll need

- A BambooHR account, or another employee directory the workflow can read new starters from
- A Context7 account for up to date library documentation
- A Notion workspace with an engineering area where the guides can be created
- A Slack workspace that your new hires are added to
- A list of the frameworks and libraries your team builds on, with the version you run

## Prompt

Every Monday at 8am, find the engineers who started in the last seven days and write each one a personalized onboarding guide built from the current documentation for the libraries we actually build on.

Start in BambooHR. Use Get Employee Directory to pull the roster, then narrow it to people in engineering roles using job title and department, for example Engineer, Developer, QA, SRE, Data or Platform. The directory's default fields may not include a start date, so for each engineering candidate confirm the hire date with Get Employee, asking for the hire date field, and keep only the people whose start date falls within the last seven days. Request Custom Report is a good alternative if you would rather get name, work email, job title, department and hire date back in a single call. If nobody qualifies this week, stop without creating pages or sending messages.

Our house stack is a configured list of libraries paired with the version we run in production, for example Next.js 15, React 19, TypeScript 5.x, Tailwind CSS 4, Postgres and Prisma. Keep this list editable at the top of the workflow so we can maintain it as the stack changes, and treat it as the single source of truth for what a new engineer needs to learn.

For each library in that list, call Context7 Search for Libraries to resolve the name to a Context7 library ID, choosing the match that corresponds to the version we run. Then call Get Documentation Context for that library ID with a natural language query covering the getting started path, the core concepts a new engineer has to understand, and current best practices at that version. Ask for enough real code snippets to be genuinely useful.

Assemble one guide per new hire, organized library by library. For each library, write a short orientation of a few sentences on what it does and why we use it, then the key concepts, then a few real code snippets drawn from the documentation that came back. Open the guide with a brief welcome that uses the person's name and role, and weight the content toward what is genuinely useful in week one rather than writing an exhaustive reference.

Publish the finished guide to our engineering space in Notion with Create a Page, parented to the engineering onboarding page and titled with the new hire's name and start date, for example "Onboarding guide: Priya Raman, starting 4 August". Use proper headings, paragraphs and code blocks so it reads as a real document rather than a wall of text.

Then reach the person in Slack. Use List Users to find the Slack account whose email matches their BambooHR work email, Open a Conversation to open a direct message with them, and Send a Message that welcomes them, links their Notion page, and explains in a sentence that the guide was written against the versions we actually run. If no Slack account matches their email yet, which is common in someone's first week, skip the direct message for that person and note it in the run, but still publish their page.

Everything in the guide must come from the documentation Context7 returns for the version we run, never from memory and never from an internal wiki page. That is the entire point of this workflow: every new starter should get a guide that is accurate on the day they read it.

## How to customize

- Change the timing. Monday morning suits weekly cohorts, but you can run it daily so each person gets their guide on the morning they start.
- Edit the stack list. This is the heart of the workflow, so keep it current as you adopt or drop libraries, and include the version you actually run.
- Swap or skip the HR system. Any employee directory works the same way, and if you would rather not connect HR at all you can simply hand the workflow the new hire's name, email and role.
- Route it for review first. Send the guide to the hiring manager for a once over before the new starter gets their welcome message.

## Example output

Onboarding guide: Priya Raman, starting 4 August

Welcome Priya. You are joining as a Senior Frontend Engineer, so this guide covers the six libraries you will touch in your first week, written against the versions we run in production today.

## Next.js 15.1

Orientation. Next.js is the framework the whole product renders through. Everything user facing lives in the App Router, and we lean on server components by default and drop to client components only where we need interactivity.

Key concepts. The App Router file conventions (layout, page, loading, error), server versus client components, data fetching and caching in server components, and route handlers for our API surface.

...followed by real code snippets pulled from the current 15.1 documentation, then the same treatment for React 19, TypeScript 5.x, Tailwind CSS 4, Postgres and Prisma.

Slack DM to Priya:
"Welcome aboard Priya! I put together an onboarding guide for our stack, written against the exact versions we run rather than an old wiki page: [Notion link]. Start with the Next.js and React sections, they will cover most of week one. Shout if anything looks off."

## FAQ

### Do we have to use BambooHR?

No. BambooHR is just the assumed HR system. The same workflow shape works with any employee directory it can read names, roles, start dates and work emails from. If you would rather not connect an HR system at all, you can skip that step and give the workflow the new hire's details directly.

### Will the guide match the version of each library we actually run?

Yes, and that is the point. The documentation is looked up per library at the version you specify, so a new starter gets guidance that is true for your codebase today rather than whatever was current when someone last updated the wiki.

### What happens on a week when nobody joins?

Nothing. If no one in an engineering role started in the last seven days, the workflow stops quietly without creating empty pages or sending any messages.

### Does this replace our existing onboarding documentation?

It replaces the part that goes stale fastest, which is the technical grounding in your frameworks and libraries. Your own material about how the team works, who to ask and where things live still lives in Notion alongside it.

### Can we see the guide before the new hire does?

Yes. A common tweak is to publish the Notion page and send it to the hiring manager first, then let them forward it on, rather than messaging the new starter automatically.

Use this prompt in General Input: https://www.generalinput.com/prompts/personalized-onboarding-guides-for-new-engineers-in-notion