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

# Set up automation integrations

> Integrations let automations call external provider actions during automation runs.

## Automation integrations

An automation integration is the provider connection a team uses to call external actions during an automation run. Each provider page lists the actions that team can allow, the provider scopes those actions need, and the risk of each action.

## Connections

Admins connect a provider from **Integrations**. They pick the team, choose the actions that team may use, and authorize the provider account. When more than one connection exists for the same provider, Flow shows each connection's name so you can choose the right one.

## Set up an integration

1. Open **Integrations**.
2. Choose **Add connection**.
3. In **Add connection**, filter to **Automations**.
4. Search for the provider.
5. Follow the connect flow in Flow.

Provider pages are listed in the sidebar alphabetically by provider name. [GitHub](/automations/connectors/github) and [Slack](/automations/connectors/slack) are common starting points.

## HTTP API

HTTP API is for an API that Flow does not publish as its own integration. An organization administrator connects it from **Integrations**. The wizard asks who can use the connection, then collects the API source, base URL, and authentication.

See [HTTP API](/automations/connectors/http) for each field and choice.

## Permissions and scopes

When an admin allows an action, Flow requests the provider scopes that action needs. Automation runs don't send scopes with each call. Flow checks the allowed actions and the granted scopes before it calls the provider.

Some providers don't publish scopes. Their page says so under **Permissions and scopes**.

## Actions and risk

Each action has an action type and a risk tier.

Action type:

* **Read** actions fetch provider data.
* **Create** and **edit** actions change provider state.
* **Delete** actions remove or disable provider resources.

Risk estimates impact, separate from the action type:

* **Low** risk actions read provider data.
* **Medium** risk actions change existing records.
* **High** risk actions can grant access, remove data, disable resources, or make broad changes.

## Related topics

* [Use integration actions](/automations/build/connectors)
* [Automations](/automations)


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