If you want to send data or fetch data from a third-party that WotNot does not have a native integration to, you can use the HTTP request action block. HTTP requests are executed server-side, not in the visitor’s browser. This makes the block suitable for API calls that require credentials or other sensitive request data.

Available on the PREMIUM plan and above.

When to use this

Choose the approach that best matches what you are trying to achieve.

Option	When to use	How it works
Native integration	A WotNot integration already exists for the service you need	Use the existing integration block. It is usually the simplest option because authentication and field mapping are already built in.
HTTP Request	You need to call any REST API from a flow	Configure the endpoint, method, authentication, request data, and response mapping directly in the block.
Function	The AI Agent should decide whether an API should be called	Create a function with a description that tells the AI when to use it. The function can use an HTTP Request or JavaScript handler.

Check the list of native integrations before building an HTTP Request. If the service already has a native integration, use it unless you specifically need API-level control.

Configuring the request

Add the HTTP Request action block to your flow and configure the request details.

Request

Configure the details for your API request.

Method

Select the HTTP method required by the API endpoint. WotNot currently supports:

GET — Retrieve data from an API.
POST — Send data to an API or create a resource.
PUT — Update an existing resource.

Always check the third-party API documentation to confirm which method the endpoint expects.

Endpoint URL

Enter the complete API endpoint URL. The URL must be an absolute URL beginning with http:// or https://. You can also use the variables in the URL by typing ’#’, as some APIs do not have headers and mention everything in the URL itself.

https://api.weatherapi.com/v1/current.json?key=e943b863ebed4572b55140350200312&q=#city#

Here in the above URL #city# is the variable that has been used

Headers

Add authentication data to the HTTP request. Commonly used for bearer token based authentication. You can also use variables as header values when the value needs to be determined dynamically.

Make sure you add the content-type field to your request.

Common headers include:

Header	Example value	Purpose
`Content-Type`	`application/json`	Tells the API what format the request body uses.
`Accept`	`application/json`	Indicates the response format you expect.
`Authorization`	`Bearer <token>`	Sends authentication credentials when required by the API.

Authentication

Query parameters

Query parameters are values appended to the URL after ?. For example:

https://api.example.com/customers?email=user@example.com

You can use variables as query parameter values. For example:

https://api.example.com/customers?email=#email#

If the API requires multiple parameters, separate them with &:

https://api.example.com/customers?email=#email#&status=#status#

Use query parameters for values that the API expects in the URL rather than in the request body.

Request body

Add the required information you want to send as part of your request. You can send information in two ways:

RAW

It is normal JSON format in which the request needs to be passed

FORM

It allows you to map the fields. You can either provide static value or map the variables

Enable retry mechanism

Enables automatic retries for API calls on failure, ensuring reliability by reattempting requests based on predefined conditions and intervals. After maximum retries are attempted, the flow will proceed in the failure path.

Using variables in a request

WotNot variables can be inserted into the HTTP Request configuration using the following syntax: #variable_name# For example, if your flow contains a variable named customer_id, reference it as: #customer_id#

Variable in the URL

https://api.example.com/customers/#customer_id#

Variable in a header

X-Customer-ID: #customer_id#

Variable in the request body

{
  "customer_id": "#customer_id#",
  "email": "#email#"
}

When the request runs, WotNot resolves the variable and sends its stored value to the API. For more information about creating and using variables, see the Variables page.

Handling the Response

When the HTTP request is made, you will receive a response from the API. You can store the objects received from the API into variables by mapping the fields.

// Object path for storing the response into variable where list is returned

result.data.list[0].id

// Here the value of the field `id` will be stored in the variable mapped to it.

// Object path for storing the response into variable where single value is returned

result.data.id 

// Here the value of the field 'id' will be stored in the variable mapped to it.

Worked examples

GET request with a query parameter

Use a GET request when you need to retrieve data based on information collected during the conversation.

Example

Suppose the visitor provides their customer ID, stored in:

customer_id

Configure the request as follows.Method

GET

URL

https://api.example.com/customers?customer_id=#customer_id#

Headers

Accept: application/json

Example response

{
  "data": {
    "customer": {
      "id": "CUS-1024",
      "name": "John Doe",
      "status": "active"
    }
  }
}

Store the response

To save the customer’s name:

result.data.customer.name

To save the customer’s status:

result.data.customer.status

You can then use these variables in subsequent blocks.

POST request with JSON body and bearer authentication

Use a POST request when you need to send information to an API.Suppose the flow collects:

customer_name
email
phone

Method

POST

URL

https://api.example.com/customers

Headers

Content-Type: application/json
Accept: application/json
Authorization: Bearer your_access_token

Raw body

{
  "name": "#customer_name#",
  "email": "#email#",
  "phone": "#phone#"
}

When the request executes, WotNot replaces the variables with the values collected during the conversation.

Example response

{
  "data": {
    "customer_id": "CUS-1024",
    "created": true
  }
}

To store the customer ID:

result.data.customer_id

You can use the resulting variable in later blocks.

Authenticated lookup followed by a Condition block

Use this pattern when the flow needs to look up information and then take a different path depending on the API response.Suppose you want to check whether a customer’s account is active.

