> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Intelbras as a data source
> Bring data from Intelbras to Nekt.
Intelbras is a leading company in security, networks, and communication solutions. This connector allows you to bring data from Intelbras access control systems into your Lakehouse, enabling you to analyze access logs and enhance your security monitoring capabilities.
## Configuring Intelbras as a Source
In the [Sources](https://app.nekt.ai/sources) tab, click on the "Add source" button located on the top right of your screen. Then, select the Intelbras 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 provide credentials to connect to your Intelbras controller.
The following configurations are available:
* **IP address**: The IP address of the controller (e.g. 192.168.1.100).
* **Port**: The port of the controller (e.g. 8080).
* **Username**: The username to authenticate against the controller (e.g. admin).
* **Password**: The password to authenticate against the controller.
* **Start Date**: The earliest date from which records will be synced.
Once you're done, click **Next**.
### 2. Select streams
Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you.
> 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 a name for each table (which will contain the fetched data) and the type of sync.
* **Table name**: we suggest a name, but feel free to customize it. You have the option to add a **prefix** and make this process faster!
* **Sync Type**: you can choose between INCREMENTAL and FULL\_TABLE.
* Incremental: every time the extraction happens, we'll get only the new data - which is good if, for example, you want to keep every record ever fetched.
* Full table: every time the extraction happens, we'll get the current state of the data - which is good if, for example, you don't want to have deleted data in your catalog.
Once you are done configuring, click **Next**.
### 4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters.
To define your [Trigger](https://docs.nekt.com/get-started/core-concepts/triggers), 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 determine when to execute a [full sync](https://docs.nekt.com/get-started/core-concepts/types-of-sync#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.
Once you are ready, click **Next** to finalize the setup.
### 5. Check your new source
You can view your new source on the [Sources](https://app.nekt.ai/sources) page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your [Catalog](https://app.nekt.ai/catalog), you need at least one successful source run.
# Streams and Fields
Below you'll find all available data streams from Intelbras and their corresponding fields:
Stream for managing access logs from the controller.
**Key Fields:**
* `RecNo` - Unique identifier for the record
* `CreateTime` - Timestamp of when the log was created
* `UserID` - ID of the user
* `CardNo` - Card number used for access
* `Door` - Door or access point identifier
* `Method` - Access method used (e.g., card, password)
* `Status` - Status of the access attempt (e.g., success, failure)
* `Type` - Type of event
* `AttendanceState` - State of attendance
* `CardName` - Name associated with the card
* `CardType` - Type of the card
* `ErrorCode` - Error code if the access failed
* `Mask` - Mask status
* `Notes` - Additional notes
* `Password` - Password used for access
* `ReaderID` - ID of the reader device
* `RemainingTimes` - Remaining access times
* `ReservedInt` - Reserved integer field
* `ReservedString` - Reserved string field
* `RoomNumber` - Room number associated with the access
* `URL` - URL related to the event
* `UserType` - Type of the user
## Use Cases for Data Analysis
This guide outlines a valuable business intelligence use case when consolidating Intelbras data, along with a ready-to-use SQL query that you can run on [Explorer](https://app.nekt.ai/explorer).
## Security Monitoring
### 1. Monitoring Access Events
Track access events to monitor who is accessing your facilities, when, and where.
**Business Value:**
* Enhance security by monitoring access in real-time
* Identify unauthorized access attempts
* Keep a historical record of all access events for auditing purposes
```sql lines theme={null}
SELECT
createtime,
userid,
cardno,
door,
method,
status
FROM
nekt_raw.intelbras_access_logs
ORDER BY
createtime DESC
```
## Skills for agents
Intelbras connector documentation as plain markdown, for use in AI agent contexts.