HTTP and Slack: Daily Store Operations Digest Template

A scheduled Spojit workflow pulls your daily retail metrics from your store system's REST API and posts a tidy operations digest to a manager Slack channel each morning.

What It Builds

A Schedule trigger fires once a day at the time you choose. A Connector node calls your store or point-of-sale system's REST API through the http connector to fetch yesterday's numbers (sales, transaction count, top sellers, low-stock items). A Transform node formats those figures into a readable summary, and a final slack Connector node posts the digest to your managers' channel.

The Prompt

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

Build a workflow that runs every morning at 7am. Call my store system's REST API to get yesterday's total sales, transaction count, top five selling products, and any items below their reorder threshold, then post a formatted daily operations digest to the #store-ops Slack channel.

Connectors Used

Schedule trigger - runs the workflow on a daily cron at the time and timezone you set.
http - Miraxa connects to your store or POS system's REST API to pull the daily metrics.
slack - posts the formatted digest to your chosen manager channel.

Customize It

Change the run time and the Slack channel name in the prompt, swap which metrics you pull (refunds, hourly traffic, labor hours), or point it at a second store by asking for a digest per location. You can also tell Miraxa to only post when a metric crosses a threshold, all without a second prompt.

Tips

Have your store API's base URL and an API key ready: Spojit stores it on the http connection so the request authenticates cleanly.
Use Direct mode on the Slack node for a fixed channel post; Agent mode only earns its keep when the AI needs to decide where to route.
Set the Schedule timezone to your store's local time so 7am means 7am on the floor.