Skip to main content

Automate change request workflow: Monday.com to Jira with Slack & Sheets

Workflow preview

Workflow preview
100%
Automate change request workflow: Monday.com to Jira with Slack & Sheets preview
Open on n8n.io

Important notice

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

1. Workflow Overview

Description Streamline IT and operations change management by automating approval routing, Jira issue creation, audit logging, and real time Slack alerts. This workflow ensures faster reviews, t...

Best for

  • Project Management automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.mondaycom, n8n-nodes-base.set, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.jira, n8n-nodes-base.googlesheets

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Automate change request workflow: Monday.com to Jira with Slack & Sheets
Workflow name
Automate change request workflow: Monday.com to Jira with Slack & Sheets

📊 Description

Streamline IT and operations change management by automating approval routing, Jira issue creation, audit logging, and real-time Slack alerts. This workflow ensures faster reviews, traceable approvals, and transparent communication across systems. 🚀💼

What This Template Does

  • Step 1: Triggers automatically every weekday at 3:00 AM to fetch new or updated change requests from Monday.com. ⏰
  • Step 2: Extracts key fields (request name, component, risk level, approvers, and description) for structured processing. 🧩
  • Step 3: Routes each request based on its current status — Pending, Approved, or Rejected. 🔀
  • Step 4: Sends Slack alerts for pending approvals with detailed context for quick action. 💬
  • Step 5: Creates Jira tickets for approved requests, ensuring smooth implementation tracking. 🎫
  • Step 6: Logs all approved requests to Google Sheets for compliance and audit purposes. 📊
  • Step 7: Sends confirmation emails to requesters with Jira ticket details via Gmail. 📧
  • Step 8: Automatically creates resubmission items in Monday.com for rejected requests. 🔁

Key Benefits

✅ Eliminates manual approval routing between tools ✅ Centralizes audit trails and implementation data ✅ Accelerates change management turnaround ✅ Provides real-time alerts to approvers and teams ✅ Ensures compliance with automated record-keeping

Features

  • Automated daily trigger (Mon–Fri, 3 AM)
  • Monday.com integration for request intake
  • Conditional branching by status (Pending, Approved, Rejected)
  • Jira issue creation for approved requests
  • Slack notifications for pending and approved updates
  • Google Sheets logging for audit tracking
  • Gmail email confirmations for requesters
  • Automatic resubmission handling for rejected requests

Requirements

  • Monday.com API credentials with board access
  • Jira API credentials with project permissions
  • Google Sheets OAuth2 credentials
  • Slack Bot token with chat:write permissions
  • Gmail OAuth2 credentials for email automation

Target Audience

  • IT & DevOps teams managing structured change approvals
  • Project management teams tracking implementation requests
  • Organizations seeking automated risk-based change routing
  • Managers needing centralized logs and instant Slack alerts

Step-by-Step Setup Instructions

  • Connect your Monday.com account and replace YOUR_BOARD_ID and groupId.
  • Configure Jira credentials and set the target project for new tickets.
  • Link your Google Sheets document and replace YOUR_SHEET_ID and YOUR_SHEET_GID.
  • Add Slack credentials and update YOUR_CHANNEL_ID for notifications.
  • Set up Gmail OAuth2 for sending confirmation emails.
  • Adjust the cron expression (0 3 * * 1-5) if needed to match your timezone.
  • Run the workflow manually once to test end-to-end connectivity.
  • Enable for scheduled automation and enjoy a fully managed approval process. ✅

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 - Workflow Overview

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

Block 2 - Schedule Trigger

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

Block 3 - Note - Schedule

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

Block 4 - Fetch Change Requests

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

Block 5 - Note - Fetch

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

Block 6 - Extract Request Data

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

Block 7 - Note - Extract

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

Block 8 - Filter Pending Requests

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

Block 9 - Note - Status Route

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

Block 10 - Notify Pending Request

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

Block 11 - Note - Pending Slack

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

Block 12 - Filter Approved Requests

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

Block 13 - Note - Approved Route

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

Block 14 - Create Jira Ticket

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

Block 15 - Note - Jira

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

Block 16 - Log to Google Sheets

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.7

Block 17 - Note - Sheets

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

Block 18 - Notify Approval

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

Block 19 - Note - Approved Slack

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

Block 20 - Send Confirmation Email

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 21 - Note - Email

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

Block 22 - Filter Rejected Requests

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

Block 23 - Note - Rejected Route

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

Block 24 - Create Resubmission Item

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

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

3. Summary Table

Workflow Automate change request workflow: Monday.com to Jira with Slack & Sheets
Complexity advanced
Nodes 25
Categories Project Management
Author Rahul Joshi
Published 17 Oct 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/9825/9825.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 change request workflow: Monday.com to Jira with Slack & Sheets do?

Description Streamline IT and operations change management by automating approval routing, Jira issue creation, audit logging, and real time Slack alerts. This workflow ensures faster reviews, t...

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.