> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.goautonomous.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up connectors

> Connect Go Autonomous to your ERP, CRM, and other business systems using pre-built or custom connectors.

## Overview

Connectors are the bridge between Go Autonomous and your external systems. When a request is confirmed in Flow, the connector sends the data to the right destination — whether that's your ERP for order processing, your CRM for customer updates, or a custom API for specialized workflows.

## Available connector types

Go Autonomous offers pre-built connectors across several categories:

> [tab] CRM
>
> * **Dynamics Customer Service** — integrate with Microsoft Dynamics 365 Customer Service.
> * **Salesforce** — integrate with Salesforce CRM.
> * **Zendesk** — integrate with Zendesk for customer service workflows.

> [tab] ERP
>
> * **Infor M3** — integrate with Infor M3 ERP.
> * **SAP C4C** — integrate with SAP Cloud for Customer.

> [tab] Custom
>
> * **API** — custom API integration for any system with a REST API.
> * **GoAutonomous** — Go Autonomous connector with API key for platform-to-platform communication.
> * **Third-Party** — integrate with a third-party system using webhooks and data contracts.

> [tab] File Transfer
>
> * **SFTP** — secure file transfer integration for systems that exchange data via files.

> [tab] Identity
>
> * **SAML** — single sign-on (SSO) integration with any SAML 2.0–compliant identity provider, like Microsoft Entra or Okta.

> [tab] Productivity
>
> * Additional productivity integrations for team tools and communication platforms.

## Set up a connector

**1. Open Connectors**

Navigate to **Administration > Company Settings > Connectors**.

**2. Browse available connectors**

Scroll through the **Available Connectors** section or use the search bar and category tabs to find the connector you need.

**3. Click on the connector**

Click on the connector card to start the setup process. A configuration panel opens.

**4. Enter connection details**

Provide the required configuration — this varies by connector type but typically includes endpoint URLs, authentication credentials, and data mapping settings. You may need an [authenticator](https://knowledge.goautonomous.io/knowledge-base/administration/authenticators.md) set up first.

**5. Test the connection**

Use the test function to verify that Go Autonomous can communicate with your system before going live.

**6. Activate the connector**

Once configured and tested, activate the connector. It appears in the **Active Connectors** section at the top of the page.

## API connector category

Go Autonomous distinguishes two ideas:

* **Integration type** — which connector product you use (for example **Salesforce**, **Microsoft**, or **API**). This is fixed by how you add the connection.
* **Category** — how the platform classifies a connector instance (**CRM**, **ERP**, **File Transfer**, **Productivity**, **Custom**, and others in the backend). Category drives behaviour such as [CRM connector routing](https://knowledge.goautonomous.io/knowledge-base/administration/connectors/connector-routing.md).

When you create an **API** connector, the form shows a field labelled **Connector type**. That field sets the connector's **category** (the UI label is easy to confuse with integration type). Options:

* **CRM**
* **ERP**
* **File Transfer**
* **Productivity**
* **Custom** (the default)

Choose **Custom** for a general-purpose API integration. Choose **CRM** when this API integration should behave as a CRM connector — it can then appear in CRM routing dropdowns and be set as your primary CRM (**Set as default CRM connector**). **ERP**, **File Transfer**, and **Productivity** classify the connector for your organisation; **per-inbox ERP routing is not available in the current release**, so those values do not add ERP inbox routing like CRM does today.

> [!NOTE]
>
> This category choice is made when you create the API connector and can't be changed afterwards. If you picked the wrong value, create a new connector with the right one.

Pre-built connectors (Salesforce, SAP C4C, Dynamics Customer Service, and so on) get their category from the integration type automatically — for example Salesforce is a **CRM** connector. The category picker appears only when you create an **API** connector.

## CRM connector routing

**CRM connector routing** decides which CRM connector receives updates when requests from a sourced inbox are confirmed in Flow. You set the organisation's primary CRM on each CRM integration (**Set as default CRM connector**), and you can set a **per-inbox CRM route** or **No CRM Routing** on the [Microsoft connector](https://knowledge.goautonomous.io/knowledge-base/administration/connectors/ms-connector.md) inbox page.

See [CRM connector routing](https://knowledge.goautonomous.io/knowledge-base/administration/connectors/connector-routing.md) for where each control appears, bulk assign, runtime resolution, and troubleshooting.

## Third-party connectors

Third-party connectors allow external partners to integrate with Go Autonomous using webhooks. This is useful when a third party needs to receive data from your platform or send data back.

Key concepts for third-party connectors:

* **Webhooks** — define endpoints that receive data when events occur in Go Autonomous.
* **Data contracts** — specify the data structure that's sent to and received from the third party.
* **Logging** — third-party events are logged alongside internal events for unified troubleshooting.

> [!NOTE]
>
> Third-party connector setup requires coordination between your team and the third party. Data contracts define what information flows in each direction.

## Managing active connectors

Once a connector is active, it appears in the **Active Connectors** section. From there you can:

* View the connector's status and configuration.
* Edit connection settings.
* Deactivate the connector if it's no longer needed.
* View logs to troubleshoot issues.

## Connector guides

Step-by-step setup guides for each available connector:

> [card] [Salesforce](https://knowledge.goautonomous.io/knowledge-base/it/integration-guides/connectors/salesforce)
>
> Connect Go Autonomous to Salesforce CRM for order and quote processing.

> [card] [MS Outlook Connector](https://knowledge.goautonomous.io/knowledge-base/it/integration-guides/connectors/ms-connector)
>
> Connect Go Autonomous to Microsoft Outlook to process incoming emails.

> [card] [SAP C4C Connector](https://knowledge.goautonomous.io/knowledge-base/it/integration-guides/connectors/sap-c4c-connector)
>
> Integrate with SAP Cloud for Customer for order and quote workflows.

> [card] [Dynamics 365 Customer Service](https://knowledge.goautonomous.io/knowledge-base/it/integration-guides/connectors/dynamics-365-customer-service)
>
> Integrate with Microsoft Dynamics 365 Customer Service for order and quote workflows.

> [card] [SAML](https://knowledge.goautonomous.io/knowledge-base/administration/connectors/saml-connector.md)
>
> Configure single sign-on (SSO) for your tenant against any SAML 2.0 identity provider.

> [card] [Zendesk](https://knowledge.goautonomous.io/knowledge-base/administration/connectors/zendesk-connector.md)
>
> Connect Go Autonomous to your Zendesk instance for customer service workflows.

## What's next

* [Configure authenticators](https://knowledge.goautonomous.io/knowledge-base/administration/authenticators.md)
* [Manage organization settings](https://knowledge.goautonomous.io/knowledge-base/administration/settings)
