Slack and Front: Unassigned-Conversation Nudge Template

A scheduled Spojit workflow that finds Front conversations with no assignee and posts a nudge to a Slack channel so customer messages always get picked up instead of slipping through unowned.

What It Builds

This template uses a Schedule trigger to run on a recurring cron (for example every 15 minutes during business hours). A Connector node on the front connector lists conversations from your support inboxes and keeps only the ones with no assignee. A second Connector node on the slack connector posts a single nudge message to a channel like #support with the count and a short list of the waiting conversations, so someone claims them before customers wait too long.

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 on a schedule every 15 minutes between 9am and 6pm on weekdays. Use the Front connector to list open conversations in our support inbox, keep only the ones that have no assignee, and post a single message to the #support Slack channel listing how many conversations are unassigned and a short summary of each one (subject and how long it has been waiting). If there are none, do not post anything.

Connectors Used

  • front - lists conversations and reads who they are assigned to; uses list-conversations and get-conversation in Direct mode.
  • slack - posts the nudge to a channel; uses send-message in Direct mode.
  • Schedule trigger - fires on a 5-field cron with an IANA timezone (for example */15 9-18 * * 1-5 in Australia/Sydney).

Customize It

Change the channel name (#support), the cron (run hourly, or only at the top of each shift), and the timezone to match your team. You can also tell Miraxa which Front inbox to scan, add a threshold so it only nudges when more than a set number are unassigned, or have it skip the post entirely when the list is empty so Slack stays quiet on slow days.

Tips

  • Keep the Front and Slack Connector nodes in Direct mode for this template: the actions are predictable single tool calls, so you avoid AI credit cost. Reach for Agent mode only if you want it to write a smarter, prioritized summary of which conversations to grab first.
  • Add the Slack app to the target channel before the first run, otherwise send-message cannot post there.
  • Set the Schedule trigger timezone explicitly so "business hours" lands where your team actually works, not in UTC.

Related

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