SMTP and Schedule: Daily Open-Ticket Reminder Email Template

A scheduled Spojit workflow that counts each teammate's open Front conversations and emails them a personal daily reminder of their outstanding customer threads from your own SMTP mail server.

What It Builds

This template uses a Schedule trigger to run every weekday morning. A Connector node on the front connector lists open conversations and your teammates, groups the open threads by owner, and a Connector node on the smtp connector sends each owner a personal reminder email from your own mail server. The result is a tidy daily nudge so nothing sits unanswered in the shared inbox.

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 8am Australia/Sydney time. List all open conversations in Front and list the teammates, group the open conversations by their assigned owner, and for each owner send a personal reminder email through the SMTP connector that says how many open customer threads they have and includes the subject line of each one. Skip owners with zero open conversations.

Connectors Used

  • Schedule trigger - fires on a 5-field cron in an IANA timezone (for example 0 8 * * 1-5 with Australia/Sydney); a single trigger can hold several schedules.
  • front - list-conversations pulls open threads and list-teammates resolves owner names; runs in Direct mode for predictable, no-AI calls.
  • smtp - send-email delivers each reminder from your own mail server, so the From address is your domain rather than Spojit's built-in mail service.

Customize It

Change the cron and timezone in the prompt to match your team's start of day, swap 1-5 for 1-7 to include weekends, and adjust the wording of the reminder body. You can also tell Miraxa to only email owners with more than a threshold of open threads (for example "skip anyone with fewer than 3 open conversations"), or to filter Front to a specific inbox or tag so the count covers just one queue.

Tips

  • Keep the front and smtp nodes in Direct mode. Counting and sending are deterministic single-tool calls, so you avoid AI credit cost and get the same result every run.
  • Add your team's addresses to the SMTP connection's verified sender domain before going live so the daily mail is not rejected as spoofed.
  • Use a Loop over the grouped owners so each person gets exactly one email; reference each owner's threads with {{ owner.conversations }} in the body.

Common Pitfalls

  • Cron is interpreted in the timezone you set, not the server's. Always pair the expression with an IANA zone like Australia/Sydney or the 8am reminder lands at the wrong local hour.
  • Front paginates list-conversations. On busy inboxes, page through all results before grouping, otherwise the counts undercount.
  • An owner with zero open conversations should be skipped. Without a Condition guard you will send empty "you have 0 open threads" emails.

Related Articles

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