Integrations
ClockCover is deliberately vendor-agnostic: it reads what your systems already export. Here is what exists today, what we need from you, and how an integration project runs.
Available today
| Path | Direction | What you provide |
|---|---|---|
| CSV upload in the console | in | The two files described in Help. Nothing else. |
| Scheduled fetch over https | in | A fixed https address where your system publishes the export (and optionally the roster). The address is the credential — use one with a secret in it. We fetch every morning before the digests and email the operator if the fetch or the file fails. |
| Script upload (API key) | in | For your own scheduler or an integrator: POST /employers/:id/imports with the CSV body and a bearer key your operator creates in the console (Settings → API keys). Keys belong to one employer, are shown once, and can be revoked. |
| Corrections export | out | CSV from the console for any date range: approved hours and reported absences with notes, planned times and planned hours. Carry it into your payroll run. |
Built on request
- Excel exports (
.xlsx) from attendance systems — a column mapping, then the same pipeline. - Vendor connectors for a specific attendance system (an API or a report URL). One per system; we write it, you keep it.
- Email attachment intake — forward the daily export to an address and it imports itself.
- Corrections push into your payroll or attendance system, once we know which one and what it accepts.
During early access we build these at no charge and have them running within two weeks of receiving your sample export.
What we need from you
- A sample export
- One real-shaped file (synthetic or anonymised names are fine) covering a few days: which columns exist, how dates and times look, how a missing entry appears (empty cell? “—”? absent row?).
- The roster source
- Where employee → manager lives: an HR export, the attendance system, or a spreadsheet someone maintains. And what the stable employee identifier is.
- Access, if we fetch
- An https URL with a secret, or read-only API credentials for the attendance system. We never need write access to anything of yours. Credentials go into an encrypted Worker secret, never into email or chat.
- Two settings
- Your timezone and the SLA you want (hours before a gap goes to the payroll accountant).
- Where corrections should land
- Which payroll or attendance system, and whether it takes a file or an API call. If unknown, the CSV export is the answer for now.
How an integration runs
- Day 0 — sample. You send the export (and roster) sample. We confirm the column mapping back to you in writing.
- Days 1–10 — build. We write the adapter and test it against your sample. You see the result in the console: shifts, entries, gaps detected.
- Parallel run. For a week the daily import runs against live exports while your current process continues. Managers can already receive digests, or we keep them off until you say go.
- Day 14 at the latest — live. Digests and escalations on. The two weeks are our commitment, counted from day 0.
Security notes
- No accounts or passwords for managers or the payroll accountant: signed, expiring links. The operator console and the admin area use emailed sign-in links.
- We store normalised records only; raw files are parsed and discarded. No biometric data ever reaches us.
- Everything is per employer; nothing is shared between employers.
Have a system we should look at? Tell us which one.