Manage employee offboarding with Google Workspace, Slack, HubSpot and Notion
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 13 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects HubSpot, Google Sheets, Gmail and Slack. It also calls slack.com and api.notion.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Parse Employee Payload (Code): runs custom JavaScript code
- Valid Offboarding Record (If): checks a condition and branches into true / false
- Enrich Offboarding Record (Edit Fields (Set)): sets 5 fields: offboardingId, riskLevel, revocationDeadline…
- Alert Invalid Record (Slack): uses Slack
- Suspend Google Workspace Account (HTTP Request): calls an HTTP API (PUT)
- Deactivate Slack User (HTTP Request): calls slack.com (POST)
- Find HubSpot Contact (HubSpot): search
- Log to Notion Offboarding DB (HTTP Request): calls api.notion.com (POST)
- Merge: merges the data from its input branches
- Log to Compliance Sheet (Google Sheets): append
…plus 2 more steps. See the full node list below.
Services it uses
HTTP calls to: slack.com, api.notion.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - HubSpot
n8n-nodes-base.hubspot - Merge
n8n-nodes-base.merge - Google Sheets
n8n-nodes-base.googleSheets - Gmail
n8n-nodes-base.gmail - Slack
n8n-nodes-base.slack
From the author
Quick Overview This workflow receives an HR offboarding webhook, validates and enriches the employee record, suspends the user in Google Workspace, deactivates the user in Slack, looks up the matching HubSpot contact, logs the event to Notion and Google…