
Configuring Nekt as a Source
In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Nekt option from the list of connectors. Click Next and you’ll be prompted to add your access.1. Add account access
You’ll need the following credentials from your Nekt account:- API Key: Your personal API key for accessing the Nekt API. You can generate one in your Nekt workspace settings under the “API Keys” section. Make sure the key has the necessary permissions to read the data you want to sync.
- Start Date: The earliest record date to sync. Only records created or updated after this date will be synced.
- Include deleted items (default:
false): Include deleted records in the sync, alongside the active ones. Applies to theSources,TransformationsandDestinationsstreams, where deleted records can be identified by thedeletedfield. Requires an API key created by an owner or an admin: if the key was created by a member, the sync will fail while this option is enabled.
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 the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will 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.
- Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
- 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: 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.
4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters. 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:- 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
You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.Streams and Fields
Below you’ll find all available data streams from Nekt and their corresponding fields:Sources
Sources
Stream containing all data sources configured in your Nekt workspace.
Runs
Runs
Stream containing all pipeline execution runs in your Nekt workspace.
Destinations
Destinations
Stream containing all data destinations configured in your Nekt workspace.
Transformations
Transformations
Stream containing all data transformations configured in your Nekt workspace.
Activities
Activities
Stream containing all audit activities and changes in your Nekt workspace.
Source Triggers
Source Triggers
Stream containing trigger configurations for data sources. Triggers are fetched per source; when Include deleted items is enabled, deleted sources are skipped because their nested endpoints are no longer available.
Destination Triggers
Destination Triggers
Stream containing trigger configurations for data destinations. Triggers are fetched per destination; when Include deleted items is enabled, deleted destinations are skipped because their nested endpoints are no longer available.
Users
Users
Stream containing all users configured in your Nekt organization.
Data Model
The following diagram illustrates the relationships between the core data streams in Nekt. The arrows indicate the join keys that link the different entities, providing a clear overview of the data platform structure.Use Cases for Data Analysis
Here are some valuable business intelligence use cases when consolidating Nekt platform data, along with ready-to-use SQL queries that you can run on Explorer.1. Daily Credits Consumption per Pipeline
Monitor credit consumption for each pipeline in a daily basis. Business Value:- Track pipeline credit consumption
- Analyze resource utilization and make future projections
- Identify pipelines that can be optmized
SQL code
SQL code
2. Data Source Performance and Reliability Analysis
Monitor data pipeline performance, execution times, and failure rates across your data sources. Business Value:- Track pipeline execution trends and identify performance bottlenecks
- Monitor data pipeline reliability and uptime
- Analyze resource utilization and optimize infrastructure costs
- Identify sources that need attention
SQL code
SQL code
3. User Activity and Platform Usage Analysis
Track user engagement, platform adoption, and operational activities across your Nekt workspace. Business Value:- Monitor platform adoption and user engagement
- Identify power users and training needs
- Track operational patterns and peak usage times
- Optimize team collaboration and workflow efficiency
SQL code
SQL code
Skills for agents
Download Nekt skills file
Nekt connector documentation as plain markdown, for use in AI agent contexts.