For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connectors

Connect Transform to external tools for notifications, data sync, and automation.

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

1

Open connectors

Navigate to SettingsConnectors (or Integrations).

2

Select a connector type

Select the connector aligned to the integration goal.

3

Authenticate

Complete the authorization flow.

Approve the requested permissions.

4

Configure and test

Set connector options.

Run a test event if available.

Common issue patterns:

Authentication fails
  • 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.

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.

Related:

Last updated