Front and Slack: Fan Inbox Digest Template

A daily Spojit workflow that reads your new Front conversations, summarizes the messages from fans and brands, and drops a tidy digest into Slack so nothing in the creator inbox slips through.

What It Builds

A Schedule trigger fires once a day and hands off to an Agent-mode Connector node. The node pulls the new Front conversations since the last run, groups them into fan messages and brand or partnership inquiries, writes a short summary for each, and posts the whole digest as a single Slack message. You start the morning with one clear recap instead of a noisy inbox.

The Prompt

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

Build a workflow that runs every morning at 8am. Pull the new Front conversations from the last 24 hours, group them into fan messages and brand or partnership inquiries, write a one-line summary and the sender for each, and post the whole thing as a single digest to the #inbox-digest Slack channel with the brand inquiries listed first.

Connectors Used

  • Schedule trigger - runs the digest once a day on a cron schedule with your timezone.
  • Front - reads the new conversations from your shared creator inbox.
  • Slack - posts the formatted digest to a channel.

Customize It

Change 8am to your preferred time, swap #inbox-digest for your own channel, and adjust the lookback window or the categories (for example, add a "press" or "collab" group). You can also ask for the count of unread conversations or a link back to each Front thread, all in the same prompt.

Tips

  • Connect Front with read access to the inbox you want digested, and invite the Slack app to the target channel before the first run.
  • Agent mode lets the node choose the right Front and Slack actions and summarize on its own; if you only ever post one fixed message, a Direct-mode node is cheaper.
  • Start with a wide lookback window while testing, then tighten it to match your schedule so conversations are never counted twice.

Related

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