Send triggered message webhook 

The "Send triggered message webhook" action allows you to send data related to the customer's message that triggered their flow enrollment to an external system. 

Prerequisites for using this node are:

• The trigger node is one of the following
  • Incoming message received
  • Outgoing message sent
  • Incoming message from Click-to-WhatsApp (CTWA) ad
• The external system is able to receive incoming webhooks from SleekFlow

Set up "Send triggered message webhook " action node

1. Click on the Send triggered message webhook action node to open up its form, which will appear on the right side of the screen

2. The node form contains the following fields for you to configure in order for SleekFlow to send the webhook payload data of the triggered message to your external system:

• Setup tab
  • URL: Input the webhook URL provided by the external system you want to send the data to
  • Header: Enable this to provide any additional data required by the webhook through the request header. Please refer to your external system's webhook documentation to see if any additional data needs to be passed through the request header of your webhook.
  • Preview payload: You see a sample of the contact payload and its parameters that would be sent to your external system’s webhook, the payload’s data structure will be in JSON syntax

Send contact webhook 

The "Send contact webhook" action allows you to send data related to the contact enrolled in the flow to an external system. A prerequisite for using this node is that the external system must be able to receive incoming webhooks from SleekFlow.

Set up "Send contact webhook " action node

1. Click on the Send contact webhook action node to open up its form, which will appear on the right side of the screen 

2. The node form contains the following fields for you to configure in order for SleekFlow to send the webhook payload data of the enrolled contact to your external system:

• Setup tab
  • URL: Input the webhook URL provided by the external system you want to send the data to
  • Header: Enable this to provide any additional data required by the webhook through the request header. Please refer to your external system's webhook documentation to see if any additional data needs to be passed through the request header of your webhook. 
  • Preview payload: You see a sample of the contact payload and its parameters that would be sent to your external system’s webhook, the payload’s data structure will be in JSON syntax

Send HTTP request 

The "Send HTTP request" action allows you to send and/or receive data between SleekFlow and the API of your external system. A prerequisite for using this node is that the external system must offer a publicly available API to enable integration with SleekFlow.

Set up the "Send HTTP request" action node form by following the steps outlined below:

1. Set up the HTTP request
2. Configure the HTTP request body
3. Configure response persistence from HTTP response

Set up “Send HTTP request” action node 

1. Click on the Send HTTP request action node to open up its form, which will appear on the right side of the screen

2. The node form contains the following fields for you to configure in order for SleekFlow to interact with your external system to send and/or fetch data:

• Setup tab
  • Method: Specify the HTTP method that the API of your external system expects. 
    • GET: Choose "GET" to request data from the API of the external system
    • POST: Choose "POST" to send data from SleekFlow to the external system via its API
    • PUT:  Choose "PUT" to update or replace existing data in your external system via its API
    • DELETE: Choose "DELETE" to remove existing data from your external system via its API

• URL: Input the URL to access the API of your external system and its various functions
• Headers: Configure the required header key-value pairs of the HTTP request to access the API
• Query string: Configure the required query string key-value pairs to access the API

• Handle error: Toggle this on to set up a fallback path whenever an HTTP request fails. When enabled:
  • An additional branch will appear in the flow, specifically for failed requests
  • You can configure this branch to define what should happen when the request cannot be completed, for example, sending an error message

Configure the HTTP request body

The "Body" section of the node form allows you to configure the data and content type to be sent by the HTTP request to the API server of the external system. Refer to the API documentation of your external system for the specific configuration and parameters required for the integration.

This section has the following fields which you can configure:

• Body type: Specify the body type that the API of your external system accepts. You can configure the content type with the options outlined in the table below:

Body type	Description
raw	Choose the raw body type if your API receives plain text, JSON, or string data.  Specify the content type that your API server accepts, either Text (text/plain), JSON (application/json), XML (application/xml), HTML (text/html), or XML (text/xml)   You can input the data into the dark blue request content box with the content type's syntax
Form-data or x-www-form-urlencoded	Choose the body type that meets the requirement of your API and enter the request content data as key-value pairs      If you have more than one set of key-value pair data to append, click on “+ Add set” to add another key-value pair set

Configure response persistence from HTTP response

After you’ve set up your HTTP request, you can now parse API responses directly from the variable tab. This makes it easier to extract specific data fields from your external system and use them later in your flow without manually writing JSON paths.

How to parse API responses

1. Go to the Variable tab in the Send HTTP request node form
2. Paste a sample response payload from your external system into the input box.
3. Click Parse data.
4. SleekFlow will analyze the payload and automatically detect all available fields within the response
5. Once parsed, these fields will become variables that you can:
   • Insert into outgoing messages 
   • Use as conditions for branching or routing contacts
   • Save for later reference in subsequent action nodes