Slack and Monday: Daily Customer-Request Digest Template

A scheduled Spojit workflow that reads the day's new items from a monday.com customer board, builds a tidy digest, and posts it to a Slack channel every evening.

What It Builds

This template runs on a Schedule trigger each evening, uses a Connector node on the monday connector to read the new items added to your customer-request board that day, then groups and formats them into one readable summary. A final Connector node on the slack connector posts that digest to the channel you choose, so the whole team sees every request in a single message instead of watching the board all day.

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 6pm Australia/Sydney. Read the items created today on my monday.com board named "Customer Requests", group them by status, and post a single digest to the #customer-requests Slack channel that lists each request with its title, owner, and status, plus a total count at the top.

Connectors Used

  • Schedule trigger - fires once per day on a 5-field cron expression and IANA timezone (for example 0 18 * * 1-5 with Australia/Sydney).
  • monday - a Connector node reads the board and its items (using tools such as get-board and list-items) so the day's new requests can be collected.
  • slack - a Connector node posts the finished digest to a channel with send-message.

Customize It

The obvious knobs to change in the prompt are the schedule (swap 6pm and the timezone, or run daily by removing weekday), the board name, the grouping field (group by owner or priority instead of status), the Slack channel, and which item fields appear in each line. You can also ask for an extra line that flags any request still unassigned, all without writing a second prompt.

Tips

  • For a fixed, predictable read like "list today's items", keep the monday and Slack Connector nodes in Direct mode so there is no AI cost; reach for Agent mode only if you want the digest summarized or prioritized in natural language.
  • The Schedule trigger can hold more than one schedule, so add a second cron line if you also want a morning digest of overnight requests.
  • Confirm the bot user behind your Slack connection is a member of the target channel, otherwise send-message cannot post there.

Related

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