Skip to main content
Publishing makes one saved revision available to an audience. Draft changes do not affect the published automation. Every production run still needs an execution team for authorization, connections, and limits.

Requests from Slack, Teams, and email

Flow does not show team-scoped automations to requesters in Slack, Teams, or email channels. Belonging to a selected team does not change this restriction or grant service desk agent access. Choose the organization audience for requester-channel discovery. This choice does not make the automation available in every channel: the channel must route requests to the automation’s owning team. The current published version must also support the channel and meet the existing authorization, audience, readiness, configuration, and availability requirements.

Publish an automation

1

Open the automation and save your changes.

2

Select Publish.

3

Choose an audience and review its channel limits.

4

Select a ready connection for each required integration and team.

5

For schedule or event triggers, choose the service account under Automated execution → Run as.

6

Review the selected version, diagnostics, Validation scenario readiness, triggers, and audience.

7

Select Publish automation.

Flow blocks publication when a required connection, service account, approval procedure, Validation scenario review, or automation diagnostic is not ready. Changing the audience or execution setup requires publishing again. Active runs keep the version, team, connections, and identity they started with.

Stop new runs

Open the automation’s row actions, select Unpublish, and confirm. Saved revisions and run history remain available to authorized operators.