Shopify and Slack: AI Order-Risk Flag Template
When a new Shopify order arrives, an Agent-mode Connector node scores it as low, medium, or high fraud risk and posts the high-risk ones to Slack with the reason.
What It Builds
This Spojit template starts with a Webhook trigger that fires the moment Shopify pushes a new order. An Agent-mode Connector node reviews the order against simple risk signals and returns a structured verdict through a Response Schema, so the result is always one of low, medium, or high plus a short reason. A Condition node then routes only the high-risk orders to a Connector node on the slack connector, which calls send-message to alert your team. Low and medium orders pass through untouched, so nobody is paged for ordinary traffic.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow triggered by a Shopify order webhook. Add an Agent-mode Connector node that classifies the order as low, medium, or high fraud risk and returns a JSON object with a "risk" field and a "reason" field using a Response Schema. Add a Condition node that checks if the risk is "high", and on the true branch add a Slack send-message node that posts the order number, customer name, total, and the reason to the #order-risk channel.
Connectors Used
- Webhook trigger - receives each new Shopify order as a JSON body, verified with a Shopify signing connection.
- shopify - the order data that feeds the risk check; use the connector if you need to enrich the order first.
- slack - posts the alert via
send-messageto your chosen channel.
Customize It
Change #order-risk to your own Slack channel, and adjust which risk levels alert by swapping "high" in the prompt for "medium" or a combined check. You can also tell Miraxa to include extra fields in the Slack message (shipping country, payment status, order tags) or to add a second branch that emails a reviewer. After scaffolding, open each node's properties panel to fine-tune the agent prompt and the Response Schema fields.
Tips
- Use Agent mode here because the risk call needs judgement; keep any straight order lookups in Direct mode to avoid AI cost.
- A Response Schema with a fixed enum (
low,medium,high) keeps the Condition node reliable; free-text verdicts drift and break branching. - Confirm the Slack connection can post to the target channel before going live, and invite the connection to private channels.