Skip to main content

Send multi-stage SaaS renewal alerts from Google Sheets to Slack

Workflow preview

Workflow preview
100%
Send multi-stage SaaS renewal alerts from Google Sheets to Slack preview
Open on n8n.io

1. Workflow Overview

Your automated SaaS contract renewal monitor that sends multi stage Slack alerts 45, 30, 14, and 7 days before each contract expires. Stop missing renewal deadlines and overpaying on auto renewals....

Best for

  • Document Extraction automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.slack, n8n-nodes-base.errortrigger, n8n-nodes-base.googlesheets, n8n-nodes-base.if, n8n-nodes-base.code, n8n-nodes-base.scheduletrigger

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Send multi-stage SaaS renewal alerts from Google Sheets to Slack
Workflow name
Send multi-stage SaaS renewal alerts from Google Sheets to Slack

Your automated SaaS contract renewal monitor that sends multi-stage Slack alerts 45, 30, 14, and 7 days before each contract expires.

Stop missing renewal deadlines and overpaying on auto-renewals. This workflow monitors your contract calendar in Google Sheets, sends progressive Slack notifications with manual research checklists, and tracks alert history to prevent duplicate notifications. You manage the vendors; it manages the reminders.

This is not a generic reminder bot. It is a production-ready procurement intelligence system designed to give finance and operations teams the advance notice needed to research alternatives, negotiate better terms, and avoid costly auto-renewals.


How the workflow works

The workflow executes in four stages:

1. TRIGGER & SCHEDULE

The workflow runs daily at 9:00 AM using a cron trigger (0 9 * * *). The schedule runs in your configured timezone (default: UTC). A single daily check scans your entire contract portfolio and identifies which renewals are entering their alert windows.

2. LOAD & VALIDATE

Using Google Sheets' native integration, the workflow reads your contract tracking spreadsheet (columns A-F: Contract Name, Vendor Name, Renewal Date, Annual Cost, Pricing URL, Status). A validation engine checks each row for:

  • Valid contract names (non-empty)
  • Proper ISO dates (YYYY-MM-DD format)
  • Positive costs (allows zero for free-tier contracts)
  • Valid HTTP/HTTPS URLs
  • Active status (skips Cancelled/Renewed contracts)

Invalid rows are silently filtered out to prevent workflow crashes from bad data.

3. MULTI-STAGE ALERT LOGIC

A Brain node calculates days-until-renewal using native JavaScript Date objects (no external dependencies). For each contract, it checks four alert windows:

  • 45 days out: 🟑 REMINDER β€” "Research Phase: Look for alternatives"
  • 30 days out: 🟠 ATTENTION β€” "Quote Phase: Get competitor pricing"
  • 14 days out: πŸ”΄ URGENT β€” "Decision Phase: Finalize negotiation"
  • 7 days out: 🚨 FINAL NOTICE β€” "Action Phase: Confirm or cancel"

Each window spans 5 days (daysUntil <= alert.days && daysUntil > alert.days - 5) to catch missed runs from weekends or server outages. The workflow only fires once per stage by checking if the Status column already contains that stage marker (e.g., alerted_45d).

Deduplication: A Set-based tracker prevents duplicate alerts if the same contract appears multiple times in your sheet.

4. NOTIFICATION & TRACKING

Success Path: When a contract enters an alert window:

  1. Slack receives a formatted message with:
  • Urgency indicator (🟑/🟠/πŸ”΄/🚨)
  • Contract details (vendor, renewal date, annual cost)
  • ROI calculation (potential savings: 15-25% of contract value)
  • Manual research checklist (vendor pricing URL, competitor search terms)
  • Upgrade CTA with UTM tracking (utm_campaign = contract slug, utm_content = alert stage)
  1. Google Sheets Status column updates to append the alert stage: "Active, alerted_45d"
  2. Next day, the workflow knows this contract was already alerted and won't send duplicate messages

