Integration refers to the method of transferring data either from Nepton to another system or from another system to Nepton. The available integration methods are:
The principle of file-based SFTP transfer is that the source system generates the data on a scheduled basis and uploads it to an SFTP server. The target system then retrieves and processes the data on a separate schedule. Typically, data is transferred during nighttime, with enough buffer time between generation and retrieval to ensure the source system has completed the file.
The API integration is based on requests, where the external system calls Nepton’s API to obtain the desired information. The capabilities available via Nepton’s API are described in the following articles:
File-based SFTP transfers are more schedule-oriented and often involve transferring a larger volume of data at once (e.g. importing new personnel and updating personal information). API integrations are used when data needs to be transferred quickly and made available in Nepton immediately (e.g. importing or exporting project data).
When implementing integrations, the following operational principles should be considered:
Problem detection and resolution
Potential issues should be anticipated and handled already during the integration implementation phase.
Scheduling
Integrations operating through the SFTP server can be scheduled in Nepton. Learn more about:
- Scheduled task - Person import
- Scheduled task - Person export
- Scheduling worktime import/export integrations
Additionally, there are some near real-time integrations that run once per minute. These include integrations to phone exchange and presence systems such as:
Identification of the person being transferred
An employee number can be assigned to the individual, which is used in all transfers. If multiple identifiers are in use, a system-specific identifier can be set in the person's Employees-section. This identifier will be used for transfers related to that specific system.
The code '0' (zero) is a special code used to exclude the individual’s data from being transferred. This code should be used as the identifier only when the person's data or events are not to be transferred.
Integration user
A dedicated user account that only executes transfers must be created in Nepton. This user is granted the required permissions for the integration tasks.
To transfer personnel data, the user must have administrator rights.
To transfer worktime data, the following additional permissions may be required (depending on the type of data):
For exporting data:
Can view events of all personnel
For importing data:
Can edit and approve all users events
Can lock event dates
Can unlock locked dates
Can administer balances
Can edit approved events
Can view external identifier of events
Can edit external identifier of events
For transferring project data:
Can manage projects and project relations
Can manage persons' settings and projects
For modifying person groups, setting groups or worktime roles:
Can manage person groups
Can manage person setting groups
Can manage worktime roles