Monday and Slack: AI Task-Priority Scorer Template

A scheduled Spojit workflow that lists your open Monday.com items, scores each one for urgency and impact with an AI agent, and posts the top priorities to a Slack channel.

What It Builds

This template starts on a Schedule trigger, pulls open items from a Monday.com board with a Connector node, then runs an Agent-mode Connector node that scores every item by urgency and impact and returns a clean, structured ranking. A final Connector node on the slack connector posts the highest-priority items to the channel of your choice so the team sees what to work on first.

It runs unattended on whatever cron schedule you set, so each morning (or at any cadence) Spojit does the triage and Slack carries the result. The agent does the scoring and reasoning at runtime, while you build and tune everything by chatting to Miraxa, the intelligent layer across your automation.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow on a Schedule trigger that runs every weekday at 9am. List the open items from my Monday.com board, then use an Agent-mode Connector node to score each item from 1 to 10 on urgency and impact and return a structured ranking with the item name, scores, and a one-line reason. Post the top five highest-priority items to the #priorities Slack channel as a single formatted message.

Connectors Used

  • Schedule trigger - runs the workflow on a 5-field cron expression and timezone, with no manual start needed.
  • monday - list-items (or get-board) reads the open items you want triaged.
  • slack - send-message posts the ranked list to your chosen channel.
  • An Agent-mode Connector node with a Response Schema does the urgency and impact scoring and returns reliable JSON.

Customize It

Change the cron time and timezone in the prompt to fit your team (for example a 5-field expression like 0 9 * * 1-5 in Australia/Sydney). Swap #priorities for your real Slack channel, point the Monday step at the right board, and adjust how many items post by editing "top five." You can also reword the scoring criteria so the agent weighs deadlines, customer impact, or revenue the way your team prioritizes.

Tips

  • Keep the Monday read in Direct mode so it deterministically lists items with no AI cost, and reserve Agent mode for the scoring step where judgment is actually needed.
  • Give the Agent-mode node a Response Schema so the ranking comes back as predictable fields (name, urgency, impact, reason) that the Slack message can format cleanly.
  • A trigger can hold several schedules, so add a second run later in the day if your team wants an afternoon refresh.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.