BeeWorkforce + Keka
Keep Keka credentials in one place and export attendance for Keka import.
Use BeeWorkforce for punches, breaks and worked hours, and Keka for payroll. Save your Keka credentials (encrypted, never shown again), check that Keka accepts them, and export attendance for any date range as a CSV keyed by employee code. There's no automatic sync yet: you download the file and import it into Keka.
What you can do
Encrypted credentials
Client ID, client secret and API key are stored encrypted and never displayed after saving.
Connection test
Check that Keka issues an access token for your credentials before you rely on them.
Attendance export
Download attendance for any date range as a CSV keyed by employee code.
Matched by employee code
Rows use the employee codes you keep in BeeWorkforce, so they line up with your Keka records.
Set up Keka in a few minutes
- Make sure each person's employee code in BeeWorkforce matches their Keka employee number.
- Go to Settings → Integrations → Keka, enter your company sub-domain, client ID, client secret and API key, and save.
- Click Test connection.
- Click Export attendance, choose the dates and download the CSV.
- Import the file in Keka, after checking the columns against Keka's attendance import template.
Frequently asked questions
Does attendance sync to Keka automatically?
No. Today you export a CSV and import it into Keka. Automatic sync is on our roadmap.
Will the CSV match Keka's template exactly?
It's laid out for attendance import, but templates vary by account. Compare the columns with your Keka import template before the first upload.
Who can see the Keka credentials?
Nobody, after saving. Only admins can change them, and the stored values are encrypted.
See BeeWorkforce with your own team
Book a 30-minute walkthrough. We'll set it up around how your team works and answer your questions.