Skip to main content

How to integrate and send data from a bot to RD Station

Help Center
  • Updated

Index:

  1.  Installing the Blip Application on the RD Station

  2.  Using Integration

 

Follow the steps below to perform the integration between RD Station and Blip.

 

 Installing the Blip Application on the RD Station

To configure a bot on RD Station, access the Blip portal, choose the desired bot, click on the puzzle icon in the upper right corner (below your username) and then click on RD Station.

image_1.png

 

Click the Install button. After that, a pop-up will open with the RD Station page. At this point, enter your RD Station credentials, choose the account you want to connect to and click Continue.

image_2.png

Read the permissions requested by the application and click Connect.

image_3.png

 

After the installation is finished, the following page will be displayed, containing the name of your RD Station account and the id of the connected bot.

image_4.png

 

Using Integration

The integration with RD Station works through actions in the flow of your bot or through commands (HTTP or SDK). This integration allows you to create leads with detailed customer data.

 

Bot Actions

In the builder, access the block in your flow where you want to create a lead. Click Actions and then click + Add input / output action. Select the Event log option. In Category fill in the value lead, and in Action fill in the value create. Label and Value do not need to be filled out.

Your customer's data should be added as extra action information.

Click + Add extra information for each information you want to send to RD Station. In Key fill in the name of the data, and in Value fill in the value of the data (you can also use variables from the flow). Extra action information must have at least two mandatory fields: conversion_identifier and email. If any of these are not defined, the lead will not be saved.

image_5.png

Note: When the lead is generated by an event in the builder, the custom fields #stateId, #messageId and #stateName are automatically generated.

Commands

To create new lead conversions in your RD Station account, you must send an event-track command type, with the fields' category: "lead" and action: "create". The command must have at least two fields that are mandatory: conversion_identifier and email. If any of these are not defined, the lead will not be saved.

 

Example: HTTP request made to save the conversion:

Note: Use the url with the contract id to consume the endpoints reported below, its performance and operation may be impacted if it does not have the contract id, so it is essential to use the url with the contract id to use http requests! 
POST https://{{contractid}}.http.msging.net/commands

Authorization: Key YOUR-BLIP-API-KEY

HTTP/1.1 200 OK

Content-Type: application/json

{

    "id": "9494447a-2581-4597-be6a-a5dff33af156",

    "to": "postmaster@analytics.msging.net",

    "method": "set",

    "type": "application/vnd.iris.eventTrack+json",

    "uri": "/event-track",

    "resource": {

        "category": "lead",

        "action": "create",

        "extras": {

            "conversion_identifier": "9494447a-2581-4597-be6a-a5dff33af156",

            "email": "joao.silva@email.com",

            "step": "Payment",

            "conversion_time": "2020-12-04 18:45:12 +00:00"

        }

    }

}

 

Notes:

  • Do not insert repeated keys in the same command or action. If this happens, the second occurrence of the Key will be ignored as well as its respective Value;
  • The Keys' names must follow the following rules: Use alphanumeric and / or underline characters, do not use special characters and use a maximum of 64 characters;
  • If you enter the name of a field that does not exist on RD Station, Blip will create them automatically.
  • After creating a custom field in Blip, RD Station guarantees that it will be available for use within 3 hours. If your lead does not display the custom field, wait for this period and try again.
  • Only string-type fields are supported by Blip. Therefore, key tags and available_for_mailing are not supported.

For more details on the supported fields click here.

 

For more information, visit the discussion on the subject in our community or the videos on our channel. 😊

Related articles

Powered by Zendesk