Prepare everything a new joiner needs on day one
A per-role onboarding checklist with real owners and dates, created before the start date. Built for an operations lead who assembles the same onboarding list every time, from memory.
Notion
Slack
4 steps2 integrationsRuns on demand
The checklist lives in one person's head. What it costs while the work is still done by hand.
- 01The checklist lives in one person's head.
- 02Something is always forgotten until the new joiner asks.
- 03Each department is chased separately.
- Read roleSupport Engineer · Aug 4
- Build list14 items · from the template
- Create taskscreate_page · 14 with owners
- Notify ownerspost_message · 5 owners
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the role and start date.Notion
- 02Build the checklist for that role from your template.ModuleX
- 03Create the tasks with owners and due dates.Notion
- 04Notify the owners in one message.Slack
The workflow is an editable graph. Reading runs freely; create the tasks with owners and due dates waits for your opt-in approval until you loosen it. The graph is the receipt.
Day one, prepared. Paste this into ModuleX chat, or hit Use this workflow.
prepare everything a new joiner needs on day one: read the role and start date; build the checklist for that role from your template; create the tasks with owners and due dates; notify the owners in one message. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Prepare everything a new joiner needs on day one. A per-role onboarding checklist with real owners and dates, created before the start date.
- notion · create_page
- slack · post_message
A per-role onboarding checklist with real owners and dates, created before the start date.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Brief yourself on a candidate before the callA brief covering the role, the application, and what earlier rounds already established. Built for an interviewer who opens the CV two minutes before the interview.
Prepare an offer and send it for signatureAn offer letter produced from the approved details, checked by a person, then sent for signature. Built for whoever assembles offer letters from a template and hopes the numbers are right.- Request the access a new joiner needs, with a person approvingAn access request with an explicit approver and a written record of the decision. Built for an IT lead who grants access by message and remembers it later, if at all.
About this use case.
No. That is the separate access workflow, and it keeps a person in the loop.