Automated employee offboarding: lock Redmine & GitLab accounts using Odoo 18
📌 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 compli...
Template notes
📌 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 is messy and slow:
- HR flags ending contracts. - IT hunts down accounts manually (Redmine, GitLab, etc.). - Misses happen, risks linger.
This n8n workflow queries Odoo 18 daily, spots offboardees, and locks accounts automatically.
📌 What It Does
- Triggers daily (e.g., 5 PM weekdays). - Queries Odoo 18 for employees ending today. - Filters active users needing offboarding. - Checks & Locks Redmine accounts via API. - Checks & Revokes GitLab access via API. - Notifies via Slack/Teams/email with summary. - Handles Errors: Retries failures, logs issues.
📌 Quick setup
1. Odoo 18 API (read employee end dates/last shifts). 2. Redmine Admin API key. 3. GitLab Admin token (for locking users). 4. Slack/Teams webhook or SMTP for alerts. 5. Cron schedule (e.g., daily 5 PM weekdays, skip weekends).