PostgreSQL for Blip

Index:

1. Introduction
2. How it works?
3. Installation and Configuration
4. User manual
5. Dependencies
6. Terms of Use
7. Support

 

Introduction

The PostgreSQL for Blip extension was developed by the Sharkdev company. Currently, it is in version 1.0.0 and available for subscription and use.

 

PostgreSQL for Blip is here to make the life of devs who need to connect to a PostgreSQL database easier. No intermediate API! Now you can rely on PostgreSQL for Blip 😍.  With this extension, you connect Blip to your PostgreSQL database by providing the connection details and can start using it in the Builder. It's easy and quick! Let's do it!

 

This manual aims to assist users of the Blip platform in the installation, configuration, and use of the PostgreSQL for Blip extension.

How it works?

The PostgreSQL for Blip extension was developed with the aim of allowing developers to access databases directly through the builder, without the need for an intermediate API.
The following features are offered:

• Connection to your own database;
• Execution of SQL statements in the database through HTTP requests;
• Viewing SQL statements executed in the database in the last 30 days;

 

Installation and Configuration

To use the PostgreSQL for Blip extension, it is necessary to access the contract to which you want to install it and then access the Router bot. After that, navigate to the extensions section where the Blip Store will be opened, and search for "PostgreSQL for Blip". Once found, you will need to activate it and install it.

After activated, installed, and with terms accepted, a small configuration is necessary for you to start using it, follow the step by step below.

 

Step 1) Connecting to the database

On the main page of the extension, enter name, host, port, user, password, and SSL in the connection form and click "Connect".

 

If the connection is successful, you will quickly see the message "Database connected". If unsuccessful, we suggest reviewing the connection data filled in the form.

 

Step 2) Set token in bot configuration variables

For your bot to be able to use the extension, it's necessary to provide the authorization token at the time of the request.

Therefore, we suggest that 

 

 

* This step is not mandatory, but it's a suggestion aimed at maintaining Intelligent Contact.

 

Step 3) Now just use it!

In this step, the extension is configured and you can already use it. To do so, familiarize yourself with the concept of commands in the "User Manual".

 

User manual

SQL Instructions

Follow the instructions below to communicate with the extension via Builder:

Basic data

Base URL: https://postgresqlforblip.blip.sharkdev.com.br/query

Authorization token: {{config.token}} or Authentication Header (Authorization)

How to execute a command

To execute a command, configure an HTTP Request, using the POST method, to the URL provided in Base URL, providing the Authorization token in the "Authorization" key of the Header. To make it easier, see the image below:

 

 

Now, you need to define the Body of the request. To do this, the JSON sent must follow the attributes below:

 

 

Dependencies

For this extension to work correctly, it is necessary to contract it through the Blip Store accessing Blip through a paying account. In addition, the use of its own database is required.

 

Terms of Use

• The database accessed through this application belongs exclusively to the client;
• Request history to the database will be accessible for 30 days;
• SharkDev does not claim any ownership rights over the data stored in the client's database;
• Access data to the database (such as passwords, tokens, or authentication keys) are securely stored in our internal database;
• The client is responsible for configuring and managing the access levels of the database users;
• The client is solely responsible for the data trafficked, stored, or returned from the database;
• SharkDev assumes no responsibility for loss, corruption, or misuse of this data;
• We reserve the right to update or modify these Terms at any time;
• SharkDev is not responsible for the sharing of authentication keys to Blip when disclosed by the client;
• All information conveyed will be treated with absolute secrecy and confidentiality, solely and exclusively within your Blip environment and in accordance with the General Data Protection Law (Law No. 13,709/2018 - LGPD).

 

Support

If you have any questions or encounter any problems with the extension, please contact us via email blippartner@sharkdev.com.br or at +55 (35) 98802-9321.

 

For more information, visit the discussion on this topic in our community or watch the videos on our channel. 😃