Docs rushflow.org ↗ Sign in Start free

How to connect a ZKTeco attendance device — with no middleware server

Android ZKTeco Web Updated Aug 2026

RushFlow connects ZKTeco fingerprint and face devices directly into HR & payroll — with no middleware server, Windows service, or third-party software, and no separate app to install. You register the device once in the RushFlow management app you already use (HR → Attendance devices), then connect it one of two ways: Cloud push (ADMS) — the device sends its punches straight to RushFlow over the internet and nothing runs on-site; or Local Wi-Fi (LAN) — an on-site phone or tablet already running the RushFlow app pulls the punches over your router on port 4370. Either way the punches land in RushFlow HRM automatically, and you can review attendance from any device (web, Android or iOS). The steps below cover setting the device’s IP, connecting it to your router, registering it in RushFlow, choosing the connection mode, enrolling employees, and syncing.

Step by step

  1. Connect the ZKTeco device to your routerPlug the ZKTeco device into your router with a LAN (Ethernet) cable, or join it to your Wi-Fi if the model supports it, then power it on. For the Local Wi-Fi (LAN) option, the device and the on-site phone/tablet running RushFlow must be on the same network / same router.
  2. Set the device’s IP addressOn the device, open Menu → Comm. (Communication) → Ethernet / Network and set a static IP in your router’s range (e.g. if your router is 192.168.0.1, use something like 192.168.0.50), with the matching subnet mask (usually 255.255.255.0) and gateway (your router’s IP). A static IP stops the address changing later and breaking the connection. Note it down.
  3. Note the port, comm key and serialIn the same Comm. menu, confirm the port is 4370 (the ZKTeco default) and note the Comm Key / password if one is set (0 means none). Also note the device’s serial number (Menu → System Info) — RushFlow uses it to match the device to your business.
  4. Register the device in RushFlowThere is no separate gateway app to download and no extra sign-in. In the RushFlow management app you already log in to, go to HR → Attendance devices → Add device. Enter a name, the device’s serial number, choose the connection mode (see the next step), enter the device’s IP address (needed if you’ll pull over Wi-Fi), and assign the branch(es) the device serves.
  5. Choose how it connectsPick the connection mode when you add the device:
    • Cloud push (ADMS) — on the device, open Menu → Comm. → Cloud Server / ADMS setting and point it at your RushFlow server address. The device then sends (“pushes”) its punches straight to RushFlow over the internet, authenticated by its serial number and an optional push key. Nothing runs on-site.
    • Local Wi-Fi (LAN) — keep an on-site phone or tablet running the RushFlow app on the same router; it reaches the device on port 4370 and pulls the punches. This uses the app you already have — not a separate download.
  6. Enroll employeesCreate the employee in RushFlow first (name + branch). Then in HR → Attendance devices, choose the employee and start enrolment on the device; have them place their finger (or face) on the ZKTeco reader as prompted (usually 2–3 captures). This ties the device slot to that employee so every future punch is attributed to them. Repeat per employee. See enroll fingerprints.
  7. Receive / pull attendanceStaff punch on the device to clock in/out. With Cloud push, punches arrive at RushFlow automatically. With Local Wi-Fi, the on-site RushFlow app pulls on a schedule and you can also tap Sync now; punches are cached on the phone and forwarded, so a brief network blip never loses data.
  8. Confirm it reached RushFlowOpen RushFlow HRM → attendance and confirm today’s punches appear against the right employees and branch. From here, hours flow into payroll automatically — see attendance to payroll.

Why “no server” matters

Traditional ZKTeco integrations rely on a Windows machine running vendor middleware or a custom service that must never be switched off — fragile and costly for a small shop. RushFlow needs neither: with Cloud push the device talks straight to RushFlow, and with Local Wi-Fi the RushFlow app you already run on-site does the pulling. There is nothing extra to install or keep alive on a PC.

Local Wi-Fi pull caches locally then forwards: if the internet drops, punches are held on the on-site device and sent when the connection returns — the same offline-tolerant approach as the POS. Cloud-push devices likewise re-send once they reconnect.

Multiple devices and branches

Larger businesses run a device at each entrance or branch. RushFlow supports several devices — cloud-push or LAN — each mapped to its branch, and a fingerprint enrolled once can be recognised across devices.

  • Register multiple ZKTeco devices (cloud-push or LAN)
  • Assign each device to one or more branches
  • Enroll a fingerprint once and use it across devices

What happens to the punches

Once in RushFlow, punches become attendance records that feed leave, overtime and — most importantly — payroll. See From attendance to payroll for how hours turn into pay.

  • Daily attendance per employee and branch
  • Late / early / absent visibility
  • Hours flow into the payslip calculation

Frequently asked questions

Is there a separate attendance app to install?

No. You manage devices and enrol staff in the RushFlow management app you already sign in to (HR → Attendance devices). There is no separate “gateway” app and no extra login.

Do I need a server or PC to use ZKTeco with RushFlow?

No. Either the device pushes punches straight to RushFlow (Cloud push / ADMS), or the RushFlow app already running on an on-site phone pulls them over your Wi-Fi. There is no Windows service, middleware server or third-party software to maintain.

What is the difference between Cloud push and Local Wi-Fi?

Cloud push (ADMS) means the device sends punches to RushFlow over the internet — nothing runs on-site, but the device must support a Cloud Server / ADMS setting. Local Wi-Fi (LAN) means an on-site phone or tablet running the RushFlow app pulls from the device on port 4370 over the same router.

What if the internet drops?

Punches are not lost — a Local Wi-Fi pull caches them on the on-site phone and forwards them when the connection returns, and cloud-push devices re-send once they reconnect.

Can I use more than one device?

Yes. Register multiple ZKTeco devices, each mapped to its branch, and a fingerprint enrolled once can be recognised across devices.

Ready to run your business on RushFlow?

Start a free trial, or explore the live demo — no credit card needed.

Create your account →