Personalized onboarding guides for new engineers in Notion

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.