Configuring Pleno as a Source
In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Pleno option from the list of connectors. Click Next and you’ll be prompted to add your access.1. Add account access
You’ll need to authorize Nekt to access your Pleno data using your API credentials. Click here to check Pleno’s documentation to learn how to generate these values. For more details on the API behavior, check the Pleno API Postman workspace. The following configurations are available:- Client ID: Client ID is seen once on the platform when an API Key is generated. This field is required.
- Client Secret: Client Secret is seen once on the platform when an API Key is generated. This value is stored securely and is never displayed after saving. This field is required.
2. Select streams
Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.Tip: The stream can be found more easily by typing its name.Select the streams and click Next.
3. Configure data streams
Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a name for each table (which will effectively contain the fetched data) and the type of sync.- Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
- Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
- Sync Type: depending on the data you are bringing to the lake, you can choose between INCREMENTAL and FULL_TABLE. Read more about Sync Types here.
4. Configure data source
Describe your data source for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings (if available):- Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
- Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
5. Check your new source
Click Done to finalize the setup. Once completed, you’ll receive confirmation that your new source is set up! You can view your new source on the Sources page. Now, for you to be able to see it on your Catalog, you have to wait for the pipeline to run. You can monitor it on the Sources page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your new table will appear in the Catalog section.If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!
Streams and Fields
Below you’ll find the available data streams from Pleno.Edifício
Edifício
Stream containing records of buildings (edifícios) registered in the platform.
Estados
Estados
Stream containing data regarding state/status mappings in the system.
Imóveis
Imóveis
Stream containing property (imóveis) management data.
Tipo Funções
Tipo Funções
Stream containing configuration data about function types (tipo funções).
Tipo Imóvel
Tipo Imóvel
Stream containing configuration data about property types (tipo imóvel).
Tipo Vistoria
Tipo Vistoria
Stream containing configuration data about property inspection types (tipo vistoria).
Vistorias
Vistorias
Stream containing detailed property inspection records (vistorias), tracking operational and inspection activity.
Skills for agents
Download Pleno skills file
Pleno connector documentation as plain markdown, for use in AI agent contexts.