> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-automate/18.latest/backoffice/connections.md).

# Manage Connections

A connection stores the credentials an action needs to talk to an external service. See [Connections](/umbraco-automate/18.latest/concepts/connections.md) for the underlying concept.

## Where Connections Live

Connections are managed from the **Settings** sidebar in the **Automate** section. The Settings sidebar is only visible to administrators.

<figure><img src="/files/mAaXlMFP7cjA3HBmXI1m" alt="The Automate section sidebar with the Automations tree on top and the Settings menu below."><figcaption><p>Connections live under the Settings menu in the Automate sidebar.</p></figcaption></figure>

## Create a Connection

1. Open the **Automate** section.
2. Switch to the **Settings** sidebar.
3. Open **Connections** in the tree.
4. Right-click the **Connections** root and select **Create connection**.
5. Pick a connection type from the picker, for example **Slack**.
6. Enter a name and configure the type-specific settings.
7. Click **Test connection** to verify the credentials.
8. Click **Save**.

<figure><img src="/files/s9l8K2RW1PzYh8ihs0QD" alt="The create connection modal with a connection type picker."><figcaption><p>Creating a connection.</p></figcaption></figure>

## Allow a Connection in a Workspace

A connection only appears in an action's connection picker when its workspace has explicitly allowed it.

1. Open the workspace that needs the connection.
2. On the **Settings** tab, find the **Allowed Connections** field.
3. Pick the connection from the connection picker.
4. Save the workspace.

## Test a Connection

The **Test connection** button calls the connection type's validator. For OAuth connections, this confirms the access token is still valid and can reach the provider's API. For credential-based connections, it attempts a real call.

A failed test shows the error message so you can correct the settings before saving. Connection types that do not implement a validator return a warning instead of a success.

## Use a Connection in an Action

When you configure an action that requires a connection, the connection picker only shows connections of the matching type that the current workspace has allowed.

## Delete a Connection

Open the connection from the Settings sidebar and click **Delete**. Any automation step that uses the deleted connection will fail at runtime until the step is reconfigured.

## Environment Safety

Connection definitions can transfer between environments via Umbraco Deploy, but sensitive credential values are stripped by default. See [Transfer Automations](/umbraco-automate/18.latest/add-ons/deploy/transferring-automations.md) for the rules Deploy applies.

## See Also

* [Connections](/umbraco-automate/18.latest/concepts/connections.md)
* [Transfer Automations](/umbraco-automate/18.latest/add-ons/deploy/transferring-automations.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.umbraco.com/umbraco-automate/18.latest/backoffice/connections.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
