Skip to main content

Monitor candidate email SLA breaches with Gmail and send Slack alerts

Workflow preview

Workflow preview
100%
Monitor candidate email SLA breaches with Gmail and send Slack alerts preview
Open on n8n.io

1. Workflow Overview

Gmail Candidate Email SLA Monitoring & Slack Alert Workflow This workflow automatically monitors candidate emails received in the last 24 hours and checks whether a recruiter has replied within the...

Best for

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

Tools used

n8n-nodes-base.gmail, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.merge, n8n-nodes-base.scheduletrigger, n8n-nodes-base.stickynote

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Monitor candidate email SLA breaches with Gmail and send Slack alerts
Workflow name
Monitor candidate email SLA breaches with Gmail and send Slack alerts

Gmail Candidate Email SLA Monitoring & Slack Alert Workflow

This workflow automatically monitors candidate emails received in the last 24 hours and checks whether a recruiter has replied within the same thread. If no reply is found, it flags it as an SLA breach and sends a Slack alert to an available team member (active if possible, otherwise random). This helps ensure timely communication with candidates.

Quick Implementation Steps

  1. Login to your n8n account.
  2. Set up the Scheduler node (e.g., every 5 minutes or as preferred).
  3. Connect your Gmail account and fetch emails from the last 24 hours.
  4. Filter candidate emails using sender domain and label/category.
  5. Use thread analysis to detect if a reply exists.
  6. Connect Slack and fetch channel members.
  7. Check presence and select an active (or random) user.
  8. Send alert message via Slack using user ID.
  9. Activate the workflow.

What It Does

This workflow continuously monitors incoming emails from candidates and ensures that no message goes unanswered. It focuses specifically on emails received within the last 24 hours and identifies conversations that have not received a reply from the recruiter.

Once emails are fetched, the workflow filters relevant candidate communications based on sender domain and label/category. It then retrieves the full email thread and analyzes whether any reply has been sent from the recruiter’s side. If no reply exists in the thread, it is marked as an SLA breach.

To ensure quick action, the workflow integrates with Slack. It checks the availability of team members and intelligently selects an active user. If no one is active, it assigns the alert to a random team member, ensuring accountability and timely follow-up.

Who It's For

  • Recruitment teams handling candidate communication
  • HR departments managing high volumes of emails
  • Hiring managers who want to improve response times
  • Operations teams focused on SLA compliance
  • Startups and agencies managing multiple candidate pipelines

Requirements

To use this workflow, you need:

  • An active n8n account
  • Gmail account connected via n8n
  • Slack workspace access
  • Slack API credentials configured in n8n
  • A Slack channel with team members
  • Basic understanding of email threads and Slack user IDs

How It Works & Set Up

Setup Instructions

  1. Scheduler Configuration
  • Set the trigger interval (default: every 5 minutes)
  • Users can adjust this based on their needs
  1. Gmail Integration
  • Connect your Gmail account
  • Use "Get Many Messages" node
  • Configure to fetch emails from the last 24 hours
  1. Filter Candidate Emails
  • Apply filtering logic using:
  • Sender domain
  • Email label/category
  1. Thread Retrieval
  • Use thread ID to fetch full conversation
  • Ensure all messages in the thread are available
  1. Reply Detection
  • Analyze messages in the thread
  • Check if any message has SENT label
  • If yes → mark hasReplied = true
  • If no → mark as SLA breach
  1. Slack Integration
  • Fetch members from selected channel
  • Retrieve presence status for each member
  1. User Selection Logic
  • If any user is active → select active user
  • Else → randomly select a user
  1. Send Slack Alert
  • Send message using selected user ID
  • Include candidate email and thread details
  1. Activate Workflow
  • Test all nodes
  • Enable workflow for automation

How To Customize Nodes

  • Scheduler Node
  • Adjust frequency (e.g., every 10 mins, hourly)
  • Gmail Node
  • Modify time window (e.g., last 48 hours)
  • Add more filters if needed
  • Filter Logic
  • Customize based on:
  • Domains
  • Keywords
  • Labels
  • Reply Detection
  • Extend logic to include time-based SLA if needed
  • Slack Message Node
  • Customize alert message format
  • Add urgency indicators or emojis
  • User Selection Logic
  • Change selection strategy (e.g., round-robin instead of random)

Add-ons (Enhancements)

  • Add SLA time tracking (e.g., alert after 6/12/24 hours)
  • Send escalation alerts if still unresolved
  • Log SLA breaches in Google Sheets or database
  • Add email auto-reply for acknowledgment
  • Integrate with CRM systems
  • Add priority tagging (high-value candidates)

Use Case Examples

  • Ensuring recruiters respond to candidates within 24 hours
  • Monitoring missed emails in high-volume hiring campaigns
  • Alerting teams about unattended job applications
  • Improving candidate experience through faster replies
  • Managing SLA compliance for recruitment agencies

There can be many more use cases depending on how you extend and customize this workflow.

Troubleshooting Guide

Issue Possible Cause Solution
No emails fetched Gmail node not configured correctly Check credentials and filters
Incorrect email filtering Wrong domain/label logic Update filter conditions
Replies not detected Thread parsing issue Verify SENT label logic
No Slack message sent Invalid user ID or Slack config Check Slack credentials
All users shown as away Slack presence limitation Verify Slack presence permissions
Random user not selected Logic error in code node Validate selection script
Workflow not triggering Scheduler disabled Enable and verify schedule

Need Help?

If you need help setting up this workflow, customizing nodes or adding advanced features, our n8n automation team at WeblineIndia is here to assist you.

We can help you:

  • Customize SLA logic
  • Integrate additional tools (CRM, databases, etc.)
  • Build advanced automation workflows
  • Optimize your recruitment processes

Feel free to reach out to WeblineIndia for expert guidance or to build similar automation solutions tailored to your business needs.

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 - Fetch Recent Emails

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

Block 2 - Filter Candidate Emails Only

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

Block 3 - Get Thread Details

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

Block 4 - Reply Detection

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

Block 5 - Check – Has Recruiter Replied?

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

Block 6 - Get Channel Members

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

Block 7 - Get User Presence

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

Block 8 - Merge Presence Data

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 9 - Select – Active/Random User

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

Block 10 - Merge Assign User Data

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 11 - Send SLA Alert

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

Block 12 - Scheduler – Every 5 min

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

Block 13 - Sticky Note

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

Block 14 - Sticky Note1

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

Block 15 - Sticky Note2

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

Block 16 - Sticky Note3

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

Block 17 - Sticky Note4

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

3. Summary Table

Workflow Monitor candidate email SLA breaches with Gmail and send Slack alerts
Complexity advanced
Nodes 17
Categories HR
Author WeblineIndia
Published 22 Apr 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15234/15234.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 Monitor candidate email SLA breaches with Gmail and send Slack alerts do?

Gmail Candidate Email SLA Monitoring & Slack Alert Workflow This workflow automatically monitors candidate emails received in the last 24 hours and checks whether a recruiter has replied within the...

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.