HTTP Request

Method

GET

URL

https://api.example.com/customers/#customer_id#

Headers

Accept: application/json
Authorization: Bearer your_access_token

Example response

{
  "data": {
    "customer": {
      "id": "CUS-1024",
      "status": "active"
    }
  }
}

Map the response field:

result.data.customer.status

Store it in a variable such as:

customer_status

Condition

Add a Condition block after the HTTP Request.Configure the condition as:

customer_status equals active

Then create two paths:If trueContinue with the flow for an active customer.If falseShow an appropriate message or route the visitor to an alternative flow.This pattern lets the API determine what happens next without exposing the API details to the visitor.

Testing API request

Once you have configured your API request, you can click on the ‘Test the API’ button and see the response received. From the response screen, you can directly save the object into a variable by clicking on the + icon.

API Retry Logs

Track each HTTP Request retry logs separately to easily understand the status and outcome of every API attempt. Each log entry includes the status, retry number, request details, response or error, and execution timestamp. View retry logs from: App Market → HTTP request → Logs

Troubleshooting

I receive a 401 Unauthorized response

A 401 response generally means that the API did not accept the authentication information.Check the following:

The API key or access token is correct.
The authentication header name is correct.
The Authorization header uses the format required by the API.
A Bearer prefix is included when required.
The token has not expired.
The API endpoint expects the authentication method you configured.

Test the same credentials using the API documentation or an API client to confirm that they are valid.

I receive a 403 Forbidden response

A 403 response means that the request was understood, but the API is refusing access.Check the following:

The API credential has permission to access the endpoint.
The required API scope or role is enabled.
The account has access to the requested resource.
The third-party service does not restrict requests by IP address.

If the API uses IP allowlisting, ask the API provider which source IP addresses must be allowlisted for server-side requests from WotNot.

My variables are being sent literally

If the API receives:

#customer_id#

instead of the actual value, check the variable reference.WotNot variables use the following format:

#variable_name#

For example:

https://api.example.com/customers/#customer_id#

Also confirm that the variable has a value before the HTTP Request block runs.

A nested response value is not mapping

Check the response returned by Test the API and make sure the object path exactly matches the response structure.For example, for:

{
  "data": {
    "customer": {
      "id": "CUS-1024"
    }
  }
}

the correct object path is:

result.data.customer.id

Do not use a path based only on the API documentation if the actual response returned by the endpoint has a different structure.For arrays, include the required index. For example:

result.data.customers[0].id

The request succeeds but the flow does not continue

First, use Test the API to confirm that the request returns the expected response.Then check the following:

The HTTP Request block has completed successfully.
The next block is correctly connected in the flow.
A subsequent Condition does not depend on a variable that was not populated.
The response mapping uses the correct object path.
The API response matches the response structure you used while testing.

If the request succeeds but a mapped variable is empty, inspect the response and verify the mapping path.

The request is timing out

A timeout can occur when the third-party API takes too long to respond.Check the following:

The API endpoint is responding normally.
The endpoint is not experiencing an outage or performance issue.
The request is not waiting on another downstream service.
The request body or query is not unnecessarily large.
The API is not subject to rate limits or processing delays.

Test the endpoint independently using the same URL, headers, parameters, and body to determine whether the delay originates from the API.

Note: Do not document a specific WotNot timeout or automatic retry interval unless it has been confirmed for your current WotNot environment.

The customer's API uses IP allow listing

Some enterprise APIs only accept requests originating from approved IP addresses.If your customer’s API uses IP allowlisting, confirm which outbound IP addresses must be allowlisted for WotNot server-side HTTP requests.If the customer’s security team requires a fixed WotNot egress IP, contact WotNot Support to confirm the currently supported configuration for your account or environment.

Getting started

Build

Operate

Deploy

Reports

Account

HTTP request/API

When to use this

Configuring the request

Request

Method

Endpoint URL

Headers

Authentication

Query parameters

Request body

RAW

FORM

Enable retry mechanism

Using variables in a request

Variable in the URL

Variable in a header

Variable in the request body

Handling the Response

Worked examples

Example

Example response

Store the response

Method

URL

Headers

Raw body

Example response

HTTP Request

Example response

Condition

Testing API request

API Retry Logs

Troubleshooting

​When to use this

​Configuring the request

​Request

​Method

​Endpoint URL

​Headers

​Authentication

​Query parameters

​Request body

RAW

FORM

​Enable retry mechanism

​Using variables in a request

​Variable in the URL

​Variable in a header

​Variable in the request body

​Handling the Response

​Worked examples

​Example

​Example response

​Store the response

​Method

​URL

​Headers

​Raw body

​Example response

​HTTP Request

​Example response

​Condition

​Testing API request

​API Retry Logs

​Troubleshooting

When to use this

Configuring the request

Request

Method

Endpoint URL

Headers

Authentication

Query parameters

Request body

Enable retry mechanism

Using variables in a request

Variable in the URL

Variable in a header

Variable in the request body

Handling the Response

Worked examples

Example

Example response

Store the response

Method

URL

Headers

Raw body

Example response

HTTP Request

Example response

Condition

Testing API request

API Retry Logs

Troubleshooting