Click Select connection.
If the connection you want to use is in the list, select it and proceed to Filling out the configuration form.
- If the connection list is empty or you don't see a connection, you must:
  1. At the bottom of the dropdown list, click Add connection.
  2. In the Connection name field, enter the name of your connection (it's visible only on the Select connection dropdown list).
  3. In the Login field, enter a login.
  4. In the Password field, enter the password.
  5. Click Create.
    The connection you created can be used later in other nodes and workflows.

Click Select connection.
In the connection list:
- If the connection you want to use is in the list, select it and proceed to Defining the request section in this article.
- If the connection list is empty or you don't see a connection, you must:
  1. At the bottom of the dropdown list, click Add connection.
  2. In the Authorization request tab, click Define.
    Result:
    
    The Request section in the configuration of a custom connection
  3. In the Connection name field, enter the name of your connection (it's visible only on the Select connection dropdown list or on the list of connections in Settings > Connections).
  4. In Secret, enter a value which is required in the request to obtain a token. This value will be anonymized and displayed as asterisks.
  5. In the Headers section, add request headers (in the left field, enter the key; in the right, enter its value).
  6. In the Body field, enter the request body.
    For example:
```
{ "api-key": "{{secret}}" }
```
    where {{secret}} retrieves the value of the Secret field to anonymize the token.
  7. Confirm the settings in the Authorization request tab by clicking Apply.
  8. In the Token placement settings section, click Define.
  9. Click Retrieve response.
    Result:
    
    Retrieved token in the Response section in the custom connection configuration form
  10. If you:
  - specify the value in the Headers section, the extracted authorization data from the response will be added as a header to the target request.
  - provide the value in the URL Parameters section, the data will be appended to the target request’s URL as a parameter.
    You can use the following values to retrieve values from the response:
    - authResponseBody - a variable that contains the full body of an authentication response
    - authResponseStatusCode - a variable that contains the status code of an authentication response
    - authResponseHeaders- a variable that contains the headers of an authentication response
      For example:
```
Bearer {{ authResponseBody | fromjson | attr("token") }}
```
    It takes the JSON response body stored in authResponseBody, parses it into a usable structure, and extracts the value of the token field. Outputs a string like: Bearer "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
  1. In TTL field, specify the how long the cached response from the external request will be valid.
    If you leave this field empty, it's 60 seconds.
  2. Confirm by clicking Apply.

Click Select connection.
If the connection you want to use is in the list, select it and proceed to Filling out the configuration form.
- If the connection list is empty or you don't see a connection, you must:
  1. At the bottom of the dropdown list, click Add connection.
  2. In the Connection name field, enter the name of your connection (it's visible only on the Select connection dropdown list).
  3. From the API key dropdown, select the API key.
  4. Click Create.
    The connection you created can be used later in other nodes and workflows.

Click Select connection.
In the connection list:
- If the connection you want to use is in the list, select it and proceed to Filling out the configuration form.
- If the connection list is empty or you don't see a connection, you must:
  1. At the bottom of the dropdown list, click Add connection.
  2. In the Connection name field, enter the name of your connection (it's visible only on the Select connection dropdown list).
  3. In the Token endpoint URL field, enter the URL used to obtain an access token from the authorization server.
  4. In the Client ID field, enter a unique identifier assigned to your application by the service provider.
  5. In the Client secret field, enter a confidential key issued alongside the Client ID. It is used to securely authenticate your application.
  6. Optionally, in the Scope field, define the level of access your application is requesting. Scopes specify which actions or data your application can access (for example, read user data, send messages). Refer to the API documentation for the correct scope values.
  7. Click Create.
    The connection you created is saved and can be used later in other nodes and workflows.

Click Select connection.
If the connection you want to use is in the list, select it and proceed to Defining the request section in this article.
- If the connection list is empty or you don't see a connection, you must:
  1. At the bottom of the dropdown list, click Add connection.
  2. In the Connection name field, enter the name of your connection (it's visible only on the Select connection dropdown list).
  3. In the Secret field, enter an API Key.
  4. If you:
    - specify the value in the Headers section, the API key will be added as a header to the request. For example, x-api-key: {{secret}} where {{secret}} retrieves the value of the Secret field to anonymize the API key value.
    - provide the value in the URL Parameters section, the API key will be appended to the request’s URL as a parameter.
  5. Click Create.
    The connection you created can be used later in other nodes and workflows.