​
Available Integration Types

  • HRMS Integration
  • Upload CSV Integration
  • Via SFTP Integration
  • Push API Integration
  • Custom Integration

​
HRMS Integration

Tartan offers seamless HRMS integration with over 80+ HRMS platforms, ensuring that no matter which system your client organization uses, you’ll receive data in a consistent and unified format. Tartan offers two types of HRMS integrations: Automated and Assisted.

​
Automated HRMS Integration

With Automated Integration, users can quickly connect by providing API credentials such as an API key or token. Once authenticated, Tartan will initiate an initial data sync for all or selected employees. Afterward, data will sync automatically at a frequency of your choice (defaulting to every Monday at a set time). If you require more frequent updates, you can easily adjust the sync frequency directly from our console.

​
Assisted HRMS Integration

Assisted Integrations are a unique offering from Tartan, where we enable connectivity with your client organisation’s HRMS within just 1 week, once we receive the necessary API documentation from you. Refer below table below to understand the main differences between the Automated and Assisted integrations.
Automated IntegrationAssisted Integration
Coverage30+50+
Default Data SyncWeeklyMonthly
On demand SyncYesYes
Setup period0 Days7 Days
Steps to build an HRMS Integration:
1

Invite your client organisation

Your client admin receives an email to login to the Tartan console (whitelabeled).
2

Client admin selects their HRMS

Your client admin selects their HRMS from the list of supported HRMS platforms.
3

Client admin provides API credentials

Your client admin enters the API credentials of their HRMS. If they don’t have them, they can refer to the documentation attached on the same screen.
4

Client admin selects data models

Your client admin selects the specific data points they wish to share with you across various data models, such as employee details, dependent information, salary data, bank details.
5

Client admin completes the journey

Finally, the client admin clicks ‘Submit,’ triggering the initial data sync.

​
Upload CSV Integration

If your client organization doesn’t use an HRMS and instead manages data in CSV files, Tartan offers an easy CSV upload integration. The client admin can upload their CSV, map the column headers, and rectify any errors before sharing (e.g., phone numbers should be 10 digits). The admin won’t be able to share the data until all errors are resolved, ensuring that you receive the correct data, eliminating multiple rounds of back-and-forth. Steps to build a CSV based Integration:
1

Invite your client organisation

Your client admin receives an email to login to the Tartan console (whitelabeled).
2

Client admin selects upload CSV option

Your client admin selects Upload CSV option from the list of supported integration methods.
3

Client admin maps the column headers with Tartan keys

The client admin associates the CSV column headers with Tartan’s corresponding keys.
4

Client admin reviews the data

The client admin reviews the final data and resolves the validation errors, if any.
5

Client admin completes the journey

Once the client admin reviews the data, client admin submits the initial data dump. For future updates, the client admin can either upload a full load file or only updated records file.

​
Via SFTP Integration

Tartan supports secure data transfer through SFTP (Secure File Transfer Protocol). If your client organization does not use HRMS and prefers to have their data fetched directly from an SFTP server, Tartan can seamlessly handle the transfer. This integration ensures secure, encrypted data retrieval from the client’s SFTP server, facilitating a reliable and efficient way to manage sensitive information during the transfer process. Steps to build a SFTP based Integration:
1

Invite your client organisation

Your client admin receives an email to login to the Tartan console (whitelabeled).
2

Client admin selects SFTP flow option

Your client admin selects SFTP flow option from the list of supported integration methods.
3

Client admin enters credentials

The client admin can select either the Host URL or IP address method to establish an SFTP connection, providing the necessary details such as file directory, username, password, or private key and data refresh rate for secure authentication.
4

Client admin maps the column headers with Tartan keys

The client admin maps the column headers from the file fetched from their SFTP server to Tartan’s corresponding data keys.
5

Client admin reviews the data

The client admin reviews the final data and resolves the validation errors, if any.
6

Client admin completes the journey

Once the client admin reviews the data, they submits the initial data dump.
File Not Found or Timeout Errors:
  • The system will attempt to fetch the file three times as per the refresh schedule.
  • If the file is not received after three attempts, the connection status will be marked as Failed.
Retry Schedule (For a refresh schedule of 1 day):
  • Attempt 1: On the scheduled day.
  • Attempt 2: On the next day.
  • Attempt 3: On the following day.
If the file is received during any attempt, the retry counter resets.

​
Push API Integration

Tartan supports pushing the data on an API. Push API method allows corporates to actively send (or “push”) employee records to Tartan in real time, one record at a time. How It Works
1

API Endpoint Exposure

Tartan provides a dedicated API endpoint where corporates can push employee data.
2

Authentication Methods

The Push API supports two authentication mechanisms:
  • Token-Based Authentication
  • Basic Authentication (Username & Password)
3

UAT (User Acceptance Testing) Phase

  • Initially, Tartan shares a set of UAT credentials (username and password) with the client via a secure webhook.
  • The client’s corporate uses these credentials to push sample employee data to the UAT environment for validation and testing purposes.
4

Approval and Data Purge

  • Once the UAT data is reviewed and approved by Client, the test data is purged from the system to ensure a clean transition to production.
5

Production Access

  • Tartan then generates a new set of production credentials.
  • These credentials are shared securely with the client, allowing them to push live employee data to establish a production-grade connection.

​
Custom Integration

Tartan also supports custom integrations tailored for your corporates. In many cases, your corporates may be large enterprises that either use internally built HRMS systems or prefer not to expose their core HRMS data directly due to security or compliance concerns. Instead, they create wrapper APIs over their internal systems to control and manage data access. For such scenarios, Tartan offers flexibility by consuming and integrating with these custom wrapper APIs—rather than relying on standard methods like CSV uploads or SFTP transfers. Our team works closely with your technical stakeholders to understand your API specifications and establish a secure, reliable connection. Best of all, we can typically build and deploy these custom integrations in under a week, ensuring minimal disruption and a fast go-live experience.