Get notifications in Microsoft Teams
Connect Microsoft Teams to receive previous-day summaries and AI optimization proposals in a channel, including how to set up a Teams workflow.
Author: Cascade
Connect Microsoft Teams to receive ad performance updates and AI proposals in a Teams channel. Open Settings > Integrations in the left menu. Create a workflow in Teams, then paste the generated URL into Cascade. Setup takes about 5 minutes. Configure the connection for each product.
Notifications you receive
Click View in Cascade in each message to open the details. Proposals and notices are sent only when they are newly created.
Notification | When it arrives |
|---|---|
Connection confirmation | Immediately after connecting |
A summary of the previous day's ad performance, including spend, impressions, clicks, CV, and CPA by ad platform. If a measurement tag is installed, it also includes Cascade-measured CV and CPL, and a breakdown of CV discrepancies. Sections include Yesterday's Changes, Delivery Status, and Ad Platform Settings Changes (Outside Cascade), plus breakdowns by campaign and ad group (sent as cards after the summary). | Every morning at 9:00 AM (only for products connected to ad platforms; changes and breakdowns appear only when applicable) |
LP Form Submission Notifications | On each submission or in a digest every morning at 9:00 AM (under Settings > Product Settings, choose Won't be sent, On every submission, or Once a day (digest)) |
AI optimization proposals: budget 💰, bids 📈, bidding strategy switches 🔀, maximum CPC 🎚️, placement exclusions 🎯, targeting 👥, creatives 🎨, copy ✏️, keywords 🔑, recommended audiences 📇, ad copy based on search terms 🔎, Amazon delivery schedules ⏰ and placements 🎯, Rakuten RPP 🛍️, LINE Delivery 📬, and more | When a new proposal is created |
Auto-apply results 🤖 and notices about changes to auto-apply settings | When a proposal with auto-apply enabled is applied or auto-apply settings change |
Automation rule | When a Campaign Management automation rule's conditions are met |
"⚠️ Some campaigns have high budget spend" and "Monthly budget pacing notice" | When the pace of budget spending differs from expectations |
"Ad review notice" and "Ad eligibility change notice" | When an ad or asset is disapproved or its eligibility changes |
"Inventory-linked ad guard notice", "Amazon Buy Box win rate notice", Amazon competitor price changes 🔍, and results of changes to your prices 💴 | When ads are paused because of a stockout, the Buy Box win rate drops, or Pricing detects a change or changes a price |
Ad Expression Check results 🛡️ and legal check results (approved ✅, sent back ↩️, or revoked ⚠️) | When a check or approval is completed |
LP Analysis updates 🔍 | When analysis results are updated |
Scheduled report creation, changes, and deletion 📊, and execution results | When report settings change or a report runs |
Integration notices (reauthorization, expired credentials, expired Smaregi authorization, or duplicate au PAY Market connections) | Before or after a connection stops working |
Requirements
Available on the Business plan
An Owner or Admin can connect or disconnect the integration
You need permission to create and edit channels in Teams
A channel to receive notifications (a dedicated channel makes them easier to follow)
You need a work or school Microsoft account
About your account This integration uses Workflows in Teams. Workflows is not available with personal Microsoft accounts (such as @outlook.com or @hotmail.com). Make sure you are signed in with an account provided by your company or school.
Steps
1. Open the Teams channel where you want to receive notifications
In Microsoft Teams, open the channel where you want Cascade notifications to arrive.
2. Add a workflow to the channel and generate a URL
Hover over the channel name and click ... (More options) on the right.

Select Workflows from the menu. The workflow creation screen opens.
Enter "Webhook" in the search field and select Post to a channel when a webhook request is received. Depending on your Teams interface, it may be called Send webhook alerts to a channel.

Follow the on-screen instructions. On the account connection screen, verify the account shown and click Next.

Confirm the destination team and channel, then click Add workflow. Click Copy to save the displayed Webhook URL.

Do not share the URL with anyone. Anyone with this URL can post to your channel. Avoid sharing screenshots of it as well.
For detailed instructions, see Microsoft's official guide, Create incoming webhooks with Workflows for Microsoft Teams.
3. Open the connection screen in Cascade
In the left menu, open Settings > Integrations. Under Workspace Integrations, click Connect for Microsoft Teams. The Connect Microsoft Teams screen opens.

4. Paste the URL and connect
Paste the URL copied in step 2 into Webhook URL. Click Connect Teams.
Setup is complete when "Successfully connected to Microsoft Teams." appears. Microsoft Teams shows Connected in the list. The following message also arrives in the Teams channel.
"🎉 Cascade and Microsoft Teams are now connected! Notifications will arrive in this channel."
If the message does not arrive after a while, see "Troubleshooting".
Disconnect the integration
On the Integrations page, click Remove for Microsoft Teams. The following confirmation appears.
"Disconnecting prevents access to data from the connected service and limits the reports and data you can view. Are you sure you want to disconnect?"
Confirm to disconnect. Notifications to Teams stop immediately. Messages already delivered remain in the channel. Your Cascade reports and data are not affected.
To change the notification channel, disconnect first, then reconnect using the new channel's URL.
Troubleshooting
Issue | Cause | Solution |
|---|---|---|
You cannot find Workflows | You are signed in with a personal Microsoft account. | Sign in again with a work or school Microsoft account. |
The message "Failed to connect with Microsoft Teams." appears | The URL was copied incorrectly, uses an old format, or the workflow is disabled in Teams. | Paste the URL from step 2 again exactly as copied. Only URLs in the form "https://[name].environment.api.powerplatform.com/..." are accepted. Old formats starting with logic.azure.com or webhook.office.com are not supported. If the issue continues, create a new workflow starting from step 2. |
The connection is complete, but notifications do not arrive | The workflow is disabled in Teams, or the channel was deleted or changed. | In Teams, check that the workflow is enabled under Workflows. |
You cannot click Connect | You do not have permission to configure the integration. | Ask an Owner or Admin to configure it. |
Related articles
More articles in this category

