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 "Access Keys";
5) Click the "+ New key" button, give the key a name (e.g. "Kondado") and confirm the creation. The token is shown only at this moment — copy it right away, since it cannot be recovered afterwards for security reasons (the screen only lists the key's Id afterwards, not the secret; if you lose the value you will need to create a new key). Copy the full value, including the word "Key" at the beginning (format Key <code>):
ATTENTION: the token is shown only once, at the moment you create the access key. Copy the full value, including the word "Key" at the beginning, exactly as it appears in Blip — that is the text you must paste into the connector's authentication field in Kondado. Only administrators of the flow can create and manage access keys.
7) Now just paste your token obtained in step (5), name your data source and click “SAVE”.
Pipelines
Relationship chart
Tickets
| Field | Type | |
|---|---|---|
| id | text | [en] the id of the ticket |
| status | text | [en] the ticket status |
| rating | float | [en] the ticket rating for the agent |
| customerdomain | text | [en] the domain of customer |
| agentidentity | text | [en] the agent identity |
| team | text | [en] the ticket team |
| sequentialid | float | [en] the ticket sequential id |
| parentsequentialid | float | [en] the ticket sequential if when transfered |
| storagedate | timestamp | [en] the ticket creation date |
| owneridentity | text | |
| closed | boolean | [en] define if the ticket is closed |
| provider | text | [en] the name of the agent provider for ticket |
| statusdate | timestamp | [en] the date of the last status |
| externalid | text | [en] the providers ticket id |
| customeridentity | text | |
| unreadmessages | float | [en] the number of unread messages |
| opendate | timestamp | [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.
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.
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.
Navigate to Connection information
In the left sidebar of the settings page, select "Connection information" to locate your API credentials.
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.
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.
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.
