Integration · KekaKeka attendance, synced into Airtask.
First-in time, last-out time and work premise fetch from Keka into Airtask on a fixed daily schedule, so your attendance reports are current before the day starts, not reconciled a week later.
- Native fetch, Keka to Airtask
- Daily, automatic
- Five credentials, no code
Quick answer
Does Airtask integrate with Keka?
Yes. Airtask fetches attendance from Keka every day at 05:30 UTC (11:00 AM IST). It pulls the previous day's first-in time, last-out time and work premise, then shows them in attendance and dynamic reports. Setup needs five Keka values and no code, and it runs automatically after you save.
What moves
One daily fetch. Three fields. No manual export.
Every day, Airtask pulls the prior day's attendance records from Keka for each employee's first clock-in, when they last clocked out, and which work premise they were logged at. Your records stay cleanly in sync every day, without anyone exporting spreadsheets or uploading manually.
Schedule
- Daily fetch
- 05:30 UTC / 11:00 AM IST
- Covers the previous day
Synced fields
- First-in time
- Last-out time
- Work premise, mapped as location
Flow directions
Which way the data moves.
Keka to Airtask
Airtask pulls the previous day's first-in time, last-out time, and work premise from Keka. Nothing is written back to Keka.
Read-only · ActiveData flows
Data flows
Exactly what moves, which direction, and how often.
| Field | Source | Destination | Frequency | Notes |
|---|---|---|---|---|
| First-in time (check-in) | Keka API | Attendance and Dynamic Reports | Daily, 05:30 UTC / 11:00 AM IST | Keka attendance punch-in time |
| Last-out time (check-out) | Keka API | Attendance and Dynamic Reports | Daily, 05:30 UTC / 11:00 AM IST | Keka attendance punch-out time |
| Work premise | Keka API | Attendance and Dynamic Reports | Daily, 05:30 UTC / 11:00 AM IST | Premise name mapped as location |
Before you start
Five values from Keka, and one rule about employee IDs.
Have these ready before you open the setup screen:
- Client ID
- Client Secret
- API Key
- Subdomain
- Unique Identification Key
- Every synced user must have an Employee ID, and the same identifier must be used in both systems. A user without an Employee ID will not sync.
- A Keka Global Admin creates the credentials in Keka. Only a Global Admin can create and manage API keys there.
Setup
Five credentials, one settings screen.
A Keka Global Admin generates the credentials, and anyone with access to Airtask Settings can complete the sync setup from there.
Generate Keka credentials
Log in to the Keka Admin Portal as a Global Admin, go to Global Admin Settings, then Integrations & Automation, then API Access, and generate a Client ID and Client Secret pair.
Generate an API key with Attendance access
In the API Key section, click Create New Key and make sure Mark Attendance privileges are selected. Without this permission, the integration will not work.
Find your Keka subdomain
Identify the subdomain in your company's Keka login URL. If your URL is https://company.keka.com, enter company.
Enter credentials in Airtask settings
Go to Settings, Integrations, Keka Fetch Attendance in Airtask, and enter your Client ID, Client Secret, API Key, Subdomain, and Unique Identification Key.
Provide the unique identification field
Specify the Unique Identification Key used to match employees between Keka and Airtask. The same identifier must be used in both systems.
Enable Auto-Run
Select the Auto-Run checkbox and save. The next scheduled run will fetch the previous day's records.
Employee IDs must match in both Keka and Airtask. If an identifier does not match, that employee's attendance sync is skipped.
Settings Center
Everything lives in Settings Center.
Airtask brings Keka integration setup into one Settings Center panel. Enable Auto-Run and save once. After that, it fetches the previous day's attendance automatically at 11:00 AM IST, no further action needed.
- Keka Client ID, Client Secret, API Key, and Subdomain
- Unique Identification Key that matches each employee's Employee ID between Keka and Airtask
- Auto-Run checkbox to enable automatic daily sync
- Employee ID required for every synced user, or that record is skipped
- Fetches first-in time, last-out time, and work premise into your attendance and dynamic reports
Client ID
Client Secret
Keka subdomain
API Key
Unique identification key
Sync schedule
Auto-Run
Troubleshooting
If something looks off, check these first.
Most sync issues trace back to credentials, mapping, or permissions. Here's what to check before contacting support.
Attendance data does not appear
Check your Client ID, Client Secret, API Key, and Subdomain for typos. The subdomain should be only the company part of your Keka URL.
Some users are missing from the sync
Check the Unique Identification Key mapping, and confirm the missing user has an Employee ID in both systems.
API calls fail
Confirm the Keka API key has Mark Attendance privileges enabled.
Still stuck? Contact Airtask support. For Keka's own API, contact [email protected].
Related integrations
Using another HR system? Start here.
Airtask also pushes attendance to greytHR and Zoho People, so you can standardize on whichever HR system your team already uses.
Security
Security your IT team will sign off on.
The first things your security review asks, answered right here.
SOC 2 Type II
Demonstrating our commitment to security, availability, processing integrity, confidentiality, and privacy.
GDPR
Ensuring compliance with European Union data protection and privacy regulations.
ISO 27001
Certified adherence to international standards for information security management.
HIPAA
Demonstrating our commitment to health data privacy, security, and HIPAA compliance.
Encrypted in transit
Data moving between your team and Airtask travels over TLS.
Encrypted at rest
Stored data is encrypted with AES-256.
Access by role
Owner, Member and Guest roles decide who can do what.
Single sign-on
Your team signs in through your company’s identity provider over SAML.
Pricing · flat per workspace, never per seat
With Airtask, every day is Black Friday.
We know you hate paying per user. So we stopped charging for it.
Plans run $25, $49 or $99 a month per workspace. On Plus, growing from 21 to 200 people costs $0 more.
Money you stop handing Jira
Jira Standard: $87/mo for 11 people. Airtask Basic: $25/mo.
Against the average of 8 per-seat tools, you keep $113/mo
- Airtask Basic
- $25/mo
- Jira Standard
- $87/mo
Competitor list prices: entry paid team tier, per user, billed monthly, from each vendor’s pricing page on Oct 10, 2026. Airtask prices are flat per workspace per month.
| Users | Airtask | Jira Standard | ClickUp Unlimited | Asana Starter | monday.com Standard | Notion Plus | Trello Standard | Smartsheet Pro → Business above 10 members | Linear Basic |
|---|---|---|---|---|---|---|---|---|---|
| 11 | $25 | $87 | $110 | $148 | $210 | $110 | $66 | $264 | $110 |
| 20 | $25 | $158 | $200 | $270 | $280 | $200 | $120 | $480 | $200 |
| 50 | $49 | $396 | $500 | $675 | $700 | $500 | $300 | $1,200 | $500 |
| 100 | $49 | $791 | $1,000 | $1,349 | $1,400 | $1,000 | $600 | $2,400 | $1,000 |
| 200 | $49 | $1,582 | $2,000 | $2,698 | $2,800 | $2,000 | $1,200 | $4,800 | $2,000 |
| 500 | $99 | $3,955 | $5,000 | $6,745 | $7,000 | $5,000 | $3,000 | $12,000 | $5,000 |
Basic
Your planUp to 20 people for $25 a month. Not $25 a head.
$25/mo
billed monthly
- Up to 10 active projects
- 10 GB storage
- Up to 20 users
- Projects, Notes, Timesheets
- Bring your own AI
Plus
Up to 200 people on one $49 bill.
$49/mo
billed monthly
- Up to 20 active projects
- 50 GB storage
- Up to 200 users
- Everything in Basic
- Reports (incl. cost management)
- Integrations
- Bring your own AI
Pro
Unlimited people. Hire like you mean it.
$99/mo
billed monthly
- Up to 50 active projects
- 250 GB storage
- Unlimited users
- Everything in Plus
- Workflow Automation
- Custom Fields & Status
- Bring your own AI
Ultra
For the org that outgrew everything else.
Let’s talk- Custom limits
- Everything in Pro
- Tailored to large organisations
No coupon code, no countdown timer. This is the everyday price.
Connect Keka in the time it takes to read this page.
Native integrations are included on the Plus plan and up.
Book a demoFAQs
Keka integration, answered.
The questions teams ask before connecting Keka.
Does Airtask integrate with Keka?
Yes. Airtask has a Keka Fetch Attendance integration that pulls attendance records from Keka every day. You set it up in Settings, Integrations, with five values from Keka and no code.
Is the Keka sync one-way?
Yes. This integration moves data one way, from Keka into Airtask. It reads first-in time, last-out time and work premise, and it does not change anything in Keka.
What time does the Keka sync run?
It runs daily at 05:30 UTC, which is 11:00 AM IST, and fetches the previous day's records.
Which Keka credentials and permissions do I need?
A Client ID, Client Secret, API Key, your Keka subdomain and a Unique Identification Key. The API key must have Mark Attendance privileges enabled, and a Keka Global Admin creates it.
Why are some users missing from the sync?
Every synced user needs an Employee ID, and the identifier must match in both systems. Check the Unique Identification Key mapping and confirm the user has an Employee ID.
Is the Keka integration included in my plan?
Native integrations are included on the Plus plan and up.