How to build a daily renewal digest in MI Flow: a scheduled trigger, a records query, a loop and condition, and email or webhook actions to owners.
By the MI Solutions SAM team8 min read2 exhibits
A renewal calendar only works if someone looks at it. MI Flow, the automation engine in MI One, takes that job over: it can check every morning for renewals approaching their deadlines and tell the right people, without anyone running a report.
The flow
Exhibit 1
Building blocks
01Triggers
Record created, updated or deleted, a field changing, an import completing, a schedule, a webhook, or a manual run.
02Data steps
Get records, get a record by ID, create, update or delete records, filter arrays.
03Logic
Conditions, branches, apply to each, do until, delays.
04Actions
Send an email, send a notification, send a webhook message or make an HTTP request.
Escalate as the deadline gets closer
A single reminder is easy to ignore. A short ladder of reminders, each going a little wider, makes sure every renewal gets a decision.
Exhibit 2
Other useful flows
01New contract alert
When a contract is created, notify the SAM lead to check the record.
02New entitlement alert
For license changes worth reviewing.
03Vendor profile updated
Notifications to vendor owners when a profile changes.
04Reclaim notices
Emails to inactive users before licenses are released.
Get started
Frequently asked questions
Do we need developers to build flows?
No. Flows are built in the MI One designer, starting from templates.
Can flows call our other systems?
Yes, through webhook messages and HTTP requests.
Can we test a flow before switching it on?
Yes. Use a manual run to check the result, then switch on the schedule.
See where your software budget goes
Bring your five largest vendors to a 30-minute call. Our SAM experts will show you where the savings usually hide, and how fast MI One can surface them.
