Get started
Using Nekt
- Sources
- Catalog
- Explorer
- Transformations
- Destinations
- Visualizations
- Runs
Understand
Use cases
- Overview
- Examples
Common questions
Frequently asked questions.
You probably haven’t had any successfully completed runs yet. When a source is created, the tables are already identified and created in the Catalog, but the data only becomes available once a successful run has occurred. Make sure you’ve triggered a manual run or wait for the scheduled automatic trigger. Once the run is complete, your data should be visible in the Catalog.
Access to sources, destinations, and transformations is determined by table and layer access permissions. For a member user to have a certain level X of access to a source, destination, or transformation, they must have the same level X (or higher) access to each of the tables involved. You can read more about permissions in Permissions.
No! We extract data exactly as it is sent from the APIs. So the way you see the data in Nekt is the same as you would if you used any tool to hit the endpoint and view the result. The only modifications you might notice are: column names are always standardized to snake_case, and a new column called nekt_sync_at is added for internal processing.
A Full Sync ignores previously extracted data and makes a copy of all data from the source, exactly as it exists at the time of extraction. Incremental Sync is more efficient and only fetches the data that has changed since the last extraction. Read more in Sync Types.
The use of Incremental Sync depends on the existence of a field that identifies when each record was last modified. Typically, it’s a column called “last_updated_at” or something similar. If the API doesn’t return this field, or if you didn’t specify it correctly when creating the source, Incremental Sync won’t be possible.
Although we can make some predictions based on information you provide, the best way to estimate your costs is to evaluate the cost of the first runs and extrapolate that to your expected future usage. Read more about how to monitor this in Cloud, and feel free to reach out if you have any questions!
Nekt follows industry best practices for security and privacy. We ensure that your data stays within your cloud environment, minimizing risk and maintaining control over your data.
No. Canceling your subscription won’t delete your data. It stays safely stored in your cloud environment.Also, Nekt doesn’t store your data, so everything remains in your own cloud infrastructure unless you choose to export it.
Nekt credits are used to pay for the value delivered as Nekt manages and monitors your data pipelines (1 credit = 1 minute of pipeline run time). We don’t charge for rows, number of connectors, or user seats. Failed pipelines and initial data source loads are also free.
If you selected to sync all fields when connecting the source, Nekt considers that you want everything to be synced, including new columns. In this case, the “Auto-add fields” flag will be active (you can check it on the source details screen).
Whether the new fields will be populated for all rows or just for newly imported ones depends on the sync type:
- Full sync: the new column will be filled for all rows in the table.
- Incremental sync: the new column will only be filled for newly imported rows; existing rows will have
nullin that column unless a full sync is triggered manually.
Was this page helpful?