What integration actions do
Automations call external systems through integration actions. An integration defines the actions Flow can use, and each action determines the provider access the automation needs. For tickets, assets, people, knowledge, and other data owned by Flow, use Flow actions instead.How integration actions work
Choose the right action
Use the integration page to confirm what the provider can do before publishing the automation.
Open the automation integration catalog to review supported providers.
Select connections
When an automation uses integration actions, Flow shows the required integrations when you test or publish it. From there, choose one of these paths:Keep access narrow
Select only the actions the automation needs. Flow uses the selected actions to request provider scopes during setup and to check access before calling the provider. This keeps automation access separate from other Flow integrations, such as knowledge, assets, or identity setup.Example
A support-intake automation that creates Jira requests and posts to Slack needs:
It does not need broad Jira administration or unrelated Slack workspace actions.