Skip to content
Book a demoStart free
Connectors

Nepton connector

Set up the Nepton connector in Kaivo: authentication, configuration, the 3 BigQuery tables it syncs, and answers to common questions.

Nepton connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Nepton data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your HR data instead of moving it.

Sync your Nepton workforce and time data into BigQuery with Kaivo to report on hours, attendance, and absences alongside the rest of your data.

CategoryHR
AuthenticationUsername and password
SetupSelf-service
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Nepton account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Connect with your Nepton login. You provide:

Field Description
Password
The login password of the authenticating account.

|

When you set up the connector, you provide:

Field Description
Customer ID
Contact Nepton Customer Service to obtain this value.

| | Username |

The login username of the authenticating account.

|

Kaivo syncs 3 tables from Nepton into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

activities (48 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
id INT64
user_id INT64
user_first_name STRING
user_last_name STRING
user_username STRING
user_personnel_number STRING
activity_type_id INT64
activity_type_name STRING
activity_type_category_id STRING
activity_type_category_name STRING
approver_user_id INT64
approver_first_name STRING
approver_last_name STRING
approver_personnel_number STRING
begin_date_time TIMESTAMP
end_date_time TIMESTAMP
modified_date_time TIMESTAMP
modified_by_user_id INT64
modified_from_ip STRING
comment STRING
is_clocked_event BOOL
is_created_with_pin_code BOOL
overtime_base_part_targeted_to STRING
overtime_increment_part_targeted_to STRING
absence_details__compensation_type_id INT64
absence_details__compensation_type_name STRING
absence_details__earns_vacation_days BOOL
absence_details__absence_type_id INT64
absence_details__absence_type_name STRING
planned_work_details__planned_work_calculation_unit STRING
planned_work_details__planned_work_color STRING
planned_work_details__planned_work_use_for_work_day_length_calculations BOOL
planned_work_details__planned_work_can_be_cancelled_until STRING
planned_work_details__planned_work_work_time_limit_offset_start_in_mins INT64
planned_work_details__planned_work_work_time_limit_offset_end_in_mins INT64
planned_work_details__assumed_lunch_in_minutes INT64
planned_work_details__planned_work_activity_group_public_info STRING
sick_leave_details__compensation_type_id INT64
sick_leave_details__compensation_type_name STRING
sick_leave_details__earns_vacation_days BOOL
sick_leave_details__sick_leave_type_id INT64
sick_leave_details__sick_leave_type_name STRING
sick_leave_details__medical_certificate_given BOOL
sick_leave_details__supervisors_permission BOOL
sick_leave_details__reason_code STRING
external_identifiers JSON
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
id INT64
duration INT64
name STRING
code STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
index INT64
value FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
activity_types (11 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
id INT64
internal_name STRING
code STRING
visible BOOL
can_assign_work_increments BOOL
can_have_related_projects BOOL
category_internal_name STRING
begin_date_time_input STRING
end_date_time_input STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
projects (12 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
id INT64
name STRING
deleted BOOL
code STRING
type_internal_name STRING
description STRING
start_date DATE
end_date DATE
parent_project_id INT64
parent_project_code STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Nepton supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.

How long does the initial sync take for Nepton?

Section titled “How long does the initial sync take for Nepton?”

It depends on how much history is in your Nepton account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.

What happens when Nepton’s schema changes?

Section titled “What happens when Nepton’s schema changes?”

New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Nepton, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Nepton instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Nepton connector in Kaivo and all of its synced data is deleted with it.

Track worked hours and attendance by employee and over time.

Analyse absences and leave to monitor patterns and coverage.

Report on time by project or cost centre to support billing and planning.

Bring time data alongside payroll or finance data in BigQuery for a full view.

Once Nepton data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Nepton data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Nepton connector pricing and plan details.