> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/automation/accounts.md).

# Accounts (connections)

Accounts in the automation module: create, test, rename and remove connections to equipme and third-party systems – OAuth sign-in, API key and security.

**Path:** sidebar → **"Automation" → "Accounts"**

An **account** is a stored connection to a system – to equipme itself, to Microsoft Entra ID, to your ERP or ticketing system. You create it once and then select it in as many flows and components as you like, without signing in again.

## The account list

| Column    | Content                                                                                |
| --------- | -------------------------------------------------------------------------------------- |
| "Name"    | Name of the account                                                                    |
| "Service" | The connected system, e.g. Equipme or Microsoft                                        |
| "Usage"   | In how many flows the account is used ("Used in 3 flows." or "Not used in any flows.") |
| "Status"  | Result of the last test: "Tested" (OK), "Failed" (connection broken) or "Not tested"   |

Use "Filter …" to search by name. The list shows the accounts of the selected workspace ("Personal" or "Team", see [Automation at a glance](https://hub.equipme.io/dokumentation/automation.md#personal-or-team)).

## Creating an account

**From the flow designer** (the usual way):

1. Drag a component of the system onto the canvas, e.g. a Microsoft Entra ID action.
2. In the inspector, click **"Connect account"** or **"Connect a new account"**.
3. Depending on the system, sign in or enter credentials (see below).
4. The new account is selected in the component and appears under "Accounts".

For every further component of the same system, simply select the account from the list ("Select account").

### Sign-in or API key

| Type                                               | How it works                                                                                                                   |
| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Sign-in with the provider** (e.g. Microsoft)     | A sign-in window of the provider opens. You sign in and confirm the requested permissions. equipme does not see your password. |
| **API key or credentials** (e.g. equipme, weclapp) | You enter a name ("Label") and the system's key or credentials.                                                                |

Which details a system needs is described on its page under [Connectors](https://hub.equipme.io/dokumentation/automation/connectors.md).

### Connection to equipme

For the [equipme connector](https://hub.equipme.io/dokumentation/automation/connectors/equipme.md) you need an **API key** from equipme:

1. Under [Integrations → "API key"](https://hub.equipme.io/dokumentation/settings/integrations-and-sso.md#api-key), generate a key and copy it.
2. In the flow designer, click "Connect account" on an equipme component and enter the label and API key.

Details are under [equipme connector → Setting up the connection](https://hub.equipme.io/dokumentation/automation/connectors/equipme.md#setting-up-the-connection).

## Testing an account

* **"Test"** on an account checks this one connection.
* **"Test all"** at the top checks all accounts in the list.

If an account shows **"Failed"**, the connection is broken – for example because the API key was deleted, a password changed, the permission was withdrawn at the provider or the sign-in expired. Create the connection again, select it in the affected components and restart the flows if necessary.

## Renaming an account

**"Rename"** on the account opens "Rename account". Give accounts meaningful names, e.g. "Entra ID – production" or "equipme – HR sync". This helps especially under "Team", when several people create accounts.

## Removing an account

**"Revoke"** removes the connection.

{% hint style="danger" %}
When an account is removed, **all flows that use it stop**. Check the "Usage" column first to see where the account is used. Afterwards you need to select another account in these flows and start them again.
{% endhint %}

## "Personal" and "Team"

* Accounts under **"Team"** are available to everyone in your company with access to the automation module. A flow under "Team" then runs regardless of who built it.
* Accounts under **"Personal"** are used only by you.

A flow uses accounts from its own workspace. So for team flows, create the account under "Team" as well.

## Security

* **Separate keys per purpose:** create a dedicated equipme API key for the automation module instead of sharing an existing one. That way you can revoke it specifically.
* **Least privilege:** grant third-party systems only the permissions the flow needs, and use service accounts rather than personal accounts where possible.
* **Create team accounts deliberately:** under "Team", everyone with automation access can use the account in their flows.
* **Tidy up:** remove accounts that are no longer used ("Not used in any flows.").
* **Staff changes:** when someone leaves the company, check whether flows depend on their personal access and switch them to service accounts.

## Frequently asked questions

**I created the account but don't see it in a component.**

Check that the account is in the same workspace ("Personal"/"Team") as the flow and that it belongs to the component's system.

**Can I use an account more than once?**

Yes. An account can be selected in any number of flows and components.

**What happens if I delete the equipme API key?**

All components using this key fail; the account shows "Failed" when tested. Create a new key and reconnect the account.

**Connecting to a provider fails – why?**

Often the provider is missing the required permissions or an administrator's approval (e.g. admin consent in Microsoft Entra ID). Notes are on the page of the respective [connector](https://hub.equipme.io/dokumentation/automation/connectors.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.equipme.io/dokumentation/automation/accounts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
