Automated Task Reminder & Notification Management System
Make.comBusiness operationsRead task rows from Google Sheets and route pending work into priority-specific Gmail reminders.
- Platform
- Make.com
- Focus
- Business operations
- Evidence available
- Original screenshot
Project overview
A compact Make.com scenario uses one task-data source and three reminder routes. The original capture makes the visible priority structure and the single exercised branch clear.
Business problem
Following up on outstanding tasks requires checking their state and choosing an appropriate reminder without treating all work as equally urgent.
Automation solution
Search Google Sheets rows, then use a Router with High + Pending, Medium + Pending and Low + Pending routes, each connected to Gmail Send an email.
Simplified process summary. Explore the architecture below for branches and decision logic.
Workflow evidence
Original image, preserved in full. Enlarge and zoom to read individual nodes.
Workflow architecture
Trigger & input
Google Sheets Search Rows is the first module. A clock badge is visible, but the scenario schedule and search conditions are not exposed.
Processing & output
- Google Sheets Search Rows supplies task rows to a Router.
- The first route is labeled High + Pending and leads to Gmail Send an email.
- The second route is labeled Medium + Pending and leads to another Gmail Send an email action.
- The third route is labeled Low + Pending and leads to a third Gmail Send an email action. The capture shows a bundle/completion marker on the Medium branch; High and Low show zero at their route filters.
Conditional logic
The route labels distinguish High, Medium and Low priorities combined with Pending state. The exact expressions, due-date criteria, recipients and message templates are hidden. Only the Medium route has execution evidence in this screenshot.
Key features
- Spreadsheet-driven task lookup
- Three priority-specific Pending routes
- Dedicated Gmail send action per route
- Visible partial-run evidence for the Medium route
Technical challenges
The visible complexity is aligning row data with priority/state routing. There is no visible write-back or logging module, so notification logging from the original brief cannot be confirmed. Duplicate prevention, task-state updates and repeat-reminder controls require additional evidence.
Business value
Intended to support more consistent task reminders and distinguish priorities. The screenshot does not establish email delivery to recipients, a logging system or measured follow-up improvements.
Project status
Testing & limitations
Partial test shown
A partial captured test is visible: the source and Medium + Pending/Gmail route show activity, while High and Low routes are not shown executing. Full branch coverage, successful delivery and production deployment are unverified.
Source: Kyle’s original workflow screenshot and project brief. The visible canvas has been reviewed; exported configuration, output contents and production run history have not been independently verified.
Limitations & next steps
What needs verification: resolve these open questions before treating this design as a verified implementation.
- Schedule and spreadsheet search criteria
- Complete filter conditions, due-date rules and recipients
- High/Low branch tests and repeat-notification prevention
- Notification logging or write-back behavior, which is not visible