Connect a time-clock system
5 min read · Updated 3 Jun 2026
Two ways in
Pick whichever matches your setup:
- A built-in adapter — WBSync polls your provider for you. Workflow Infinity is available on every plan; Deputy, ClockShark, QuickBooks Time, Connecteam and Hubstaff are available on Pro and up.
- The open ingest endpoint — any kiosk, biometric reader, RFID turnstile or in-house system POSTs events to a single secure URL. No adapter required.
Connect a built-in provider
Choose your provider and fill in the connection fields it asks for (an API key, or a client ID and secret — exactly what your provider's admin console gives you). Secrets are encrypted at rest and never shown back to you.
Hit Test connection for a real credential and connectivity check — a green badge means you're wired up. WBSync then pulls new clock events on a schedule.
Set each operative's external clock ID to the ID they have in your time system. That's the key WBSync uses to attach a clock event to the right person. Unknown IDs can be auto-added as operatives if you switch that on.
Push from anything: the open endpoint
For systems without an adapter, POST JSON to /api/v1/clock-events/ingest/ with your tenant's secret in the X-Inbound-Secret header. Send the worker's clock ID, the clock-in and clock-out times, and optionally the WBSync project code. Include an Idempotency-Key and retries are safe — replays are de-duplicated, never double-counted.
What next?
Clock-ins and manual logs for the same person can collide — that's by design, and easy to sort: Clashes & approvals →
Frequently asked
Which time-clock systems are supported?
Workflow Infinity ships on every plan. Deputy, ClockShark, QuickBooks Time, Connecteam and Hubstaff have built-in adapters on Pro and up. Anything else can push to the open endpoint over HTTPS.
How does WBSync know which worker a clock event belongs to?
By the external clock ID. Set each operative's external clock ID to match the ID they have in your time system, and events attach to the right person automatically.
Do clock-ins skip approval?
No. They arrive as submitted entries in the project's unallocated bucket. A foreman assigns the cost code and approves them, exactly like a crew-log row — so the approval gate still protects your data.
Is the open endpoint safe to retry?
Yes. Authenticate with your tenant's secret header and include an idempotency key; replays are de-duplicated, so a network retry never double-counts a shift.