> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/administration/connectors.md).

# Connectors

### Overview

Connectors link Transform to external systems.

They support notifications, data movement, and context linking.

### Key Concepts

* **Connector**: configured integration to an external system
* **Scope**: Account or Project boundary for connector settings
* **Authentication**: authorization flow used to grant access
* **Mapping**: field alignment between systems for sync or imports
* **Test event**: validation step that confirms configuration

### How It’s Used

Use connectors to reduce manual updates and keep reporting consistent.

Use them to route notifications and link delivery evidence back to source systems.

### Benefits

* Less duplicated work across systems
* More reliable governance signals
* Faster issue triage through traceable sources

### Setup Steps

{% stepper %}
{% step %}

### Open connectors

Navigate to **Settings** → **Connectors** (or **Integrations**).
{% endstep %}

{% step %}

### Select a connector type

Select the connector aligned to the integration goal.
{% endstep %}

{% step %}

### Authenticate

Complete the authorization flow.

Approve the requested permissions.
{% endstep %}

{% step %}

### Configure and test

Set connector options.

Run a test event if available.
{% endstep %}
{% endstepper %}

Common issue patterns:

<details>

<summary>Authentication fails</summary>

* Confirm the correct external account is used for authentication.
* Confirm pop-ups are not blocked by the browser.
* Request access from an Account Admin when connector configuration is restricted.

</details>

### Best Practices

* Use least-privilege access for authentication.
* Assign an owner for renewals and maintenance.
* Test in a pilot Project before broader rollout.
* Keep field mappings stable to protect reporting continuity.

### Summary

Connectors support notifications, data movement, and context linking.

For ERP connector setup using MCP, see [NetSuite MCP Connector](/integrations/netsuite-mcp-connector.md).

Related:

* [Connecting Your Tools](/integrations/connecting-your-tools.md)
* [Project Settings and Configuration](/organizations-and-projects/project-settings-and-configuration.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://help.transform.ai/administration/connectors.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.