How to trigger Slack/Teams alerts for high‑risk orders using Flow Builder?

Question

Accepted Answer

Quick Answer

You can trigger Slack or Microsoft Teams alerts for suspicious orders in Shopware by combining Flow Builder conditions with webhook actions. Most stores use this for unusually high order values, mismatched billing and shipping countries, repeated failed payments, or risky payment methods. The setup usually takes under an hour if your Slack or Teams webhook is already ready, and the main work is defining the right risk rules without flooding your operations team with noise.

Before You Start

✦ Flow Builder access — you need admin permissions to create and activate flows.
✦ Slack or Teams webhook URL — the alert action depends on an incoming webhook endpoint.
✦ Defined fraud indicators — decide what counts as “high risk” before building conditions.

1

Create incoming webhook

Start on the Slack or Microsoft Teams side first. Create an incoming webhook for the channel where your operations or fraud review team already works. Keep the alerts in a dedicated channel instead of mixing them with deployment notifications or customer support messages. Otherwise people start ignoring them after a few days (this happens constantly on busy stores).

Create a new Slack app or Teams connector
Generate the incoming webhook URL
Test the webhook with a manual message

PRO TIP Add “HIGH RISK ORDER” directly into the webhook message title so alerts stand out immediately on mobile devices.

2

Create new flow

Settings → Flow Builder

Create a new flow using the “Order placed” trigger. This trigger works well because it fires immediately after checkout and still gives you access to customer, order, payment, and shipping data. Name the flow clearly so other admins know exactly what it does six months from now. We usually use names like “Fraud Alert — High Order Value”.

Select “Order placed” as the trigger
Name the flow based on the risk type
Keep one flow per major fraud condition

COMMON MISTAKE Many teams put every fraud rule into one giant flow. That becomes painful to debug later when alerts stop firing correctly.

3

Add risk conditions

This step decides whether the setup becomes useful or annoying. Add conditions that genuinely indicate fraud risk instead of broad rules that trigger on normal customer behaviour. Start simple. You can always add more signals later after reviewing real orders for a few weeks. Most stores begin with high order value thresholds and country mismatches before moving into advanced scoring logic.

Check for orders above a value threshold
Compare billing and shipping countries
Filter specific payment methods if needed

IMPORTANT If your conditions are too broad, your team will stop trusting the alerts within days because of false positives.

4

Configure webhook action

Add a webhook or HTTP request action to the flow and paste your Slack or Teams webhook URL. Then build the payload message using variables from the order context. Include the order number, customer email, order total, payment method, and a direct admin link if possible. Your operations team should be able to review the order without opening multiple tabs.

Paste the webhook endpoint URL
Map order variables into the payload
Include enough data for quick review

{
   "text": "HIGH RISK ORDER: {{ order.orderNumber }} | Total: {{ order.amountTotal }}"
}

5

Test and activate flow

Before enabling the flow on your live store, place test orders that intentionally match your fraud conditions. Check both positive and negative cases. You want to confirm the alert fires when it should and stays silent when it should not. This catches most configuration mistakes early, especially broken conditions or malformed webhook payloads.

Place a test order above the threshold
Verify the Slack or Teams message arrives
Activate the flow after successful tests

PRO TIP Keep alerts in “monitor only” mode for the first week before automatically cancelling or tagging risky orders.

Shopware Fraud Alert Checklist

0 of 6 complete

Create Slack or Teams webhook
Create new Flow Builder automation
Define high-risk order conditions
Add webhook payload variables
Test positive and negative cases
Activate the production flow

Mistakes Most Developers Make

! Alerting every expensive order

What happens: Legitimate wholesale or repeat customer orders constantly trigger alerts.

Fix: Combine order value checks with country, payment, or customer history conditions.

! Missing useful order data

What happens: Staff still need to open Shopware admin to understand why the alert fired.

Fix: Include totals, countries, payment method, customer email, and order links directly in the message.

! Forgetting negative testing

What happens: The flow works technically but floods channels with false alerts after launch.

Fix: Test orders that should not trigger alerts before enabling the flow in production.

Key Takeaway

The short version: Shopware Flow Builder can send real-time Slack or Teams alerts whenever an order matches your fraud conditions. The setup itself is fairly quick, but the quality of your conditions matters more than the webhook connection. Keep flows focused, include useful order data in the payload, and test both triggering and non-triggering scenarios before going live. Most stores get the best results by starting with a few high-confidence rules instead of building a complicated fraud engine immediately. Start with Step 3—that one alone handles most of it.

Magento (Adobe Commerce)

How to trigger Slack/Teams alerts for high‑risk orders using Flow Builder?

Create incoming webhook

Create new flow

Add risk conditions

Configure webhook action

Test and activate flow

Shopware Fraud Alert Checklist

Related Answers