> ## Documentation Index
> Fetch the complete documentation index at: https://docs.letsflow.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Use integration actions

> Use provider actions safely inside Flow automations.

## 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](/automations/build/flow-actions) instead.

## How integration actions work

```mermaid theme={null}
flowchart LR
  builder["Flow adds action"] --> requirement["Flow detects required integration"]
  requirement --> connection["Select or create connection"]
  connection --> run["Live tests and published runs use it"]
```

## Choose the right action

Use the integration page to confirm what the provider can do before publishing the automation.

| Question | Where to check |
| - | - |
| Can this integration perform the needed work? | Supported actions |
| What provider access is required? | Permissions and scopes |
| How much impact can the action have? | Risk |

Open the [automation integration catalog](/automations/connectors) 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:

| State | What to do |
| - | - |
| Ready connection exists | Select the connection for this automation |
| No ready connection exists | Connect the provider if you have permission |
| Another admin owns setup | Request setup or ask an admin to connect it |
| Connection needs repair | Fix the connection before live tests or publishing |

## 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:

| Integration | Needed action |
| - | - |
| Jira Service Management | Create customer request |
| Slack | Post message |

It does not need broad Jira administration or unrelated Slack workspace actions.

## Related topics

* [Automation integration catalog](/automations/connectors)
* [Test and publish](/automations/build/test-and-publish)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.