Notify Redmine project members in Slack about teammates’ approved Odoo leave

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

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

1. Workflow Overview

Who is this for? This workflow is designed for engineering teams, project managers, and IT operations who need consistent visibility into team availability across multiple projects. It’s perfect ...

Best for

Project Management automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.set, n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.noop, n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.splitinbatches, n8n-nodes-base.wait

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: Notify Redmine project members in Slack about teammates’ approved Odoo leave
Workflow name: Notify Redmine project members in Slack about teammates’ approved Odoo leave

📌Who is this for?

This workflow is designed for engineering teams, project managers, and IT operations who need consistent visibility into team availability across multiple projects. It’s perfect for organizations that use Odoo for leave management and Redmine for project collaboration, and want to ensure that everyone involved gets timely, automated Slack notifications whenever a team member will be absent the next day.

📌The problem

When team members go dark, everything grinds to a halt. You're stuck with:

Last-minute meeting reschedules (and frustrated stakeholders)
Tasks assigned to people who aren't there
No time to redistribute workload
Bottlenecks affecting multiple projects

📌How it works

Runs daily at 17:15 - Set it and forget it. Executes every afternoon, giving teams time to prepare.
Fetches Tomorrow's Approved Leaves from Odoo - Pulls all leave records with tomorrow's start date and "approved" status.
Maps Employee & Project Data - Grabs the employee's details and identifies every Redmine project they're assigned to.
Finds All Teammates on the Same Projects - Deduplicates across overlapping projects to avoid notification spam.
Sends Targeted Slack Notifications - Only notifies people who actually work with the absent member, plus optional manager alerts.

📌Quick setup

Before you start, you’ll need:

Odoo API key
Redmine API key
Slack Bot Token (or Incoming Webhook URL)
Subflows need to be created within a new flow; the main flow will call these subflows.

📌Results

What changes immediately:

Zero surprises - teams know absences 24 hours ahead
Workload rebalancing happens before the person goes off
Managers make proactive decisions, not reactive ones
No more wasted Slack messages to irrelevant people
This creates a more predictable and transparent workflow across your engineering and project teams.

📌Take it further

Ready to supercharge it? Add:

Auto-assign backup owners for critical tasks
Sync absences to Google Calendar/Outlook
Log notifications to a database for auditing
Conditional alerts (key roles, high-priority projects only)
Daily summary digest of all upcoming absences

📌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 - Step2: Set Variables

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 2 - Step 1: Schedule the trigger to run every weekday at 5:15 PM.

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

Block 3 - Step3: Get datetime

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

Block 4 - Step4: Get all user in Redmine6

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

Block 5 - Step5: Get a list of closed projects.

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

Block 6 - Step7: Get the list of members' leave records for tomorrow.

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

Block 7 - End

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

Block 8 - End1

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

Block 9 - Step1: When Executed by Another Workflow

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

Block 10 - Step3: Loop Over Items

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 11 - Step4: Get membership list of user in Redmine 6

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

Block 12 - Step2: Return redmine list ProjectID of user

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

Block 13 - Step5: Get redmine project Team MemberIds

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

Block 14 - Step6: Remove duplicate id

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

Block 15 - No Operation, do nothing

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

Block 16 - Step2: Loop Over Items

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 17 - Step3: Wait 1s

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

Block 18 - Step6: Get many users

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

Block 19 - Step8: Check if there is a record or not?

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

Block 20 - Step9: Handling and get user information in Odoo 18

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

Block 21 - Step10: Loop Over Items

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 22 - Step11: Get leave record information

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

Block 23 - Step12: Get name record

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

Block 24 - Step13: Get employee information in Odoo 18

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

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

3. Summary Table

Workflow	Notify Redmine project members in Slack about teammates’ approved Odoo leave
Complexity	advanced
Nodes	54
Categories	Project Management
Author	BHSoft
Published	30 Dec 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/12298/12298.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
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. 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.

Download workflow JSON Original n8n.io source Project Management workflows

Frequently asked questions

What does Notify Redmine project members in Slack about teammates’ approved Odoo leave do?

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 Project Management use case.

BHSoft

5 workflows

Nodes

n8n-nodes-base.set n8n-nodes-base.scheduletrigger n8n-nodes-base.code n8n-nodes-base.httprequest n8n-nodes-base.noop n8n-nodes-base.executeworkflowtrigger n8n-nodes-base.splitinbatches n8n-nodes-base.wait

Complexity

advanced

Published 30 Dec 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/12298/12298.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Tag stale ClickUp tasks and escalate overdue items with assignee comments

## Quick overview This workflow runs daily on a schedule and checks ClickUp tasks in one or more lists for inactivity based on the task’s date_updated field, automatically applying “stale” tags and escalating long-idle tasks by tagging them and posting an assignee comment. ## How it works 1. Runs every day at the configured hour using the schedule trigger. 2. Loads monitoring settings (statuses, tags, stale thresholds, and tag names) and fetches matching tasks from the selected ClickUp list(s), then merges and deduplicates them. 3. Skips tasks that already have the second-level stale tag (for example, stale:14). 4. For tasks without the first-level stale tag, checks the last updated timestamp and adds either the first-level stale tag (for example, stale:7) or the second-level stale tag if they already exceed the higher threshold. 5. For tasks that already have the first-level stale tag, checks whether enough time has passed since that tag was applied and, if so, removes the first-level tag and adds the second-level stale tag. 6. When a task is escalated to the second-level stale tag, posts a warning comment on the ClickUp task and assigns the comment to the task assignee (or the creator if no assignee exists). ## Setup 1. Add a ClickUp API credential (OAuth or API token) and select it on all ClickUp nodes. 2. In the ClickUp task search node(s), choose the list(s) you want to monitor and enable/configure the second list node if you want to pull tasks from multiple lists. 3. Update the monitoring settings (monitoredStatuses, monitoredTags, daysUntilFirstStaleTag, daysUntilSecondStaleTag, and the stale tag names) to match your ClickUp workspace conventions. 4. Adjust the schedule trigger time and, if needed, set the workflow timezone in n8n settings so the run time matches your local time. ## Requirements - A ClickUp account with API access - ClickUp credential configured in n8n - At least one ClickUp list to monitor ## Customization - Change thresholds — Edit `daysUntilFirstStaleTag` and `daysUntilSecondStaleTag` in `SetContext` to any number of days - Change tag names — Update `firstStaleTagName` / `secondStaleTagName` to match your ClickUp tag naming convention - Monitor different statuses — Edit `monitoredStatuses` and `monitoredTags` in `SetContext` (e.g. add `review`, `blocked`) - Add more lists — Duplicate `GetTaskFromList1`, update the List ID, enable the node, and connect its output to a new input port on `AppendListTasks` - Change schedule — Open `TriggerRegularly` and switch from daily to weekdays-only or any custom cron interval - Disable subtasks — Open each `GetTaskFromList` node and set `subtasks` to `false` in the Filters section

