Doris only ever posts into your own team’s channels. No flow sends anything to your buyer.
Microsoft Teams
Teams webhooks come from Workflows, Microsoft’s replacement for the retired Office 365 connectors. You create one from the channel you want Doris to post into.1
Open Workflows on the channel
In Teams, find the channel you want the alerts in. Hover its name in the sidebar, choose the … menu, then Workflows.You can also get there from the channel itself: … in the top-right, then Workflows.
2
Pick the webhook template
Search the template list for
webhook and choose Post to a channel when a webhook request is received.This is the template that matters. Others post plain text and will render Doris alerts as raw data — the one above understands the card Doris sends, so you get the title, the labelled facts and the button.For a group chat rather than a channel, choose Post to a chat when a webhook request is received instead.3
Confirm the connection
Teams shows which account the workflow will run as. Confirm it and continue.Whoever creates the workflow owns it. If they leave the company and their account is removed, the webhook stops working — so a shared or team-owned account is worth considering for a channel the whole team relies on.
4
Choose the team and channel
Select the team and the channel the messages should land in, then Add workflow.
5
Copy the URL
Teams shows the webhook URL once, with a copy button. Copy it now — you cannot see it again later, and getting a new one means creating the workflow again.It looks like
https://<something>.environment.api.powerplatform.com/powerautomate/automations/direct/....Slack
1
Create or open a Slack app
Go to Slack’s app directory and either create an app for your workspace or open an existing one.
2
Turn on incoming webhooks
Under Features, open Incoming Webhooks and switch them on.
3
Add a webhook and choose the channel
Choose Add New Webhook to Workspace, pick the channel, and allow it.
4
Copy the URL
Copy the URL Slack shows. It starts
https://hooks.slack.com/services/.Add the channel in Doris
A channel lives on the step that posts to it. There is no separate list to keep — open the flow, open its notify step, and the channel is there.1
Open the notify step on the flow
On the flow, select the step that does the notifying. Its panel shows the chat channel it posts to. While you are building a flow by asking, Doris offers to add a channel in the conversation as soon as the flow has a notify step.
2
Name it and paste the URL
Give it a name that says which room it is —
#revops, Deal alerts. Then paste the webhook URL. Doris works out whether it is Slack or Teams from the URL itself, so there is nothing to choose.3
Send a test
Press Test and go and look at the channel. A webhook URL says nothing about which room it points at, so this is the only way to be sure it is the one you meant. Test posts only to the channel you pressed it on.
Choosing where a flow posts
Each notify step posts to the one channel it names, and to nowhere else — pipeline slips to#revops, onboarding to #csm — so add as many as you need.
A step with no channel sends no chat message; its alert still reaches the person
in Doris and by email.
The step’s panel is also where a channel is renamed or removed, and where it
shows what it last delivered and why it last failed. Renaming matters more than
it sounds: the webhook URL is shown once and never again, so the name is the
only thing anyone will ever see of that channel.
Anyone who can change the flow can change its channels. On a flow you share
with your workspace, that is a workspace administrator; on your own, it is you.
If nothing arrives
Doris says the URL is not one it recognises
Doris says the URL is not one it recognises
Doris accepts webhook URLs on Slack’s and Microsoft’s own hosts and nothing else — pasting any other address is refused. Check you copied the whole URL, including everything after the
?.The test says delivered, but nothing appeared in Teams
The test says delivered, but nothing appeared in Teams
Teams accepts the request before it posts anything, so a workflow that was built from the wrong template accepts Doris’s message and then does nothing useful with it. Open Workflows on the channel, check the run history, and confirm the workflow came from Post to a channel when a webhook request is received.
It worked and then stopped
It worked and then stopped
Open the flow’s notify step — a failing channel shows the reason there. The usual causes are the workflow being deleted in Teams, the Slack app being removed from the channel, or the account that created the Teams workflow being deactivated.
Nothing arrives in chat, but the email does
Nothing arrives in chat, but the email does
The step has no channel named. Open the notify step on the flow and pick one — a step posts only to the channel it names, so adding a channel to the workspace does not by itself make an existing step use it.