Skip to main content

Monitor API rate limits and alert with Slack, Gmail and Google Sheets

Workflow preview

Workflow preview
100%
Monitor API rate limits and alert with Slack, Gmail and Google Sheets preview
Open on n8n.io

1. Workflow Overview

Quick Overview This workflow runs on a recurring schedule to check an API’s rate limit status via HTTP, calculates usage and severity, sends Slack and Gmail alerts when thresholds are breached, and...

Best for

  • DevOps automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.set, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.gmail, 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 Avkash Kakdiya.

Original n8n.io source

1.1 Workflow description

Title
Monitor API rate limits and alert with Slack, Gmail and Google Sheets
Workflow name
Monitor API rate limits and alert with Slack, Gmail and Google Sheets

Quick Overview

This workflow runs on a recurring schedule to check an API’s rate-limit status via HTTP, calculates usage and severity, sends Slack and Gmail alerts when thresholds are breached, and logs each check to Google Sheets for tracking.

How it works

  1. Runs on a schedule trigger at a fixed interval.
  2. Calls the API rate-limit status endpoint via an HTTP request using a bearer token header.
  3. Parses the response to normalize rate-limit fields and calculates used quota, remaining quota, usage percentage, and reset time.
  4. Assigns a severity level (Normal, Warning, High, Critical) and flags whether usage is at or above the alert threshold.
  5. When the threshold is breached, posts either a critical or warning message to the configured Slack channel based on severity.
  6. Emails the on-call address via Gmail and appends the check results to a Google Sheets “Log” sheet.

Setup

  1. Update the HTTP request URL and replace the Authorization header value with your API’s rate-limit endpoint and bearer token (or configure an n8n HTTP Header Auth credential).
  2. Connect your Slack credentials and set the target channel ID(s) used for the alerts.
  3. Connect your Gmail credentials and set the on-call recipient email address.
  4. Connect your Google Sheets service account credentials and set the spreadsheet document ID and sheet name used for logging.
  5. Adjust the schedule interval and, if needed, tweak the severity and breach thresholds (currently alerts at 80% and marks critical at 95%).

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 - Schedule Check

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

Block 2 - Fetch Rate Limit Status

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

Block 3 - Parse Usage Data

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

Block 4 - Score Severity

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

Block 5 - Threshold Breached

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

Block 6 - Is Critical

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

Block 7 - Slack Critical Alert

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

Block 8 - Slack Warning Alert

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

Block 9 - Email On-Call

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

Block 10 - Log to Sheets

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

Block 11 - Sticky Note

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

Block 12 - Sticky Note1

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

Block 13 - Sticky Note2

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

Block 14 - Sticky Note3

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

3. Summary Table

Workflow Monitor API rate limits and alert with Slack, Gmail and Google Sheets
Complexity intermediate
Nodes 14
Categories DevOps
Author Avkash Kakdiya
Published 11 Jun 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/16269/16269.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 API rate limits and alert with Slack, Gmail and Google Sheets do?

Quick Overview This workflow runs on a recurring schedule to check an API’s rate limit status via HTTP, calculates usage and severity, sends Slack and Gmail alerts when thresholds are breached, and...

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 DevOps use case.