> 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/integrations/connecting-your-tools.md).

# Connecting Your Tools

Overview of integrations and where to configure them.

### Overview

Integrations connect Transform to external systems for data, notifications, and context.

Most integrations are configured through **Connectors**.

### Key Concepts

* **Connector**: configurable connection to an external system
* **Scope**: where the connector applies (Account or Project)
* **Authentication**: authorization flow used to grant access
* **Data mapping**: field alignment between systems for sync or imports

### How It’s Used

Use integrations to reduce manual re-entry and keep reporting consistent.

Use them to keep delivery evidence and decisions linked to source systems.

### Benefits

* Less duplicated work across systems
* Cleaner governance through consistent data signals
* Faster escalation through traceable sources and timestamps

### Setup Steps

{% stepper %}
{% step %}

### Define the integration goal

Common goals include:

* send notifications for mentions, assignments, or approvals
* connect data sources to reduce manual updates
* link context, such as files, meeting outputs, and evidence
  {% endstep %}

{% step %}

### Select the scope

Select the scope that matches the governance model:

* **Account** scope for shared standards across multiple Projects
* **Project** scope for one delivery initiative
  {% endstep %}

{% step %}

### Configure a connector

1. Navigate to **Settings** → **Connectors**.
2. Select the connector type.
3. Complete authentication.
4. Configure mapping and options.
5. Run a test event when available.

Related: [Connectors](/administration/connectors.md)
{% endstep %}
{% endstepper %}

### Best Practices

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

### Summary

Start here:

* [Connectors](/administration/connectors.md)
* [Project Settings and Configuration](/organizations-and-projects/project-settings-and-configuration.md)
* [Business Tools](/integrations/business-tools.md)
* [NetSuite MCP Connector](/integrations/netsuite-mcp-connector.md)
* [Data & Analytics](/integrations/data-and-analytics.md)
* [Data Sources](/integrations/data-sources.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://help.transform.ai/integrations/connecting-your-tools.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.