Sync Agent
Automatically synchronize attendance data from ZKTeco biometric devices to AttendUX cloud.
Overview
The AttendUX Sync Agent is a lightweight Windows desktop application that bridges your local ZKTeco biometric devices with the AttendUX cloud platform.
It runs in the background, periodically pulling attendance records from your ZKTeco devices and uploading them to your AttendUX server automatically.
Download & Install
Download the Sync Agent installer and follow the setup wizard:
Download the Installer
Download the latest version of the Sync Agent: Download Attendux-Sync-Agent.exe
Run the Installer
Double-click the downloaded file and follow the installation wizard. Accept the default settings.
Launch the Agent
After installation, the Sync Agent will start automatically. You'll see its icon in the system tray.
AttendUX Sync Agent
v2.1.0 · Windows Desktop
Configuration
Configure the Sync Agent with your server details and device information:
| Field | Description | Example |
|---|---|---|
| Server URL | Your AttendUX server address | https://yourcompany.attendux.com |
| Company Code | Your unique company identifier | COMP-001 |
| API Key | Authentication key from Settings → Integrations | sk_live_xxx... |
| Sync Interval | How often to sync data (in minutes) | 5 |
| Device IP | Local IP address of the ZKTeco device | 192.168.1.201 |
How Sync Works
The sync process follows these steps automatically:
Connect to Device
The agent connects to your ZKTeco device over the local network using TCP/IP.
Fetch New Records
It retrieves all new attendance punch records since the last sync.
Upload to Cloud
Records are securely sent to your AttendUX server via HTTPS and matched to employees automatically.
Running as a Service
For maximum reliability, you can configure the Sync Agent to run as a Windows service so it starts automatically when the computer boots.
Open the Sync Agent settings and enable "Run as Windows Service". This ensures syncing continues even when no user is logged in.
Troubleshooting
Common sync issues and how to fix them:
Verify the device IP is correct, ensure the device is powered on, and check that the computer and device are on the same network. Try pinging the device IP.
Ensure the API key is correct and not expired. Check that the server URL includes https://. Verify the device has new attendance records.
The agent has built-in deduplication. If duplicates appear, clear the agent cache and re-sync. Check that only one instance of the agent is running.