Skip to main content

Easy Redmine and Microsoft Teams workflow template

Workflow preview

Workflow preview
100%
Easy Redmine and Microsoft Teams workflow template preview
Open on n8n.io

Important notice

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

1. Workflow Overview

This workflow contains community nodes that are only compatible with the self hosted version of n8n. Daily Easy Redmine Task Digest to Microsoft Teams Channel Overview This workflow automatically c...

Best for

  • Project Management automation workflows
  • Multimodal AI automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, @easysoftware/n8n-nodes-easy-redmine.easyredmine, n8n-nodes-base.splitout, n8n-nodes-base.set, n8n-nodes-base.microsoftteams, n8n-nodes-base.stickynote, n8n-nodes-base.splitinbatches

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Easy Redmine and Microsoft Teams workflow template
Workflow name
Easy Redmine and Microsoft Teams workflow template

This workflow contains community nodes that are only compatible with the self-hosted version of n8n.

Daily Easy Redmine Task Digest to Microsoft Teams Channel

Overview

This workflow automatically collects newly assigned Easy Redmine tasks for a specific team and sends a concise, formatted summary to a Microsoft Teams channel each weekday morning. It’s designed to keep your team updated without manual copy-pasting or sifting through outdated information.

Perfect for project managers, team leads, or consultants using Easy Redmine, this automation ensures that no high-priority or recent tasks are missed, improving transparency and daily planning.


How it works

  • Daily Trigger (8:30 AM on workdays): Initiates the automation at a fixed schedule.
  • Get Issues by Query: Easy Redmine node retrieves all issues matching a saved filter
  • Split Out Issues: Breaks the received array of tasks into individual items for separate processing.
  • Keep Relevant Fields & Add Link: Filters to essential data (ID, author, subject, description) and creates a clickable issue link using URL concatenation.
  • Run for Each Task: Iterates over tasks to process and send individually.
  • Message into Team Channel: Uses the Microsoft Teams node to post formatted HTML content into the chosen channel.

How to Use

  1. Import the workflow into your n8n instance.
  2. Set up Easy Redmine credentials with API access.
  • Add or configure your Easy Redmine API credential.
  1. Set up Microsoft Teams credentials with API access.
  • Add or configure your Microsoft Teams OAuth2 API credential.
  1. Adjust the saved filter in Easy Redmine to match your team’s needs.
  2. Update Teams channel or chat selection in the final node.
  3. Modify the scheduled trigger time if desired.
  4. Test with a smaller query before enabling full automation.

Example Use Cases

  • Daily Team Stand-ups: Provide an automated pre-meeting digest of all new or updated tasks.
  • Consulting Project Management: Keep consultants aware of the latest client requests.
  • Support Teams: Quickly distribute newly assigned tickets without manual coordination.

Requirements

  • Easy Redmine account with API access and permission to use saved filters.
  • Microsoft Teams account with permission to post to the target channel.

Customization

  • Adjust the saved filter in Easy Redmine to target different teams, statuses, or update windows.
  • Change the schedule to match your meeting cadence (daily, twice daily, etc.).
  • Alter the HTML formatting for better readability or company branding.
  • Add more fields from Easy Redmine (priority, due date, etc.) for richer summaries.

Workflow Improvement Suggestions:

  • Rename generic nodes like “manual” and “get-manyissues” to descriptive titles (e.g., “Filter Fields & Build Link”).
  • Remove any real names or project-specific data before publishing.
  • Consider adding error handling if Easy Redmine or Teams API calls fail.

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 - Daily Trigger (8:30 work-days)

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

Block 2 - Get Issues by Query

Type / Role
@easysoftware/n8n-nodes-easy-redmine.easyRedmine - easyRedmine
Config choices
Version 1

Block 3 - Split Out Issues

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

Block 4 - Keep Relevant Fields & Add Link

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

Block 5 - Message into Team Channel

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

Block 6 - Sticky Note2

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

Block 7 - Sticky Note3

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

Block 8 - Sticky Note4

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

Block 9 - Run for Each Task

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

3. Summary Table

Workflow Easy Redmine and Microsoft Teams workflow template
Complexity intermediate
Nodes 9
Categories Project Management, Multimodal AI
Author Easy8.ai
Published 12 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/7293/7293.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 Easy Redmine and Microsoft Teams workflow template do?

This workflow contains community nodes that are only compatible with the self hosted version of n8n. Daily Easy Redmine Task Digest to Microsoft Teams Channel Overview This workflow automatically c...

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, Multimodal AI use case.