FeaturedLegal & Compliance#Legal#Contract Management#Renewals#Google Sheets#Slack#Compliance

Contract Renewal & Expiry Tracker

Scan a contract register on a schedule, flag agreements nearing renewal or auto-renew notice deadlines, and alert owners in Slack.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Legal#Contract Management#Renewals#Google Sheets#Slack#Compliance

Click a node to select it — same as the Heym editor; the panel shows its settings.

7 nodes · Free & source-available

Contract Renewal & Expiry Tracker

Stop missing renewal windows and silent auto-renewals. This template reads a contract register from Google Sheets on a schedule, asks an LLM to surface agreements approaching expiry or notice deadlines, and routes the ones that need action to a legal-ops Slack channel.

What this workflow does

  1. renewalSchedule runs every Monday morning
  2. readContractRegister reads the contract register rows
  3. assessRenewals flags contracts within the renewal window, notice-period deadlines, and auto-renew traps
  4. renewalActionCheck branches when the output includes RENEWAL_ACTION
  5. notifyContractOwners posts the action list to Slack
  6. Outputs preserve the full renewal brief for the record

Use cases

  • Vendor and SaaS contract lifecycle management
  • Catching auto-renew notice deadlines before they pass
  • Giving legal and procurement a weekly renewals digest

Setup

Use a sheet with columns such as vendor, contractValue, renewalDate, noticePeriodDays, autoRenew, and owner. Connect a Google Sheets credential in readContractRegister, an LLM credential in assessRenewals, and a Slack credential for the legal-ops queue. This is an operations aid, not legal advice.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3PressCmd+V/Ctrl+V— nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis · production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom · glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner — none of them talk.
symptom · visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym · one runtime
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym