Weekly Ironclad contract renewal digest in Slack and Asana

Every Monday, find contracts renewing or expiring in the next 90 days, post a ranked digest to Slack, and open Asana tasks for the ones that need a decision now.

Agentic Task
IroncladSlackAsanaOperationsNotifications & AlertsDaily Digests
PromptCreate

Every Monday at 8am, scan my Ironclad contract repository for agreements with a renewal or expiration date in the next 90 days, and turn what you find into an actionable renewal plan.

Ironclad record fields are dynamic, so before filtering anything, read the records schema to resolve the actual field IDs for renewal date, expiration date, auto renewal flag, notice period, counterparty, contract value, contract owner and contract status. Do not assume field names or hard code field IDs, since they differ per Ironclad tenant.

Then use Ironclad List Records to pull the contract records, paging through results until you have the full set. If a record in the list response is missing detail you need to make a call, use Retrieve a Record to fetch that single record in full. Skip any contract whose status is terminated, expired and closed out, or otherwise already ended, since those need no decision.

For each remaining contract, work out the date the decision actually has to be made. That is not the renewal date itself. For a contract with a notice period, the real deadline is the renewal or expiration date minus the notice period, because after that point the cancellation window has closed. Treat that notice deadline as the date that drives urgency.

Rank the contracts by how soon a decision is needed, and pay special attention to auto renewing contracts where the cancellation notice window closes before the next weekly run seven days from now. Those are the ones that will silently renew if nobody acts this week, so they outrank everything else regardless of value.

Group the results into three buckets. Act now covers contracts whose notice deadline falls before the next weekly run, or has already passed while the contract is still live. Decide this month covers contracts whose notice deadline or renewal date falls within roughly the next 30 days. Watch covers the rest of the 90 day window. Within each group, list the highest contract value first so the biggest financial exposure is read first.

Post the prioritized digest to my contracts Slack channel using Send a Message. Use the three groups as clear headings, and for each contract show the counterparty, contract value, renewal or expiration date, the notice deadline, and whether it auto renews. Call out the auto renewing contracts in the Act now group explicitly, so the reason they are urgent is obvious. If a group is empty, say so briefly rather than omitting it.

For every contract in the Act now group, create an Asana task with Create a Task. Assign it to the contract owner recorded on the Ironclad record, set the due date before the notice deadline so there is time to act, and put the counterparty, contract value, renewal date and notice deadline in the task notes along with a way to identify the contract record.

Do not create a duplicate Asana task for a contract that was already flagged in a previous run. Before creating anything, check which contracts you have already raised tasks for in earlier runs and skip those, so each contract gets one task rather than a fresh one every Monday. If an already flagged contract is still unresolved, mention it in the Slack digest as an outstanding item instead of opening a second task.

Additional information

What does this prompt do?
  • Checks your Ironclad contract repository every Monday morning for agreements that renew or expire within the next 90 days
  • Flags auto renewing contracts whose cancellation notice window closes before next week's check, so nothing renews by default while you are not looking
  • Posts one ranked Slack digest split into Act now, Decide this month and Watch, with your highest value contracts listed first
  • Opens an Asana task for every urgent contract, assigned to its owner and due before the notice deadline, without repeating tasks it already created
What do I need to use this?
  • An Ironclad account with access to your contract repository
  • A Slack workspace and a channel where the weekly digest should be posted
  • An Asana account with a project for renewal tasks, and owners set up as Asana users
  • Renewal dates, auto renewal flags and notice periods filled in on your Ironclad contract records
How can I customize it?
  • Change the 90 day look ahead window, or the day and time the weekly check runs
  • Adjust what counts as Act now versus Decide this month to match how long your legal team needs to turn a renewal around
  • Send the digest to a different channel, or route the highest value contracts to their own channel or direct message

FAQs

Why does it focus on the notice deadline instead of the renewal date?
Because the renewal date is usually too late. If a contract auto renews and requires 60 days notice to cancel, the decision really has to happen 60 days before renewal. This workflow works backwards from the notice period so contracts surface while you can still do something about them.
Will it create the same Asana task for a contract every week?
No. Before creating anything it checks which contracts were already flagged in earlier runs and skips those, so each contract gets one task. Still unresolved contracts get mentioned in the Slack digest as outstanding rather than getting a second task.
What happens to contracts we have already terminated?
They are filtered out. The digest only covers agreements that are still live and genuinely need a decision, so your channel does not fill up with contracts nobody needs to think about.
What if a contract has no renewal date recorded?
It cannot be ranked, so it is left out rather than guessed at. This is a good reason to keep renewal dates, auto renewal flags and notice periods filled in on your Ironclad records, since the quality of the digest depends on that data.
What if different people own different contracts?
Each Asana task is assigned to the owner recorded on that contract in Ironclad, so tasks land with the right person automatically instead of everything going to one inbox.

Related templates

Turn website roof inspection requests into JobNimbus leads

New roof inspection requests from your website form land in JobNimbus within a minute, with no duplicate records and nothing retyped by your team.

JobNimbus
Google Forms
Slack
Agentic Task
Triage new Jira Service Management requests before anyone opens them

Every new customer request gets a priority, triage labels, a friendly reply with the right help article, and a Slack ping only when it is truly urgent.

Jira Service Management
Jira
Slack
Agentic Task
Risk-check every dependency upgrade pull request in GitHub

When a bot opens a version bump pull request, we read the real documentation for that exact version and tell you whether it is safe to merge.

Context7
GitHub
Slack
Agentic Task
Launch an Ironclad contract when a HubSpot deal is won

The moment a deal hits Closed Won, the right contract starts in Ironclad, the link lands on the deal, and your sales channel hears who owns the next step.

Ironclad
HubSpot
Slack
Agentic Task
Turn repeat support tickets into draft help articles

Every Friday, spot the questions your team keeps answering by hand and get a ready-to-review help article drafted from real fixes.

Jira Service Management
Confluence
Slack
Agentic Task
Chase overdue ERPNext invoices with escalating reminders

Every weekday morning, review your unpaid ERPNext invoices, email each customer a reminder that gets firmer as the debt ages, and brief finance in Slack.

ERPNext
Gmail
Slack
Agentic Task

Stop losing money to contracts that renew themselves.

Get a ranked renewal plan in Slack every Monday, with tasks already assigned before the cancellation window quietly closes.