> 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/connectors.md).

# Connectors

Overview of all connectors in the automation module: which systems equipme can be connected to and where to find the respective documentation.

**Connectors** connect equipme with other systems in the [automation module](/dokumentation/automation.md). Each connector comes with ready-made **triggers** (events) and **actions** that you combine via drag & drop in the [flow designer](/dokumentation/automation/workflows.md) – without programming.

## Available connectors

| Connector                                   | Category                  | Typical use cases                                                                                                     | Documentation                                                        |
| ------------------------------------------- | ------------------------- | --------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| **equipme**                                 | equipme                   | Use employees, locations, groups, assets, orders, approvals, tickets, email and forms in flows                        | [equipme connector](/dokumentation/automation/connectors/equipme.md) |
| **Microsoft Entra ID**                      | Identity & access         | Manage users, groups, licenses and devices – e.g. create accounts during onboarding and block them during offboarding | coming soon                                                          |
| **Microsoft Intune**                        | Device management         | Retrieve devices and set the device owner                                                                             | coming soon                                                          |
| **Microsoft Dynamics 365 Business Central** | ERP                       | Transfer customers, suppliers, items and sales invoices                                                               | coming soon                                                          |
| **weclapp**                                 | ERP                       | Transfer sales orders, purchase orders, invoices, contracts, items and serial numbers                                 | coming soon                                                          |
| **Autotask**                                | IT service management     | Synchronize companies, tickets, configuration items and contracts                                                     | coming soon                                                          |
| **Zoho Desk**                               | Helpdesk                  | Transfer tickets, comments, attachments and contacts                                                                  | coming soon                                                          |
| **Jamf**                                    | Device management (Apple) | in preparation                                                                                                        | coming soon                                                          |
| **SAP**                                     | ERP                       | in preparation                                                                                                        | coming soon                                                          |

In addition, general building blocks are available with which almost any system can be connected – e.g. **HTTP** (REST interfaces), **Webhooks**, **Email**, **Forms**, **Filter** and **Scheduler** (see [Workflows](/dokumentation/automation/workflows.md)). You can find many more standard connectors (e.g. for Microsoft Teams, Google Sheets or Slack) directly in the flow designer.

{% hint style="info" %}
Which connectors are available in your company depends on the automation scope that has been enabled. If a system you want to connect is missing, contact [Support](/dokumentation/help/support.md).
{% endhint %}

## Connecting a connector

The process is the same for all connectors:

1. In the flow designer, drag a component of the connector onto the canvas.
2. Click **Connect account** and enter the credentials for the target system (e.g. API key or sign-in with the provider).
3. The connection is saved and is available to all flows under **"Accounts"**. There you can test it ("Test") or revoke it ("Revoke").

You set up the connection to equipme itself with an [API key](/dokumentation/settings/integrations-and-sso.md#api-key).


---

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