DOCUMENT OPS

Alert before auto-renewal notice windows close

Runs daily against the obligation calendar, finds contracts whose auto-renew opt-out deadline falls within a configurable window.

CategoryDocument Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionFetch upcoming auto-renewal notice deadlines from Google CalendarGoogle CalendarGoogle Calendar
  • LogicSplit imminent deadlines from approaching ones
  • ActionDraft per-contract decision summaries with OpenAIOpenAI
  • OutputPost renew-or-cancel prompt to SlackSlack

What it does

This workflow stops contracts from silently auto-renewing. It reads upcoming obligations from Google Calendar, isolates the auto-renewal notice deadlines arriving soon, and posts a clear decision prompt to Slack listing each contract, its counterparty, and the last date to act.

When to use it

Use it when you already track obligation dates on a calendar but still miss the narrow window to opt out of auto-renewals. It turns a passive calendar into an active nudge with enough lead time to make a renew-or-cancel call.

How it works

  1. 1A daily schedule starts the run.
  2. 2Google Calendar events tagged as auto-renewal notice deadlines within the lookahead window are fetched.
  3. 3A logic branch separates deadlines that are imminent (act now) from those that are merely approaching.
  4. 4For imminent items, OpenAI drafts a concise decision summary per contract.
  5. 5A Slack message is posted to the contracts channel with the summaries and the hard cutoff dates.
  6. 6The run returns which contracts were surfaced.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.