👥 Automated employee offboarding: lock Redmine & GitLab accounts using Odoo 18
⚡ 65 views · 👥 HR & Recruitment
Description
📌 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
- Odoo 18 API (read employee end dates/last shifts).
- Redmine Admin API key.
- GitLab Admin token (for locking users).
- Slack/Teams webhook or SMTP for alerts.
- Cron schedule (e.g., daily 5 PM weekdays, skip weekends).
📌 Customize It
- Add Systems: Jira, Confluence, LDAP—easy toggles.
- Notification: Full reports or alerts-only.
- Error Rules: Retries, escalations.
- Audit Logs: Save to DB, S3, Sheets, or dashboard.
📌 Results
100% automated: Accounts locked on exit day. No orphans, no workload, full compliance.
📌 Workflow in Action
- Schedule trigger fires.
- Pull Odoo offboardees.
- API checks & disables Redmine/GitLab.
- Logs + summary notification.
🔗 Nodes Used
HTTP Request, Schedule Trigger
📥 Import
Download workflow.json and import into n8n:
Workflow menu → Import from File