Monday, MySQL and Slack: Stale-Deal Escalation Template

Build a Spojit workflow that runs every week, finds stale deals on a Monday pipeline board, records them in MySQL, and posts the escalation list to a Slack sales channel.

What It Builds

A Schedule trigger fires the workflow once a week. A Connector node on the monday connector reads your pipeline board with list-items, then a Condition and Loop sweep keeps only the deals whose last activity is older than your threshold. Each stale deal is written to a MySQL table with insert-rows, and a Connector node on the slack connector posts the full escalation list to your sales channel with send-message. The result is a weekly nudge that keeps deals from quietly going cold, with a MySQL log you can report on later.

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 Monday at 9am Australia/Sydney time. Read the items from my Monday pipeline board, keep only the deals whose last-activity date is more than 14 days ago, and for each stale deal insert a row into the MySQL stale_deals table with the deal name, owner, value, stage, and days stale. Then post a single message to the #sales Slack channel listing every stale deal with its owner and days stale.

Connectors Used

  • Schedule trigger - runs the workflow weekly on a cron expression and IANA timezone you set.
  • monday - list-boards and list-items read your pipeline board and its deals.
  • mysql - insert-rows logs each stale deal to your reporting table.
  • slack - send-message posts the escalation list to your sales channel.

Customize It

The obvious knobs to change in the prompt are the cron time and timezone (for example 0 9 * * 1 in America/New_York), the staleness window (swap 14 days for 7, 30, or whatever your team uses), the Monday board and the field that holds last activity, the MySQL table name, and the Slack channel (change #sales to your own). You can also tell Miraxa to add a Human approval node before the Slack post if you want a manager to sign off on the list first. Adjust those values in the prompt and Spojit tailors the build without a second prompt.

Tips

  • The Monday read and MySQL log are predictable single-tool calls, so keep those Connector nodes in Direct mode to avoid AI credit cost. Reserve Agent mode for steps that need judgment.
  • Make sure your MySQL stale_deals table already exists with matching columns before the first run, or have Miraxa add a Connector node that creates it. insert-rows writes data, it does not define the schema.
  • Run the workflow with the Run button once to confirm the Monday board, MySQL table, and Slack channel all resolve before you leave it on the weekly schedule.

Related

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