New order and lead alerts in Slack or Microsoft Teams
Short answer: Post an alert to Slack or Teams only when someone has to act on it soon, and send everything else as a daily summary. For a Shopify store, Shopify Flow's "Send Slack message" action is the simplest route. For website forms, a Slack incoming webhook or a Teams workflow triggered by a webhook does the job. Keep each message short, put it in a dedicated channel, and leave personal details in the system they came from.
Order and enquiry emails pile up in one person's inbox, and everyone else finds out late. Moving alerts into the team chat fixes that until the channel becomes so noisy people mute it. The trick is deciding what deserves a ping before choosing the tool.
Decide first: does this alert need a chat message?
Work through these questions for each type of event.
1. Does someone need to act within the next few hours?
- No → leave it out of chat. Use a daily or weekly summary email or report.
- Yes → go to question 2.
2. How many of these happen per day?
- A handful → one message per event is fine.
- Dozens or more → post only the exceptions (large orders, express shipping, failed payments, enquiries for a specific service) and summarise the rest.
3. Who acts on it?
- One role (dispatch, sales, the owner) → one channel for that role, and mention the role's user group only when needed.
- Several roles → separate channels per action, not one "#notifications" channel for everything.
4. Does it need a reply or a status?
- Yes → put the conversation in a thread under the alert, so the history stays with the order or lead.
- No → a plain message is enough.
Hypothetical example: a small Dublin homeware shop
- Every new order → no chat alert; a morning summary covers it.
- Orders with express shipping → #dispatch, one message each.
- Orders above a set value → #owner, for a personal thank-you note.
- Contact form enquiries about trade accounts → #sales, with a mention for whoever is on duty.
- Failed workflow runs → #ops, so broken automations get noticed.
What to put in the message
A good alert answers "what, how urgent, where do I click".
- Type and key fact: "Express order #1042, 3 items" or "Trade enquiry: café, Galway".
- One link to the order or lead in your admin, where the full details live.
- No unnecessary personal data. Names, addresses and phone numbers belong in Shopify, your CRM or form tool, not copied into chat history; check the rules where you operate on what you keep where.
Recipe 1: Shopify orders to Slack with Shopify Flow
Shopify's help page for the Send Slack message action sets out the steps:
- Connect Flow to your Slack account.
- Add the FlowBot app to each Slack channel it will post in (channel details → Integrations → Add an app).
- In a workflow, add the action and fill in the channel (
#your-channel-name, or the channel ID with a$prefix for unnamed channels) and the message. - Format the message with Slack's mrkdwn, including a link such as
<https://…|View order>.
Shopify notes the action can be used with any trigger, so you can start from an order trigger, add a condition (shipping method, order value, tag), and only then send the Slack message. The same page lists ready-made templates, including a Slack alert when a Flow workflow run fails, which is worth turning on regardless.
Recipe 2: Website forms to Slack with an incoming webhook
Slack's guide to incoming webhooks explains the model: you create a Slack app, activate incoming webhooks, pick a channel, and get a unique URL. Your form handler or automation tool sends a JSON payload to that URL, and the message appears in the channel.
Details worth knowing from the same page:
- The webhook URL contains a secret. Don't put it in public code; Slack says it searches for and revokes leaked secrets.
- You can't override the default channel, username or icon from the webhook; they come from the app configuration. One webhook per channel, then.
- You can't delete a message after posting it through a webhook.
- You can format with Slack's text formatting and layout blocks, and post replies in threads.
This suits a custom website form, a booking system that supports outgoing webhooks, or a small script.
Recipe 3: Forms and orders to Microsoft Teams with Workflows
Microsoft's incoming webhook documentation states that Office 365 Connectors in Teams, including connector-based incoming webhooks, were retired in May 2026. To receive webhook requests and post to Teams, use the Workflows app with the "When a Teams webhook request is received" trigger, starting from a template or from scratch.
From the same page:
- Workflows webhooks support private channels.
- They accept Adaptive Card and MessageCard payloads; for interactive buttons, use Adaptive Cards.
- A workflow belongs to specific users (its owners), not to the team or channel. Add a co-owner so the alert doesn't stop when someone leaves.
If you still have an old connector URL in a form plugin or script, that's the first thing to check.
Recipe 4: No-code connectors in between
When the source system has neither a Slack/Teams integration nor webhooks, an automation tool such as Zapier or Make can sit in the middle: trigger on a new form entry or order, filter, then post to Slack or Teams. Use the filter step to keep the channel quiet, and check each tool's current task limits on its own pricing page.
Avoiding alert fatigue
- Review after two weeks. Which alerts led to an action? Remove the rest.
- Mute-proof the important ones. If every message mentions everyone, people stop noticing mentions.
- Use a summary for volume. A morning digest ("14 orders yesterday, 2 express, 1 refund request") keeps the team informed without pings.
- Name channels by action: #dispatch-today, #new-enquiries, not #shopify.
FAQ
Should every order go to Slack?
Rarely. For most small stores, only exceptions and orders needing fast action are worth a message; the rest belong in a summary.
Is a webhook URL safe to put in my website code?
Keep it on the server side. Slack treats the URL as a secret, and anyone holding it could post to your channel.
Our Teams alerts stopped working. Why?
If they used an Office 365 connector webhook, Microsoft's documentation says those were retired in May 2026. Rebuild the alert with a Workflows webhook.
Can staff reply to the customer from Slack or Teams?
Not through these simple alerts. Use the alert's link to open the order or lead and reply from there.
Alerts that reach the right person and nobody else are a small build, so tell us which events your team needs to see.