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

# Business Tools

### Overview

Business tool integrations connect Transform to systems that manage customer, finance, and delivery operations.

They reduce manual duplication and keep scope, progress, and evidence consistent.

### Key Concepts

* **Source system**: system of record for an upstream dataset
* **Downstream reporting**: analytics that depends on consistent fields and status meanings
* **Connector scope**: Account or Project configuration boundary

### How It’s Used

Use business tool integrations to pull reference data and push status signals.

Use them to keep identifiers consistent across systems when cross-reporting is required.

### Benefits

* Reduced re-entry for key metadata
* More reliable stakeholder reporting
* Clearer auditability through source links

### Setup Steps

{% stepper %}
{% step %}

### Define the integration boundary

Decide whether Transform is the source of truth for:

* requirements and scope
* execution status
* testing outcomes
* delivery evidence
  {% endstep %}

{% step %}

### Configure the connector

1. Navigate to **Settings** → **Connectors**.
2. Select the connector aligned to the business tool category.
3. Authenticate using least-privilege access.
4. Configure mapping for key fields, such as owner, status, and identifiers.
   {% endstep %}

{% step %}

### Validate and monitor

1. Run a test event when supported.
2. Confirm scope alignment for Organization and Project boundaries.
3. Assign an owner for renewals and maintenance.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Keep a written mapping for fields and identifiers.
* Avoid changing status meanings after rollout.
* Use Segments for consistent reporting dimensions across Projects.

### Summary

Business tool integrations should prioritize stable identifiers, clear ownership, and consistent status meanings.

Related:

* [Connectors](/administration/connectors.md)
* [Data Sources](/integrations/data-sources.md)
* [NetSuite MCP Connector](/integrations/netsuite-mcp-connector.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/integrations/business-tools.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.