# Catalog connectors and connected accounts

> Source: https://docs.clonepartner.com/connectors/catalog-and-connected-accounts/

Envoy exposes connector types enabled in the deployed build. Some types are built into the binary; others are generated from an approved connector catalog. A connector record supplies the environment-specific configuration for one type.

Tasks refer to connector slots, not connector record IDs or credentials.

## Built-in and catalog types

The connector picker reports every available type and its configuration schema. Common built-in categories include:

- databases such as SQLite, PostgreSQL, MySQL, Microsoft SQL Server, and MongoDB;
- files such as CSV and YAML;
- object stores such as Amazon S3 and Azure Blob Storage;
- application connectors such as Truto, Dynamics 365, Jira, and Freshdesk;
- catalog-powered connectors included for a particular deployment.

Availability varies by build. If a task bundle requires an unavailable type, ask the deployment administrator to include it; renaming the connector type does not make the task compatible.

## Create a connector

1. Open **Connectors** and choose **New connector**.
2. Select the type.
3. Enter a name that describes the account and environment.
4. Complete the generated configuration form.
5. Store secret values through the supported secret input.
6. Save and run the available connection or discovery test.

Use separate connector records for production and test accounts. A task can bind to either record without changing its YAML.

## Connected accounts

Some catalog connectors distinguish the connector's provider configuration from a connected account selected within that provider. In those cases:

- the connector record stores the provider-level endpoint and authentication;
- discovery lists connected accounts;
- a task or template argument stores the selected account ID;
- each connector call passes that ID explicitly.

The selected ID is not a credential, but it is environment-specific. Use [template arguments](/guides/template-arguments) when it should be fixed at job creation.

## File-backed connectors

Supported connectors can upload files through the connector editor. Use the returned managed path or resource identifier in task configuration.

In container deployments, paths must be visible inside the control-plane and executor containers. Do not document or rely on a workstation path that is not mounted into the deployment.

Uploaded files can contain customer data. Apply the same retention, access, and backup controls as other source data.

## Introspection and option discovery

Connector-backed pickers and Data Explorer use introspection methods to list resources, fields, accounts, or options. Large lists must be searched and paged on the server.

Discovery is not a write path. Do not configure option sources with methods that mutate the external system.

## Promotion between environments

Task and job-template bundles contain connector slot names and types, not connector records or secrets. On the target:

1. verify required connector types are available;
2. create target connector records;
3. test network access and permissions;
4. create or upgrade the job;
5. bind template connector names to target records;
6. run a bounded validation.

Never export credentials as part of a documentation or bundle workflow.

See [Connector reference](/reference/connectors) and [Truto connector](/connectors/truto).