Keka integrations, and an AI agent for Keka.
Raven connects Keka HR and Keka Hire to Slack, Google and RazorpayX. It answers questions about time, leave, staffing and projects in Slack. Keka stays your system of record.
What syncs in from Keka
- EmployeesProfiles, reporting lines, job titles, worker type, locations, and joining and exit dates. Title changes and relocations show up as timeline events.
- Projects, tasks & budgetsKeka PSA projects with phases, tasks and budgeted hours. Raven sorts tasks into seven work categories.
- ClientsClient records and billing roles.
- TimesheetsApproved and pending entries, so mid-month utilization isn't understated.
- AllocationsExisting bookings come in and set the baseline for capacity and utilization.
- Attendance, leave & WFHDaily attendance, leave and work-from-home requests, including half days. Keka webhooks push changes.
- Holidays & weekly offsHoliday calendars and each person's weekly-off policy feed capacity, nudges and digests.
- Locations, departments & job titlesMirrored from Keka, so pre-boarding and offer letters show names, not Keka ids. Each office building links to its Keka location.
- Skills, certifications & praiseSkills and certifications drive staffing matches. Keka praise badges show on the employee profile.
- Helpdesk ticketsHelpdesk categories, tickets and closing reasons appear in Raven's Helpdesk, with SLAs and aging.
- Keka HireJobs, candidates, interviews, scorecards and Blacklist tags appear in Recruitment.
What flows back
Approved allocations
When a staffing request clears Ops and Executive approval, Raven writes the booking to Keka.
Won prospects
A prospect marked Active in Client Management becomes a client in Keka.
Seat locations
A desk change updates the person's building, floor and section in Keka and Google Workspace.
An AI agent for Keka, in Slack
Raven Assistant is a read-only agent in Slack. It answers from live Keka data you're allowed to see. Personal answers come back only in a DM.
- “Who on my projects is on leave this week?”
- “How many hours did I log last month, and how much is still unapproved?”
- “Which projects are over this year's budget?”
- “Who has React and AWS certification and capacity in October?”
- “What did we agree in my last 1:1?”
- “Is Friday a holiday in Chennai?”
- “What is our production rollback procedure?”
Scheduled agents for Keka, in Slack
Raven also runs scheduled and AI-assisted workflows on the Keka data it syncs.
Morning brief for every project lead
At 9:30, each PM and Tech Lead gets a Slack DM. It shows who is out or working from home, open escalations and release milestones due.
Attendance and health nudges
Leave-aware reminders for no-shows, WFH marks and clock-outs. Monday and Friday nudges for the weekly project health update.
AI coach on health updates
The coach checks drafts against the writing guide. It can rewrite them into the standard template before they post to Slack.
AI prep for 1:1s and escalation detection
A prep summary of a report's recent months. When the same issue recurs across months, Raven escalates it to Global Admins automatically.
AI screening calls for Keka Hire candidates
An automated caller runs first-pass screens. Responses and recordings are saved on the candidate.
Approvals in Slack
Allocation and change-order approvals arrive as Slack DMs. Approved allocations are written back to Keka.
What Raven adds on top of Keka
All of this runs on Keka data you already have.
Timesheets sorted into seven work categories
The categories are Development, Meetings, L&D, Design, Testing, Management and Admin. Overrides follow every entry under a task. Every combined figure shows how much still awaits Keka approval.
Budgets judged per calendar year
Raven splits the Keka hour budget into yearly periods that always add up to Keka's total. A multi-year project is judged on this year's allocation. Last year's overrun is a quiet pill, not an alarm.
Staffing requests with skill match and approvals
PMs raise allocation requests. Raven suggests people whose Keka skills and certifications fit. Ops and Executive approve, and the booking lands in Keka. Capacity accounts for holidays and is pro-rated for mid-month joiners.
Utilization, unallocated, overtime and weekend reports
See who is on the bench or working overtime. Break it down by PM or manager. Export the month's allocations, or a grouped timesheet, as CSV with approved and unapproved hours side by side.
Weekly project health, escalations and releases
Weekly Red/Amber/Green health updates with an AI coach. Escalations have owners. Release milestones are QA-gated, with a Release Metrics report. Updates go out over Slack for the projects on your Keka list.
A daily brief for every project lead
At 9:30 each morning, PMs and Tech Leads get a Slack digest. It shows who on their projects is out or working from home, plus open escalations and release milestones due.
Leave and WFH appear in Google Calendar
Approved Keka leave and WFH create personal out-of-office and team calendar events, with auto-decline set. Notes stay off shared calendars.
Attendance nudges over Slack
Raven flags outliers in the Keka attendance matrix. Leave-aware Slack nudges chase no-shows, missing WFH marks and clock-outs.
Recruitment on top of Keka Hire
Scorecards, calendar-based scheduling and an AI screening caller. Candidate notes start in Raven and go to Keka only when you push them. Hiring managers get a seat with salary details hidden.
People analytics from Keka data
Headcount, tenure, attrition and joiners, with period changes, trends and department comparisons.
Compensation tracking beside Keka payroll
Raven tracks dated package revisions, letters, bonuses, pay bands and cost rates. Keka and RazorpayX keep running payroll. Internship stipends are tracked separately from compensation.
Employee records checked across systems
Raven cross-checks Keka against Google Workspace, Slack and RazorpayX. Every mismatch goes to a queue where you resolve or ignore it.
Monthly 1:1s across the reporting line
Keka reporting lines decide who meets whom each month. Google Calendar handles scheduling. An AI prep summary helps each meeting, and recurring issues are escalated automatically.
Ask questions about Keka data in Slack
Raven Assistant answers questions about projects, your own time and leave, who is out, staffing capacity and company SOPs. It uses live data and follows your permissions. Personal answers come back only in a DM.
What stays in Keka
- 1Time entry and timesheet approval stay in Keka. Raven reads the approval status.
- 2Payroll processing stays with Keka and RazorpayX. Raven tracks compensation and reconciles what was paid.
- 3Raven does not invoice clients. Change orders hand off to invoicing with the evidence attached.
Questions Keka teams ask
- Does Raven replace Keka?
- No. Keka stays your system of record for people, time, leave, projects and payroll. Raven syncs from it and adds delivery reporting, approvals, budgets and Slack workflows.
- How often does the Keka sync run?
- A scheduled sync runs nightly. Keka webhooks push leave and WFH changes as they happen. Admins can also start a sync by hand.
- Can Raven show utilization before timesheets are approved in Keka?
- Yes. Hours awaiting Keka approval count in every utilization figure. Each figure shows how much is still unapproved.
- Is Raven an AI agent for Keka?
- Raven Assistant answers questions about Keka time, leave, attendance, people, projects and 1:1s in Slack. It is read-only and follows each person's permissions. Scheduled agents send daily briefs, nudges and approvals. Raven writes back to Keka only allocations, won clients and seat locations.
- Which integrations does Raven connect to Keka?
- Slack, Google Workspace, Google Calendar, RazorpayX and CallerDesk. Keka data feeds Slack answers and digests, and leave events in Google Calendar. Raven checks it against Workspace, Slack and RazorpayX, and uses CallerDesk for Keka Hire calls.
- Does anything write back to Keka?
- Three things: approved allocations, clients won in Client Management and seat locations. Everything else is read-only.