Empty Path: When no contracts are in alert windows, a daily summary message confirms the workflow ran successfully: "βœ… Daily check complete. Reviewed 12 contracts. No renewals in alert windows."

Error Path: If Google Sheets/Slack APIs fail, an Error Trigger fires and sends a troubleshooting alert to the same Slack channel with specific fix instructions.


Benefits

  • Multi-Stage Progression: Four strategic touchpoints (45d, 30d, 14d, 7d) give you time to research alternatives, get quotes, negotiate terms, and finalize decisions β€” not just a last-minute panic alert.
  • No Duplicate Spam: Status column tracking ensures each contract only triggers once per stage, even if the workflow runs daily.
  • Catch-Up Logic: 5-day alert windows prevent missed notifications if your n8n server is down for a weekend or you skip a few days.
  • ROI-Focused Messaging: Every alert shows potential savings (15-25% of contract value) to justify the time spent on renewal research.
  • Freemium Conversion Funnel: Built-in upgrade CTAs with UTM tracking measure which contracts drive the most premium conversions.
  • Production Error Handling: Error Trigger workflow ensures you know immediately if credentials expire or APIs fail.

Target Audience

  • Finance/Ops Teams at startups managing 5-50 SaaS contracts who want automated renewal reminders but are willing to do manual research.
  • Procurement Managers who need advance notice to negotiate better terms and avoid auto-renewal price hikes.
  • CFOs/Controllers looking to reduce SaaS spend by 15-25% through systematic renewal reviews.
  • Bootstrapped Founders wearing multiple hats who can't afford dedicated procurement software but need basic contract monitoring.

Required APIs

  • Google Sheets OAuth2: Read/write access to your contract tracking spreadsheet.
  • Scope required: https://www.googleapis.com/auth/spreadsheets
  • Slack API: Post messages to your #contract-renewals channel.
  • Scopes required: chat:write, chat:write.public
  • Bot must be added to the channel before first run

Easy Customization

  • Alert Stages: Modify the alertStages array in the Brain node to change days (e.g., 60d, 45d, 30d, 14d for longer lead times) or urgency labels.
  • Notification Channels: Replace Slack nodes with Email (Gmail), Microsoft Teams, or Discord to match your team's communication stack.
  • Timezone: Change Workflow Settings β†’ Timezone from UTC to your local timezone (e.g., Europe/Helsinki, America/New_York) so 9 AM means 9 AM local time.
  • Schedule Frequency: Modify cron expression in Schedule node to run twice daily (0 9,17 * * *) or weekly (0 9 * * 1) instead of daily.
  • Data Destination: Swap Google Sheets for Airtable, Notion, or PostgreSQL by replacing the Sheets nodes while keeping the same logic flow.

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 - Sticky Note3

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

Block 2 - Sticky Note2

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

Block 3 - Sticky Note1

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

Block 4 - Sticky Note

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

Block 5 - README: Production Setup

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

Block 6 - Slack: Error Alert

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

Block 7 - Error Trigger

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

Block 8 - Google Sheets: Update Status

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

Block 9 - Slack: Daily Summary

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

Block 10 - Slack: Send Alert

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

Block 11 - IF: Is Alert?

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

Block 12 - Brain: Validate & Route

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

Block 13 - Google Sheets: Load Contracts

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

Block 14 - Schedule: Daily 9AM

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

3. Summary Table

Workflow Send multi-stage SaaS renewal alerts from Google Sheets to Slack
Complexity intermediate
Nodes 14
Categories Document Extraction
Author Mychel Garzon
Published 05 May 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15498/15498.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 Send multi-stage SaaS renewal alerts from Google Sheets to Slack do?

Your automated SaaS contract renewal monitor that sends multi stage Slack alerts 45, 30, 14, and 7 days before each contract expires. Stop missing renewal deadlines and overpaying on auto renewals....

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 Document Extraction use case.