Automated employee offboarding: lock Redmine & GitLab accounts using Odoo 18
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 31 nodes and runs on a schedule (every week at ={{ 17 }}:00). It uses only n8n's built-in nodes.
How it runs
Trigger: On a schedule (every week at ={{ 17 }}:00).
- Step2: Handle get today (Code): runs custom JavaScript code
- Step3: Set Variables (Edit Fields (Set)): sets or maps fields
- Step4: Get Employee Resignation in Odoo (HTTP Request): calls an HTTP API (POST)
- Step5: If total_count is not equal to 0 = true (If): checks a condition and branches into true / false
- Step6: Check if there is a valid record. (Code): runs custom JavaScript code
- Step7: If hasRecords is empty==> true (If): checks a condition and branches into true / false
- Step8: Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
- Step9: Get employee information in Odoo (HTTP Request): calls an HTTP API (POST)
- Step10: Handle work_email (Code): runs custom JavaScript code
- Step11: Get user info in RM (HTTP Request): calls an HTTP API
…plus 18 more steps. See the full node list below.
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 (7)
- No Operation, do nothing
n8n-nodes-base.noOp - Code
n8n-nodes-base.code - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - HTTP Request
n8n-nodes-base.httpRequest
From the author
📌 Who is This For? IT Ops, HR, and Security teams automating employee offboarding. Zero manual work: Disable access to Redmine, GitLab, and more- right after their last day. Boost security, cut risks, and stay compliant. 📌 The Problem It Solves Offboarding…