# Teams webhook workflow will not post to a private channel > For the full documentation index, see https://250highstreet.com/llms.txt > A Workflows webhook runs but nothing shows in a private channel? Microsoft lists flow bot posting in private channels as not ready. Post as a user instead. Short answer: Microsoft's Learn page says the Workflows app "can post as a flow bot in shared channels" and that support for posting as a flow bot in private channels "is under development". It adds: "Workflows can currently post messages on behalf of a user." Microsoft's April 14, 2026 post on the connector retirement goes further: "Private channels are already supported for Workflows webhooks through the Power Automate portal." So if your workflow posts as Flow bot and the target is a private channel, try changing the Post as setting to User in Power Automate. Three Microsoft pages word this differently, so I describe each below and tell you what to test. ## What Microsoft says - The Learn page "Webhooks and connectors - Teams" lists it under Known issues: Flow bot posting works in shared channels, is under development for private channels, and posting on behalf of a user works now. - The Microsoft Teams connector reference page says about the action that posts a card: "Posting a message or adaptive card to a private channel currently isn't supported." That page also lists two settings for the action, named "Post as" and "Post in". - Microsoft's post "Retirement of Office 365 connectors within Microsoft Teams", updated April 14, 2026, says private channels "are already supported for Workflows webhooks through the Power Automate portal", and that picking a private channel directly in the Workflows app in Teams would be fully rolled out by April 20, 2026. Because the pages differ, treat the fix below as a test, not a promise. ## The fix to try Exact names may differ on your screen. 1. Open Power Automate and find the webhook flow you built from the Workflows app, under My flows. 2. Open that flow. 3. Select Edit. 4. Open the action that posts the card to Teams. Its name on the connector page is "Post card in a chat or channel". 5. Find the setting "Post as". If it says Flow bot, change it to User. 6. Check the setting "Post in" points to your channel. 7. Select Save. 8. Send a test request to the webhook URL. Microsoft's example body is {"text": "Hello from a webhook workflow!"}. If the message now appears in the private channel, it was the Flow bot setting. ## What "on behalf of a user" means for you The post then shows under a person, not under a bot. Our advice, not a Microsoft rule: pick a shared service account as the owner, so alerts do not stop when one employee leaves. If the owner leaves and nobody else is set as co-owner, the flow can end up with no one in charge, which Microsoft calls an orphan flow. See "[Power Automate flow owner left the company](/guides/power-automate-flow-owner-left-company/)". ## If it still fails Check that the account on the Teams connection can open that private channel in Teams. Then send the test request again. ## Government cloud note Microsoft's connector reference says the Flow bot poster option "is available only in commercial tenants." In a Government Cloud tenant it names the error "BotNotInConversationRoster - The bot is not part of the conversation roster" and says to use the User option instead. ## Other reasons a channel stays empty - The workflow is switched off. Open the Workflows app, find the flow in your list of workflows, open its More actions (...) menu, and see which of Turn on or Turn off is offered. - The sender still uses an old Office 365 connector URL. See "[Teams webhook stopped working? Replace it with a Workflows webhook](/guides/teams-webhook-stopped-working-use-workflows/)". - The flow connection expired. See "[Power Automate connection expired, flow failing](/guides/power-automate-connection-expired-flow-failing/)". ## When to get help You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: \$5,000 for one, built in 2 weeks. See "[What a SharePoint tracker costs to build](/guides/what-a-sharepoint-tracker-costs/)". Bring one example of the problem to a free call. I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything. See trackers I built: [Tools I built](/portfolio/) ## FAQ ### Can a Teams Workflows webhook post to a private channel? Microsoft's Learn page says flow bot posting in private channels is under development, and posting on behalf of a user works now. ### Where is the Post as setting? In the Power Automate action "Post card in a chat or channel". Microsoft's reference lists the settings "Post as" and "Post in". ### What is the Flow bot option? It is a poster choice in that action. Microsoft says it is available only in commercial tenants, and to use User in Government Cloud. ### Why does the webhook run with no error but show nothing in the channel? One cause to test is the Flow bot setting on a private channel. Switch Post as to User and send a test request. ### Will Microsoft add flow bot support for private channels? Microsoft's Learn page says flow bot posting there is under development. Microsoft's April 14, 2026 post says private channels already work for Workflows webhooks through the Power Automate portal. ## Sources - [Microsoft Learn, Webhooks and connectors - Teams](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/what-are-webhooks-and-connectors) - [Microsoft Learn, Microsoft Teams connector reference](https://learn.microsoft.com/en-us/connectors/teams/) - [Microsoft Learn, Create an Incoming Webhook - Teams](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook) - [Microsoft Developer Blog, Retirement of Office 365 connectors within Microsoft Teams](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/) ## Related guides - [Teams webhook stopped working? Replace it with a Workflows webhook](/guides/teams-webhook-stopped-working-use-workflows/) - [Teams shared channel vs private channel](/guides/teams-shared-vs-private-channel/) - [Teams channel files missing: how to get them back](/guides/teams-channel-files-missing/) Source: https://250highstreet.com/guides/teams-workflow-webhook-post-to-private-channel/