# Add a custom connector to the catalogue

A custom connector extends the catalogue so people can create connections to a service. The catalogue entry describes the service; individual connections hold the account-specific configuration and access.

## Choose the scope

A personal entry is available to its creator. An organisation-scoped entry affects what members can connect and requires the appropriate administrative authority. Confirm the intended audience before publishing an entry.

## Define the connection experience

Provide a stable catalogue identifier, readable name, description, sign-in method, and the fields users must fill. Mark credential fields as secret. For OAuth, use the configured consent flow. For tool services, identify the offered service and transport without embedding live credentials in a public definition.

A declarative HTTP records source can describe how to list records, page through results, map fields, and track an incremental watermark. Its declared base address and non-secret path parameters must match the fields users supply. This source capability does not automatically create a record-writing destination.

The exact machine-readable authoring schema and integration endpoints belong in the authenticated developer documentation. Use the Assistant to inspect and propose a supported entry when you are administering the product.

## Validate and test

Review the proposal, create the entry, then create a connection with a test account. Test the intended reads or tools and an empty page of data. A catalogue entry that looks correct is not proof that its pagination or provider permissions are correct.

## Update or remove

Changes can alter future connection setup and tool behaviour. Re-read the current entry before changing it; a stale edit needs a fresh proposal. Removing an entry stops new connections through it. Inspect existing connections and dependent processes separately rather than assuming every old resource disappeared.