
Jul 10, 2024
Tartan's HyperSync Product Update - March 2025
New Feature: Set Sync Frequency on Console
Give Your Clients Control Over When Data Syncs Happen
With Set Sync Frequency, admins can now define how often data should sync, directly from the console. Whether it’s syncing daily, weekly, or monthly, this feature eliminates the need for backend intervention and empowers clients with full control over scheduling.
What It Does & Why It’s Needed
Clients can now:
Choose from three frequency options — Daily, Weekly, or Monthly
Set a preferred time and timezone for syncs
Modify or pause/resume syncs at any time
Schedule syncs per corporate entity within a vendor
This gives vendors flexibility to tailor sync cadences for each corporate, avoiding data overloads while ensuring timely updates.
How It Works
Navigate to the “Sync Frequency” section from the Action menu on the console
Select frequency (e.g., every Monday at 7 PM IST)
Set preferred time and timezone
Save the configuration and see the next sync time immediately
Need to pause a sync? Simply use the Pause Sync option, and resume it anytime to revert to the previous schedule.
Use Case
A benefits platform managing hundreds of corporate clients can now schedule data pulls every Friday at 6 PM, giving them fresh employee data before the start of a new workweek. For clients with infrequent updates, they can switch to monthly syncs, optimizing API usage and operations.
New Feature: Webhook Recon V2
End-to-End Visibility with Sync Session IDs & Webhook Tracking
We’ve introduced Webhook Recon V2, a smarter way for clients to track, validate, and troubleshoot webhooks. With the addition of syncSessionId and webhookCounter, vendors now have complete traceability across each data sync session.
What It Does & Why It’s Needed
syncSessionId: A unique identifier assigned to each sync session, grouping all related webhooks together
webhookCounter: A sequential number in each webhook to track order and completeness
totalWebhookCount: Shared at the start of a sync session, telling clients how many webhooks to expect
These enhancements make it easier to:
Reconcile missing or delayed webhooks
Re-trigger specific sync sessions
Audit data integrity with precision
How It Works
Each sync session generates a unique syncSessionId
All webhooks in that session include this ID along with an incremented webhookCounter
The first webhook now shares totalWebhookCount, indicating how many will follow
Only clients upgraded to Webhook V2 will receive these new fields. Existing clients using V1 will continue uninterrupted.
Use Case
A travel tech vendor syncing thousands of employee records daily can now instantly detect if any webhook is missing. By tracking webhookCounter and totalWebhookCount, they can pinpoint discrepancies and re-trigger only the affected sync session using the syncSessionId — saving hours of debugging.

Welcoming New HRMS Integrations – Beehive and DarwinBox
We’ve expanded HRMS Sync’s compatibility by adding two new powerful HRMS platforms: Beehive and DarwinBox.
Beehive HRMS is a robust, user-friendly platform used by fast-growing startups and mid-sized companies.
DarwinBox is a leading enterprise HR tech solution widely adopted across the APAC region for managing large-scale workforces.
With these additions, HRMS Sync continues to push boundaries, offering even broader connectivity for service providers looking to automate employee data sharing at scale.
Want to explore these new features? Sign up for sandbox access to experience custom sync scheduling and advanced webhook reconciliation firsthand.
We’re committed to building a smarter, more transparent HR data ecosystem. Stay tuned — there’s more innovation coming your way soon.