Skip to main content

Orchestrate M365 employee onboarding with SharePoint, OneDrive, Teams, Outlook and Claude

Workflow preview

Workflow preview
100%
Orchestrate M365 employee onboarding with SharePoint, OneDrive, Teams, Outlook and Claude preview
Open on n8n.io

1. Workflow Overview

Stop managing onboarding as a checklist. Let automation handle the infrastructure so you can focus on the people. Manually provisioning a new hire's digital workspace is a recipe for human error an...

Best for

  • HR automation workflows
  • AI Chatbot automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.microsoftagent365trigger, n8n-nodes-base.code, n8n-nodes-base.microsoftsharepoint, n8n-nodes-base.microsoftonedrive, n8n-nodes-base.itemlists, n8n-nodes-base.merge, n8n-nodes-base.microsoftteams

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mychel Garzon.

Original n8n.io source

1.1 Workflow description

Title
Orchestrate M365 employee onboarding with SharePoint, OneDrive, Teams, Outlook and Claude
Workflow name
Orchestrate M365 employee onboarding with SharePoint, OneDrive, Teams, Outlook and Claude

Stop managing onboarding as a checklist. Let automation handle the infrastructure so you can focus on the people.

Manually provisioning a new hire's digital workspace is a recipe for human error and "Day 1" friction. This workflow orchestrates the entire Microsoft 365 onboarding stack in a single, parallel execution. It doesn't just run tasks; it verifies them, handles API failures gracefully, and reports a live status dashboard directly back to HR.

How it works

The workflow operates in four synchronized stages:

  1. Ingestion & Smart Parsing: The workflow triggers via Microsoft Agent 365 (Teams @mentions or Outlook emails). A JavaScript engine parses the unstructured HR request using flexible regex to extract the employee's name, role, department, and start date.
  2. True Parallel Execution: Once parsed, the data fans out into four independent branches:
  • SharePoint: Creates a structured entry in the HR Onboarding master list.
  • OneDrive: Provisions a personal root folder and automatically generates 5 templated sub-folders (Contracts, Equipment, Training, etc.).
  • Teams: Creates a private onboarding channel for the employee's cohort.
  • AI Communications: Leverages Claude 3.5 Sonnet to draft a warm, personalized welcome email based on the specific role and department, then sends it via Outlook.
  1. Fault-Tolerant Merging: The workflow uses a multi-stage Merge Cascade. Every node is configured with Continue on Fail logic. This means if one branch hits an API limit or error, it passes an error object forward rather than crashing the entire process.
  2. Verified Status Delivery: The final stage gathers all outputs, validates whether each task actually returned a success ID/URL, and generates a Microsoft Teams Adaptive Card. HR receives a clean summary with live links to provisioned assets and clear ❌ markers for any step that requires manual intervention.

Key Benefits

  • Zero-Hang Resilience: Built with "Continue on Fail" logic. If SharePoint is down, the employee still gets their welcome email and OneDrive folder.
  • Live Asset Verification: The final report doesn't just "hope" things worked; it checks for live IDs and URLs from the Microsoft Graph API before showing a green checkmark.
  • Parallel Performance: Provisioning happens concurrently. The total wait time is only as long as the slowest single task (usually the AI generation).
  • Global Error Handling: Includes a dedicated Error Trigger flow that catches catastrophic system crashes and alerts IT with a full stack trace and the name of the failed node.

Setup

  1. Credentials: Add credentials for Microsoft SharePoint, OneDrive, Teams, Outlook, and Anthropic (Claude).
  2. Environment Config: Open the Parse New Hire + Config node and replace the placeholder IDs with your specific SharePoint Site ID, List ID, and Teams Team ID.
  3. Entra ID Permissions: Ensure your registered Azure App has the necessary Graph API permissions (Sites.ReadWrite.All, Files.ReadWrite.All, Channel.Create, Mail.Send).
  4. Activate: Turn the workflow on and trigger it by @mentioning your Agent in Teams with new hire details.

Who this is for

  • IT Operations Teams looking to standardize M365 provisioning without expensive third-party SaaS.
  • HR Departments that want immediate, transparent feedback on onboarding progress.
  • Managed Service Providers (MSPs) providing automated "Hiring-as-a-Service" for their clients.

Required APIs & Credentials

  • Microsoft 365 Stack: SharePoint, OneDrive, Teams, Outlook.
  • AI Provider: Anthropic (Claude 3.5 Sonnet) or OpenAI (GPT-4o).

How to customise it

  • Add More Branches: Easily add nodes for Jira, Slack, or HRIS updates by fanning out from the Parser and adding them to the Merge Cascade.
  • Adjust Folder Templates: Modify the Build SubFolder Paths code node to match your company's specific folder structure.
  • Modify AI Tone: Change the System Message in the AI node to match your company's unique brand voice.
  • Custom Triggers: Swap the Agent 365 trigger for a Webhook (to connect to Workday/HiBob) or a Typeform trigger.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - README

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Microsoft Agent 365

Type / Role
@n8n/n8n-nodes-langchain.microsoftAgent365Trigger - microsoftAgent365Trigger
Config choices
Version 1.1

Block 3 - Parse New Hire + Config

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 4 - SharePoint: Create Onboarding Entry

Type / Role
n8n-nodes-base.microsoftSharePoint - microsoftSharePoint
Config choices
Version 1

Block 5 - OneDrive: Create Employee Folder

Type / Role
n8n-nodes-base.microsoftOneDrive - microsoftOneDrive
Config choices
Version 1

Block 6 - Build SubFolder Paths

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 7 - OneDrive: Create SubFolders

Type / Role
n8n-nodes-base.microsoftOneDrive - microsoftOneDrive
Config choices
Version 1

Block 8 - Limit SubFolders Array

Type / Role
n8n-nodes-base.itemLists - itemLists
Config choices
Version 3

Block 9 - Wait: SP & OneDrive

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 2.1

Block 10 - Teams: Create Onboarding Channel

Type / Role
n8n-nodes-base.microsoftTeams - microsoftTeams
Config choices
Version 2

Block 11 - AI: Generate Welcome Email

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 1.7

Block 12 - Claude Sonnet 4

Type / Role
@n8n/n8n-nodes-langchain.lmChatAnthropic - lmChatAnthropic
Config choices
Version 1.2

Block 13 - Outlook: Send Welcome Email

Type / Role
n8n-nodes-base.microsoftOutlook - microsoftOutlook
Config choices
Version 2

Block 14 - Wait: Teams & Email

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 2.1

Block 15 - Wait: All Branches

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 2.1

Block 16 - Build HR Summary Card

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 17 - Teams: Post HR Summary Card

Type / Role
n8n-nodes-base.microsoftTeams - microsoftTeams
Config choices
Version 2

Block 18 - Error Trigger

Type / Role
n8n-nodes-base.errorTrigger - errorTrigger
Config choices
Version 1

Block 19 - Build Error Alert Card

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 20 - Teams: Post Error Alert

Type / Role
n8n-nodes-base.microsoftTeams - microsoftTeams
Config choices
Version 2

Block 21 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 25 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Orchestrate M365 employee onboarding with SharePoint, OneDrive, Teams, Outlook and Claude
Complexity advanced
Nodes 25
Categories HR, AI Chatbot
Author Mychel Garzon
Published 11 May 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15628/15628.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Orchestrate M365 employee onboarding with SharePoint, OneDrive, Teams, Outlook and Claude do?

Stop managing onboarding as a checklist. Let automation handle the infrastructure so you can focus on the people. Manually provisioning a new hire's digital workspace is a recipe for human error an...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your HR, AI Chatbot use case.