Monday and Slack: Stalled-Task Reminder Template

A scheduled Spojit workflow that scans a Monday.com board for items that have not moved in several days and nudges the owner in Slack so nothing in your customer pipeline goes quiet.

What It Builds

This template uses a Schedule trigger to run on a recurring cron (for example, every weekday morning). A Connector node on the Monday.com connector reads the board's items with list-items, a Condition node and date utilities flag items whose status has not changed within your stall window, and for each stalled item a Connector node on the Slack connector posts a reminder to the owner's channel with send-message. The result is a daily, hands-off sweep that keeps owners accountable for every open task.

The Prompt

Paste this into Miraxa, the intelligent layer across your automation, and it builds the workflow, connecting the tools for you:

Build a workflow that runs every weekday at 9am Australia/Sydney time, reads all items from my Monday.com board, finds items whose status has not changed in the last 3 days, and for each stalled item posts a Slack message to the owner's channel with the item name, its current status, how many days it has been stuck, and a link back to the Monday item.

Connectors Used

Schedule trigger - fires the workflow on a 5-field cron in your chosen IANA timezone (for example, 0 9 * * 1-5).
Monday.com - list-items reads the board's items, statuses, and owners; get-board can confirm the board layout.
Slack - send-message posts the reminder to the owner's channel; lookup-user-by-email can map a Monday owner to a Slack user when you want a direct ping.

Customize It

The obvious knobs to change in the prompt are the run time and timezone, the stall window (change "3 days" to whatever counts as stalled for your pipeline), and the destination channel (post to one shared #pipeline channel instead of per-owner channels). You can also narrow the scan by naming a specific status, such as only flagging items still in Working on it or Stuck, so finished items are never pinged.

Tips

Use Direct mode on both Connector nodes here: reading items and sending a message are predictable single-tool calls, so you avoid AI credit cost. Reach for Agent mode only if you want the reminder text drafted in a friendlier tone.
A Schedule trigger can hold several schedules, so you can run a light morning sweep on weekdays and a heavier catch-up on Monday without a second workflow.
Confirm the Slack connection's scope can post to every target channel, and invite the connection to private channels first, or send-message will fail for those.