Skip to main content

Automate Odoo-triggered Redmine & GitLab account creation with Slack notifications

Workflow preview

Workflow preview
100%
Automate Odoo-triggered Redmine & GitLab account creation with Slack notifications preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Who is this for? HR teams, IT Operations, and System Administrators managing employee onboarding at scale. It’s perfect if you use Odoo 18 to trigger account requests and need Redmine + GitLab ac...

Best for

  • HR automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.webhook, n8n-nodes-base.respondtowebhook, n8n-nodes-base.wait, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.noop

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by BHSoft.

Original n8n.io source

1.1 Workflow description

Title
Automate Odoo-triggered Redmine & GitLab account creation with Slack notifications
Workflow name
Automate Odoo-triggered Redmine & GitLab account creation with Slack notifications

📌Who is this for?

HR teams, IT Operations, and System Administrators managing employee onboarding at scale. It’s perfect if you use Odoo 18 to trigger account requests and need Redmine + GitLab accounts created instantly and consistently.

📌The Problem

Manual account creation creates bottlenecks:

  • IT waits for HR notifications that often get missed or delayed.
  • Duplicate accounts pile up when no one checks existing data first.
  • Account creation timelines are inconsistent (sometimes correct, sometimes wrong).
  • Zero visibility into what succeeded or failed.

📌What It Does

Catches an employee account creation request from Odoo 18 → queries employee data → checks for existing accounts → creates only the accounts that are missing → notifies your team via Slack with the full status. Here's the flow in detail:

  1. Webhook trigger from Odoo 18 - automatically fires when your HR team marks an employee as needing Redmine, GitLab, or both.
  2. Fetch employee data from Odoo 18 - pulls email and account type requirements.
  3. Deduplicate requests - separates "needs both," "GitLab only," and "Redmine only" cases.
  4. Check for existing accounts - queries Redmine and GitLab to avoid duplicate creation attempts.
  5. Create accounts - uses Redmine and GitLab APIs to spin up accounts (only if they don't exist).
  6. Slack notification - sends a summary showing what was created, skipped, or failed- including error details if something went wrong.

📌Quick Setup

  • Generate a Webhook URL in n8n and configure Odoo 18 to call it during onboarding.
  • Add Redmine admin API key and GitLab admin access token.
  • Enable /users.json (Redmine) and /users (GitLab) endpoints.
  • Configure Slack webhook for notifications.
  • Test with sample data, then activate.

📌Results

  • Zero duplicates - the system checks before creating.
  • Full visibility - Slack reports every single attempt.
  • Instant delivery - new hires get accounts on day one.
  • Dramatically reduced IT workload.

📌Take It Further

  • Auto-assign projects in Redmine/GitLab post-creation.
  • Generate passwords or TOTP setup and email them to new hires.
  • Log everything to Google Sheets, Notion, or a database.
  • Handle multi-tenant setups if your Odoo manages multiple organizations.
  • Add provisioning for Slack, Google Workspace, VPN, or other systems.

📌Need help customizing?

Contact me for consulting and support: Linkedin / Website

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Step1: Odoo 18 called a webhook

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 2

Block 2 - Step2: Respond to Webhook

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1.2

Block 3 - Step 3: Wait 5s

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 4 - Step5: Handle get today

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 5 - Step 6: Check if there's a requirement to create a Redmine or GitLab account on Odoo 18.

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 6 - Step7: If total_count is not equal to 0 = true

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 7 - Step8: Get many users

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

Block 8 - End

Type / Role
n8n-nodes-base.noOp - noOp
Config choices
Version 1

Block 9 - Step 9: Find the record requesting both Redmine and Gitlab accounts on Odoo 18.

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 10 - Step10: If total_count is not equal to 0 = true

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 11 - Step 11.1: Find and extract the email from the request

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 12 - Step12.1: Get user info in RM6

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 13 - Step13.1: If total_count is not equal to 0 = true

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 14 - Step14.1: Get user information in Gitlab

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 15 - Step15.1: Check if there is a record = true

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 16 - Step16.1: Send a message to channel

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

Block 17 - Step 16.2: Create a new user in Gitlab

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 18 - Step 17.1: Send reset password

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 19 - Step 19.1: Send a message to the member via Slack once their Gitlab account has been created.

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

Block 20 - Step18.1: Convert to text

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 21 - Step20.1: Send a message to channel REPORT

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

Block 22 - Step 14.2: Create a new user in Redmine

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 23 - Step 15.2: Assign the user to a group in Redmine

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 24 - Step 16.3: Code

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Showing the first 24 of 60 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Automate Odoo-triggered Redmine & GitLab account creation with Slack notifications
Complexity advanced
Nodes 60
Categories HR
Author BHSoft
Published 23 Dec 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/12056/12056.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automate Odoo-triggered Redmine & GitLab account creation with Slack notifications do?

Who is this for? HR teams, IT Operations, and System Administrators managing employee onboarding at scale. It’s perfect if you use Odoo 18 to trigger account requests and need Redmine + GitLab ac...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your HR use case.