> For the complete documentation index, see [llms.txt](https://docs.brigge.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brigge.ai/documentation/brigge-for-transformers/pipelines/pipeline-nodes/connector-node.md). # Connector node

## Overview The `connector` node connects to an external [system](/documentation/brigge-for-engineers/systems.md) using saved [credentials](/documentation/brigge-for-engineers/credentials.md) to send or receive data - it's how a pipeline knows which system to contact and what request to make. To configure a connector, you select which system [credentials](/documentation/brigge-for-engineers/credentials.md) to use and an associated [endpoint](/documentation/brigge-for-engineers/systems.md) (sometimes referred to as an *operation*). Then, you can set any variables and parameters that may be defined for the selected endpoint, configure general connector behaviour, and define [error handling](#handle-errors-manually) requirements. ## Overview The *Connector* node connects to an external [system](/documentation/brigge-for-engineers/systems.md) using saved [credentials](/documentation/brigge-for-engineers/credentials.md) to send or receive data - it's how a pipeline knows which system to contact and what request to make. To configure a connector, you select which system [credentials](/documentation/brigge-for-engineers/credentials.md) to use and an associated [endpoint](/documentation/brigge-for-engineers/systems.md) (sometimes referred to as an *operation*). Then, you can set any variables and parameters that may be defined for the selected endpoint, configure general connector behaviour, and define [error handling](#handle-errors-manually) requirements. ## Configuring a connector node

*Connector* node settings are summarised below:

#	Summary
1	Credentials are the saved login details used to authenticate a system when a pipeline runs. Endpoints are the requests available to that system. Select credentials for a system to make its associated endpoints available.
2	If variables are configured for the selected endpoint, they are shown here. Depending how the variable is configured, variables might be displayed with a default value, or you can add your own. Variable values are injected to the connector request at runtime.
3	If parameters are configured for the selected endpoint, they are shown here. These are similar to variables, except parameter values are appended to the request URL. As with variables, parameter values are injected to the connector request at runtime.
4	The `timeout` setting is used to override the default number of seconds allowed before a request to this endpoint is considered failed.
5	The `maximum retries` setting determines the number of automatic retries attempted if a connection can't be made. You can define a value between `0` and `2`. The default setting is `0`.
6	The refresh icon is used to pick up any changes that have been made to the selected system while you have been configuring the connection. This can be useful if you need to make system changes 'on the fly' during pipeline setup.
7	The cog icon is used to access `advanced settings`. These are options that typically do not need to be updated regularly, and should be considered with care. For details, please see Advanced settings.

## Advanced settings ### Handle errors manually By default, if a *Connector* node fails, it automatically retries (as per your settings) and then fails if a connection can't be made. In this case - since a connection to data can't be made - the [pipeline fails](/documentation/brigge-for-operators/history-and-retries.md#investigating-a-run-failure). If you prefer to control what happens if a *Connector* node fails, access `advanced settings` and set the `handle errors manually` option to `on`:

This adds an extra 'stub' to the *Connector* node, so now you can build two paths - one for a successful connection, and one for a failed connection:

## Configuring a connector node

Connector node settings are summarised below:

#	Summary
1	Credentials are the saved login details used to authenticate a system when a pipeline runs. Endpoints are the requests available to that system. Select credentials for a system to make its associated endpoints available.
2	If variables are configured for the selected endpoint, they are shown here. Depending how the variable is configured, variables might be displayed with a default value, or you can add your own. Variable values are injected to the connector request at runtime.
3	If parameters are configured for the selected endpoint, they are shown here. These are similar to variables, except parameter values are appended to the request URL. As with variables, parameter values are injected to the connector request at runtime.
4	The `timeout` setting is used to override the default number of seconds allowed before a request to this endpoint is considered failed.
5	The `maximum retries` setting determines the number of automatic retries attempted if a connection can't be made. You can define a value between `0` and `2`. The default setting is `0`.
6	The refresh icon is used to pick up any changes that have been made to the selected system while you have been configuring the connection. This can be useful if you need to make system changes 'on the fly' during pipeline setup.
7	The cog icon is used to access `advanced settings`. These are options that typically do not need to be updated regularly, and should be considered with care. For details, please see Advanced settings.

## Advanced settings ### Handle errors manually By default, if a connector node fails, it automatically retries (as per your settings) and then fails if a connection can't be made. In this case - since a connection to data can't be made - the [pipeline fails](/documentation/brigge-for-operators/history-and-retries.md#investigating-a-run-failure). If you prefer to control what happens if a connector node fails, access `advanced settings` and set the `handle errors manually` option to `on`:

This adds an extra 'stub' to the connector node, so now you can build two paths - one for a successful connection, and one for a failed connection: