> 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/pro/automation/connectors.md). # Connectors Overview of the connectors in the Equipme Pro automation module: equipme connector with Pro modules, ERP, PSA, helpdesk, Microsoft, distributors, leasing and shipping providers. **Connectors** connect Equipme Pro with other systems in the [automation module](/pro/automation.md). Each connector comes with ready-made **triggers** (events) and **actions** that you combine via drag & drop in the [flow designer](/pro/automation/workflows.md) – without programming. ## Available connectors | Connector | Category | Typical use cases | Documentation | | ------------------------------------------------------------------------------------------- | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- | | **equipme – "Equipme Pro" module** | equipme (provider) | Customers, customer locations and employees, services and offers, service instances, customer orders, fulfillment positions and parcels, purchase orders, product master data, billing, order authorizations | [equipme connector – Pro modules](/pro/automation/connectors/equipme-pro.md) | | **equipme – "Equipme", "Equipme Approval", "Equipme Operations", "Email", "Forms" modules** | equipme | Employees, locations, groups, assets and orders of your own organization, tickets, email and forms | see customer guide, "equipme connector" | | **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 (PSA) | 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 | ### Industry-specific connections for providers For provider operations, additional connections to typical partners in the hardware and service business are available. Which ones are specifically available is something you clarify with equipme. | Category | Typical use cases | | -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | **Distributors and wholesalers** | Retrieve products and data sheets from the distributor catalog, fill shopping carts, place orders with the distributor and retrieve order documents | | **A distributor's reseller ERP** | Retrieve contacts and items, create sales orders and order items | | **Leasing and rental financing** | Create quote requests and calculations, retrieve financing cases and contracts, manage partners, complete shopping carts | | **Shipping and parcel tracking** | Retrieve delivery and tracking information, create returns | 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](/pro/automation/workflows.md)) as well as the helper modules **"Lists"** (compare and merge lists) and **"PDF"** (convert HTML to PDF). 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](/pro/help/support.md). {% endhint %} {% hint style="info" %} Some distributor and shipping connections are also available as built-in integrations without a flow, e.g. the product import from a distributor catalog or passing parcels to a shipping service. You set these up under [Administration → "Integrations"](/pro/administration/integrations.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 Pro itself with an [API key](/pro/administration/integrations.md#api-key) from Pro. ## Frequently asked questions **Which connector is responsible for my provider data?** The **"Equipme Pro"** module of the equipme connector. The other equipme modules ("Equipme", "Equipme Approval", etc.) work with your own organization's data, just as a customer does in their customer portal. **Can I use the distributor catalog without a flow?** Yes. For the product import, there is a built-in integration under ["Integrations"](/pro/administration/integrations.md). A flow is worthwhile if you need your own rules, e.g. regularly synchronizing certain categories. --- # 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/pro/automation/connectors.md?ask=&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.