"Send File" node

You can use the Send File node to transfer the files further using HTTP protocol.

Node configuration

Set up a connection

In this part of the process, you must define how you will get access to your source. By selecting the authentication method and providing required information, you establish a connection.

Select HTTPS > Send File.
Selecting the authentication method
Select the authentication method:
- No authentication - No authentication is required.
- Login & Password - This method lets you use basic authentication to authenticate with the remote server.
  Click here to see the instructions
  1. Click Select connection.
  2. 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:
    
    At the bottom of the dropdown list, click Add connection.
    
    In the Connection name field, enter the name of your connection (it’s visible only on the Select connection dropdown list).
    
    In the Login field, enter a login.
    
    In the Password field, enter the password.
    
    Click Create.
    The connection you created can be used later in other nodes and workflows.
- Custom connection - This method sends an authentication token request before executing the main request defined in the Outgoing integration node settings. The token is fetched when the request data is uncached, then cached according to its TTL, and added to the target request.

Click here to see the instructions

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.

- OAuth2 Client Credentials - This method lets you use your OAuth2 credentials to authorize.

Click here to see the instructions

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.

- API Key - This method lets you authenticate using an API secret by including it in a header of your choice or in a URL parameter — example outputs: - the authorization header: Authorization: Bearer [secret] - URL parameter: client_id=[rendered secret].
When you use this connection in the Outgoing Integration node, the token will be automatically added to either the request header or the request URL with every request.

    
Click here to see the instructions


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:

At the bottom of the dropdown list, click Add connection.
In the Connection name field, enter the name of your connection (it’s visible only on the Select connection dropdown list).
In the Secret field, enter an API Key.
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.


Click Create.

The connection you created can be used later in other nodes and workflows.

Fill out the configuration form

A blank form for the HTTP Send File node — A blank form for the HTTPS Send File node

Note: Fields marked with the

icon accept snippets or inserts. But, you can’t use profile-related inserts.

From the Method dropdown list, select the method.
In the URL field, enter the endpoint.
From the File format dropdown list, select the format of the file:
- JSON
- JSON Lines
- CSV - Provide the details on how to format the file for sending:
1. From the Delimiter dropdown, select the character that marks the end of a column.
2. From the Quotation mark dropdown list, select the characters that contain the text or data type.
3. From the Escape character dropdown lists, select the character that changes the default interpretation of a character or a string followed by the character.
4. From the Line ending dropdown list, select:
  - Line feed - This option shifts the cursor to the next line vertically.
  - Carriage return and line feed - This option points the cursor to the beginning of the line horizontally and shifts the cursor to the next line vertically.
5. Optionally, select the Quoting style only if required checkbox to wrap the values with characters selected in the Quotation mark field when the delimiter occurs in the value. For example, for the following values:
  - one
  - two,three,four
  The output with the enabled Quoting style only if required option will be as follows: one,"two,three,four"
In the Headers fields, define request headers required by the HTTP API.
Optionally, by clicking Check connection, you can verify if your connection you created in Set up a connection procedure is ready.
Confirm the settings by clicking Apply.

Examples of use

In this example, you can select a group of customers and their attributes to pass it further to the external resource (for example, Azure) by using HTTP protocol.

Add the Scheduled Run node.
In the configuration of the node, set it to immediately.
Add the Get Profiles node.
In the configuration of the node:
1. Select a segmentation of customers.
2. Select the attributes to be extracted.
3. Confirm by clicking Apply.
Click THEN, from the dropdown list, select HTTPS > Send File.
In the configuration of the node:
1. Select the authentication method.
  - If no connections are available or you want to create a new one, see Add connection.
  - If you selected an existing connection, proceed to defining the integration settings.
2. Select the method.
3. Enter the URL of the endpoint.
4. Select the format of the file.
5. Only for CSV files, verify the following fields: Delimiter, Quotation mark, Escape character, Charset, Line ending.
6. If required, enter the headers.
7. Confirm by clicking Apply.
Add the End node.

"Send File" node

Node configuration

Set up a connection

Fill out the configuration form

Examples of use

We are sorry to hear that

Awesome!