Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

1. Description

It is designed to execute an HTTP REST request and process the result.

It integrates third-party systems (for example, Creatio, 1C).

It allows you to determine who to route the call to and receive information about the subscriber from the CRS system.

This component is present in flow types like:

  • Voice;
  • Chat;
  • Forms;
  • Service.

The block (Fig.1(1)) is used in space to build the Flow. The settings panel for this component opens (Fig.1(2)) when you click on the block.

Fig.1. HTTP Request component

1.1. HTTP Request block

The block consists of the following elements:

  1. The name of the component;
  2. in branch - receiving (connecting with the previous block) branch;
  3. out branch - outgoing (connecting with the following block) branch.

1.2. HTTP Request settings panel

It consists of the following elements:

  1. Url;
  2. Methods;
  3. Timeout;
  4. Insecure skip verify;
  5. Response Code to variable;
  6. Cookie to variable;
  7. Headers;
  8. Path;
  9. Request data;
  10. Export variables;
  11. Break;
  12. Add limit.

1.2.1. Url

Here you enter the URL address to which to make a request.

1.2.2. Methods

Here you choose the method that will be used for the request.

The following options are available:

  • Post;
  • Put;
  • Get;
  • Delete;
  • Patch.

1.2.3. Timeout

Enter the maximum time to wait for a response in this field.

1.2.4. Insecure skip verify

Responsible for the use of self-signed certificates.

- do not use;

- use.

1.2.5. Response Code to variable

Enter the variable's name in which to write the server response in this field.

1.2.6. Cookie to variable

Enter the variable's name in which to write the cookies transmitted in this field.

1.2.7. Headers

It is designed to send HTTP headers.

1.2.8. Path

It is designed to pass a variable to the URL address.

For example, it is used when it is necessary to pass caller_id_number to the link (Fig. 2).

Fig. 2. Path

1.2.9. Request data

This is where the request body is entered.

1.2.10. Export variables

It is intended to write the answer into variables and break it down into details for further analysis.

1.2.11. Break

Responsible for the completion of the flow execution.

- initiates the end of the flow execution after the given component.

- the switch is in the off position.

1.2.12. Add limit

Unable to render {include} The included page could not be found.

Fig. 3. Setting a limit

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.