Manage HR offboarding and archival with Odoo, Google Calendar, Gmail, and Slack

by Anir Agram ✓ · 31 views · created 2026-08-17 · HR

What this workflow does

This workflow has 39 nodes and runs when an HTTP POST request hits its webhook URL (plus 1 other trigger). Along the way it connects Odoo, Google Calendar, Gmail and Slack.

How it runs

Trigger: When an HTTP POST request hits its webhook URL (plus 1 other trigger).

1. Validate Offboarding Input (Edit Fields (Set)): sets 7 fields: valid, validationError, employeeName…
2. Odoo: get many (custom)
3. Input Valid? (If): checks a condition and branches into true / false
4. Odoo: update (custom)
5. Has Employee Email? (If): checks a condition and branches into true / false
6. Respond 400 Invalid Input (Respond to Webhook): sends the response back to the webhook caller
7. Odoo: get many (custom)
8. Odoo: get many (custom)
9. Respond 502 Employee Lookup Failed (Respond to Webhook): sends the response back to the webhook caller
10. Employee Found? (If): checks a condition and branches into true / false

…plus 19 more steps. See the full node list below.

Services it uses

OdooGoogle CalendarGmailSlack

Before you upgrade to n8n 3.0

Nodes used (11)

• Webhookn8n-nodes-base.webhook
• Edit Fields (Set)n8n-nodes-base.set
• Ifn8n-nodes-base.if
• Respond to Webhookn8n-nodes-base.respondToWebhook
• Odoon8n-nodes-base.odoo
• No Operation, do nothingn8n-nodes-base.noOp
• Google Calendarn8n-nodes-base.googleCalendar
• Gmailn8n-nodes-base.gmail
• Slackn8n-nodes-base.slack
• Split Outn8n-nodes-base.splitOut
• Schedule Triggern8n-nodes-base.scheduleTrigger

From the author

Quick overview This workflow accepts HR offboarding requests via webhook, updates the employee’s departure details in Odoo, then schedules an exit interview in Google Calendar, sends a confirmation email with Gmail, notifies Slack channels, and creates Odoo…

View the original on n8n.io → Check your own copy