Nembl
Examples
Employee Onboarding

Example: Employee Onboarding

Onboard a new hire by triggering parallel tracks for HR paperwork, IT setup, manager intro, and equipment delivery — each owned by a different team, all completing independently before the new hire starts.

You'll build: Service Employee Onboarding → Offering New Hire → Form (8 fields) → Workflow (Start → 4 parallel branches → Join → End). Time: ~30 min.

The shape

                        ┌─→ HR Paperwork ────────┐
                        │                         │
                        ├─→ IT Account Setup ────┤
Submit New Hire ──Fork──┤                         ├──Join── Welcome Email ── ✅ Complete
                        ├─→ Equipment Delivery ──┤
                        │                         │
                        └─→ Manager Intro ───────┘

The Parallel phase is the key — it forks into N branches and joins when all complete.

What you'll need

  • Company account
  • 1 person playing HR
  • 1 person playing IT
  • 1 person playing Manager (the new hire's direct manager)
  • 1 person playing Operations (laptop / desk)

You can play all four roles yourself if testing — just sign in with different accounts (or use multiple browser profiles).

Step 1 — Create the Service & Offering

Service

Admin → Services → New Service.

  • Name: Employee Onboarding
  • Description: Coordinates everything needed to get a new hire productive on day 1

Offering

In the new Service → Offerings → New Offering.

  • Name: New Hire
  • Description: Submit when an offer has been signed

Step 2 — Build the Form

FieldTypeRequiredNotes
New Hire NameText✓Full legal name
Personal EmailEmail✓For initial onboarding emails
Start DateDate✓First day on the job
DepartmentSelect✓Engineering, Sales, Marketing, Ops, Finance
Reports To (Manager)User picker✓Must be an existing Nembl user
Office LocationSelect✓Remote, HQ, NYC, SF, Other
Job TitleText✓
Equipment NotesTextarea–"Needs dual monitor", "Standing desk", etc.

Step 3 — Build the Workflow

New Workflow

Admin → Workflows → New Workflow → name New Hire Onboarding.

Drag phases

From the palette:

  1. Start
  2. Parallel — name: Onboarding Tracks (this is the fork)
  3. Four Process phases (these will be the four branches):
    • HR Paperwork
    • IT Account Setup
    • Equipment Delivery
    • Manager Intro
  4. The Parallel node has a built-in Join — connect each of the 4 process phases back to it
  5. Process — Welcome Email (auto-fired after join)
  6. End — Onboarding Complete

Connect

  • Start → Onboarding Tracks (Fork)
  • Fork branches: → HR Paperwork, → IT Account Setup, → Equipment Delivery, → Manager Intro
  • All four phases → Join (the same Parallel node)
  • Join → Welcome Email → Onboarding Complete

Configure each parallel branch

  • HR Paperwork: assign Responsible = HR Team. Add task templates: "I-9 verified", "W-4 signed", "Benefits enrolled".
  • IT Account Setup: assign Responsible = IT Team. Task templates: "Email account created", "SSO group added", "VPN access verified".
  • Equipment Delivery: assign Responsible = Operations Team. Task templates: "Laptop ordered", "Laptop shipped", "Desk assigned".
  • Manager Intro: assign Responsible = Manager (resolved from the form's Reports To field via variable interpolation).

Configure the Welcome Email phase as automated

  • Execution Mode: Automated
  • Automation Type: Webhook Callout (your email provider's API, or an internal "send-email" service)
  • Body Template uses {{newHireName}}, {{personalEmail}}, {{startDate}}, etc.

Publish the Workflow

Step 4 — Link, Publish, Test

Link the Workflow to the New Hire offering

Publish the Offering, then the Service

Submit a test as anyone

Open the Service Catalog → Employee Onboarding → New Hire → fill the form → Submit.

Watch all four branches activate simultaneously

The instance shows ACTIVE in the Workflow viewer with all four parallel phases highlighted. Each assigned team (HR, IT, Ops, Manager) sees the request in their My Workflows.

Complete each branch independently

Sign in as each role. Tick off task templates. Mark the phase complete. The instance waits at Join until all four finish.

Watch Welcome Email fire automatically

When the slowest branch completes, Join releases, Welcome Email fires its webhook, and Onboarding Complete is reached.

What you can adapt

  • Conditional branches: Marketing hires get an extra "Brand training" branch; Engineers get "GitHub access provisioning". Add a Decision phase before the Parallel that picks which sub-branches to fork.
  • Time-bound phases: Equipment Delivery should complete 7 days before Start Date. Add a Timer phase that fires a reminder if it hasn't.
  • Status visibility for the new hire: send the new hire a status link (with their personal email) showing which onboarding tracks are complete.
  • Dependencies between branches: IT can't create accounts until HR Paperwork's "I-9 verified" task is done. Add a dependsOn constraint on the IT Account Setup phase, or restructure with a sequential phase between branches.

Related

IT Support — New LaptopVendor Approval