Block 1 - Sticky Note3
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
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....
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
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mychel Garzon.
Original n8n.io sourceStop 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.
The workflow executes in four stages:
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.
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:
Invalid rows are silently filtered out to prevent workflow crashes from bad data.
A Brain node calculates days-until-renewal using native JavaScript Date objects (no external dependencies). For each contract, it checks four alert windows:
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.
Success Path: When a contract enters an alert window:
utm_campaign = contract slug, utm_content = alert stage)"Active, alerted_45d"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.
https://www.googleapis.com/auth/spreadsheets#contract-renewals channel.chat:write, chat:write.publicalertStages array in the Brain node to change days (e.g., 60d, 45d, 30d, 14d for longer lead times) or urgency labels.Workflow Settings β Timezone from UTC to your local timezone (e.g., Europe/Helsinki, America/New_York) so 9 AM means 9 AM local time.0 9,17 * * *) or weekly (0 9 * * 1) instead of daily.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.
| Workflow | Monitor SaaS contract renewals from Google Sheets and send Slack alerts |
|---|---|
| Complexity | intermediate |
| Nodes | 14 |
| Categories | Document Extraction |
| Author | Mychel Garzon |
| Published | 05 May 2026 |
Use the JSON export at /data/workflows/15496/15496.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
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....
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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.