View

Summarize daily Slack standups with OpenAI, Notion, and Google Sheets

## Quick overview This workflow runs every weekday, pulls standup messages from a Slack channel, uses OpenAI to generate a structured daily digest, saves the digest to a Notion database, posts a summary back to Slack, and appends an audit entry to Google Sheets. ## How it works 1. Runs every weekday morning on a cron schedule. 2. Fetches the day’s recent messages from a specified Slack standup channel and filters out bot, subtype, and join/leave system messages. 3. Checks whether any standup messages remain and posts a Slack notice if none are found. 4. Formats the remaining Slack updates into a single structured prompt with date, team name, and message count. 5. Sends the formatted standup text to OpenAI (gpt-4.1-mini) to generate a JSON digest with summary, highlights, blockers, per-user updates, and mood. 6. Parses and enriches the AI output with metadata, creates a new page in a Notion database, posts the digest to a Slack summary channel, and appends a run record to a Google Sheets “Audit Log” sheet. ## Setup 1. Add a Slack OAuth2 credential and set the standup channel ID (history source) and the summary channel ID (digest destination). 2. Add an OpenAI credential and confirm the model selection (gpt-4.1-mini) is available in your account. 3. Add a Notion credential, create/select a target database, and replace `YOUR_NOTION_DATABASE_ID` (and ensure the database has the referenced properties: Date, Team, Message Count, Mood). 4. Add a Google Sheets Service Account credential, share the target spreadsheet with the service account email, and replace `YOUR_SHEET_ID` and the sheet name (“Audit Log”) if different. 5. Adjust the schedule cron expression (`0 9 * * 1-5`) to match your team’s standup timing and timezone expectations.

View

Sync check due dates from Google Sheets to Google Calendar with Telegram alerts

## Quick overview This workflow watches a Google Sheets check inventory list and creates or updates matching all-day events in Google Calendar, then posts a creation or update notice to a Telegram group. ## How it works 1. Polls Google Sheets every hour for any updates in the “Check Inventory” sheet. 2. Checks whether the updated row already contains a Google Calendar Event ID. 3. If the Event ID is empty, searches Google Calendar for an existing event whose text matches the check number and backfills the found Event ID to Google Sheets. 4. If no matching calendar event exists, creates an all-day Google Calendar event using the check date and details from the Google Sheets row, then writes the new Event ID back to the sheet. 5. If an Event ID exists, fetches the corresponding Google Calendar event and compares its date, summary, and description to the latest Google Sheets values. 6. When differences are detected, updates the Google Calendar event to match the sheet and sends a Telegram message summarizing the created or updated events. ## Setup 1. Connect credentials for Google Sheets (including Google Sheets Trigger), Google Calendar OAuth2, and a Telegram Bot API account. 2. Replace `YOUR_CHECK_INVENTORY_SHEET_ID` in all Google Sheets nodes and ensure the “Check Inventory” sheet contains the required columns (including “Check Number” and “Event ID”). 3. Set the target Google Calendar ID (for example `[email protected]` or a shared calendar ID) in the Google Calendar nodes. 4. Replace `YOUR_TELEGRAM_GROUP_CHAT_ID` in the Telegram nodes and edit the message text to use the correct @mentions for your team.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Notify Redmine project members in Slack about teammates’ approved Odoo leave

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

📌Who is this for?

📌The problem

📌How it works

📌Quick setup

📌Results

📌Take it further

📌Need help customizing?

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Step2: Set Variables

Block 2 - Step 1: Schedule the trigger to run every weekday at 5:15 PM.

Block 3 - Step3: Get datetime

Block 4 - Step4: Get all user in Redmine6

Block 5 - Step5: Get a list of closed projects.

Block 6 - Step7: Get the list of members' leave records for tomorrow.

Block 7 - End

Block 8 - End1

Block 9 - Step1: When Executed by Another Workflow

Block 10 - Step3: Loop Over Items

Block 11 - Step4: Get membership list of user in Redmine 6

Block 12 - Step2: Return redmine list ProjectID of user

Block 13 - Step5: Get redmine project Team MemberIds

Block 14 - Step6: Remove duplicate id

Block 15 - No Operation, do nothing

Block 16 - Step2: Loop Over Items

Block 17 - Step3: Wait 1s

Block 18 - Step6: Get many users

Block 19 - Step8: Check if there is a record or not?

Block 20 - Step9: Handling and get user information in Odoo 18

Block 21 - Step10: Loop Over Items

Block 22 - Step11: Get leave record information

Block 23 - Step12: Get name record

Block 24 - Step13: Get employee information in Odoo 18

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions