Blip (Take)

Based on the Blip API documentation

Adding the data source

Requirements

  • Use an account with administrator access

Instructions

1) As an administrator, login to your Blip (Take) account;

2) Once logged in, select the chatbot you want to integrate;

3) On your chatbot page, at the top right, below your name, click on the gear button to go to settings;

4) In the settings page, on the left bar, select the option of “Connection information”;

5) Now just navigate to the bottom of the page, where you will find the “HTTP Endpoints” section, copy the value of your token displayed in “Header authentication (Authorization)” including the word *Key* that is at the beginning:

BLIP_1.png

ATTENTION: It is important to copy the “Header authentication (Authorization)” field exactly as it is in the Blip, including the word Key if it is there

6) On the Kondado platform, go to the add new sources page and select the Blip (Take) data source;

7) Now just paste your token obtained in step (5), name your data source and click “SAVE”.

Pipelines

Relationship chart

Tickets

FieldType 
idtext[en] the id of the ticket
statustext[en] the ticket status
ratingfloat[en] the ticket rating for the agent
customerdomaintext[en] the domain of customer
agentidentitytext[en] the agent identity
teamtext[en] the ticket team
sequentialidfloat[en] the ticket sequential id
parentsequentialidfloat[en] the ticket sequential if when transfered
storagedatetimestamp[en] the ticket creation date
owneridentitytext 
closedboolean[en] define if the ticket is closed
providertext[en] the name of the agent provider for ticket
statusdatetimestamp[en] the date of the last status
externalidtext[en] the providers ticket id
customeridentitytext 
unreadmessagesfloat[en] the number of unread messages
opendatetimestamp[en] the ticket open date

NOTES
1. This integration refers to agent chats
2. Due to API limitations, only tickets created less than 1 month ago or with closed=false status are returned

Add Blip (Take) as a Data Source on Kondado

Connect your Blip (Take) chatbot data to Kondado by extracting the HTTP authentication token and configuring the source.

1
Access Blip with admin rights

Log in to your Blip (Take) account using an administrator account, as this permission level is required to access connection settings and tokens.

2
Select your chatbot and open settings

Choose the chatbot you want to integrate, then click the gear icon at the top right of the page (below your name) to enter the settings area.

3
Navigate to Connection information

In the left sidebar of the settings page, select "Connection information" to locate your API credentials.

4
Copy the full Authorization header token

Scroll to the HTTP Endpoints section and copy the complete "Header authentication (Authorization)" value, including the word Key at the beginning if present. This exact string is required for authentication.

5
Add Blip (Take) source on Kondado

Go to the add new sources page on the Kondado platform, select the Blip (Take) connector, paste your copied token, name the data source, and click SAVE.

6
Build pipelines to destinations

Once connected, create pipelines to send your Blip chatbot data to destinations like data warehouses, BI tools, or spreadsheets for analysis.

Frequently asked questions

What permission level do I need to connect Blip (Take) to Kondado?
You need an account with administrator access in Blip (Take). Only admin accounts can access the Connection information settings where the HTTP authentication token is located.
Where exactly do I find the authentication token in Blip (Take)?
After logging in as an admin, select your chatbot, click the gear icon for settings, choose "Connection information" in the left sidebar, then scroll to the HTTP Endpoints section. Copy the full "Header authentication (Authorization)" value, making sure to include the word Key if it appears at the beginning.
Why must I include the word "Key" when copying the Blip token?
The Blip API requires the exact Authorization header value as displayed. Omitting the word Key (if present) will cause authentication failures because the token must match the format expected by Blip's HTTP endpoints.
What Blip data can I extract through this integration?
This integration covers agent chat tickets, including fields like ticket ID, status, rating, agent identity, team, creation date, open date, unread messages, and closure status. You can view the full relationship chart and schema details on the Kondado platform.
Are there any limitations on the ticket data returned by the Blip API?
Yes, due to API limitations, only tickets created less than 1 month ago or with closed=false status are returned. Older closed tickets are not accessible through this integration.
What can I do with Blip data once it's connected to Kondado?
After connecting Blip (Take), you can build pipelines to various destinations such as data warehouses, BI tools like Google Data Studio, or spreadsheets for reporting and analytics on your chatbot performance.

Written by·Published 2023-06-05·Updated 2026-04-25