FLOW DIRECTIONS
Keka → We360.ai
We360.ai pulls raw daily logs. Data includes the overall duration of attendance, times, and device IDs registered during clock-ins.
- READ-ONLY • ACTIVE
INTEGRATION | Keka
Keka Attendance, Synced Into We360.ai Every Morning
First-in time, last-out time, and work premise fetch from Keka into We360.ai on a fixed daily schedule, so your attendance reports are current before the day starts, not reconciled a week later.
NATIVE Fetch (Keka → We360.ai) Daily, automatic Setup: 5 credentials, no code
Free 7-Day Trial
5 mins Setup
No Credit-card
One daily fetch. three fields. no manual export.
Every day, We360.ai pulls the prior day's attendance records from Keka for each employee's first clocked-in, when they last clocked out, and which work premise they were logged at. Your databases stay cleanly sync'd daily without anyone exporting spreadsheets or uploading manually.
FLOW DIRECTIONS
We360.ai → Keka
A separate, opposite direction sync is rarely necessary. Leave empty to allow We360.ai to remain the clear downstream consumer of records.
- SETUP GUIDE PENDING
Data Flows
Exactly what moves, which direction, and how often.
Field
Source
Destination
Frequency
Notes
Check-in time
Keka → Attendance
We360.ai → Logs
Daily, 6 AM
Raw punch-in timestamp
Late arrival time
Keka → Computed
We360.ai → Analytics
Daily, 6 AM
Minutes past shift start
Work period
Keka → Duration
We360.ai → Productivity
Daily, 6 AM
Total hours logged
Grace time
We360.ai → Settings
We360.ai → Rules
On save
Configurable buffer window
Connect once, then configure how the two systems stay in step.
A We360.ai Super Admin connects Jira and configures how the two systems sync.
1
Start the connection.
On the Jira tile, click Connect with Jira for OAuth, or enter your Jira Base URL, Service Account Email, and API Token for token-based auth.
2
Authorize or test.
For OAuth, approve the request in the Jira popup. For a token, click Test Connection to confirm the credentials work, then save.
3
Set the sync direction.
Choose Bidirectional, Inbound only, or Outbound only.
4
Choose field toggles.
Pick which fields sync each way. Inbound can include task creation, summary, description, status, assignee, story points, due date, comments, and attachments. Outbound can include summary, description, assignee, story points, due date, worklogs, comments, and attachments.
5
Set the Story Points Field ID.
Enter the Jira custom-field ID used for story points.
6
Decide how to handle unmapped users.
Choose to skip, create a new user, or use a fallback user when a Jira user has no We360.ai match.
7
Map your projects.
Open Project Mappings and link a We360.ai project to a Jira project by its project key, or turn on Auto-create projects on import.
8
Run Auto-Map to We360.ai Users, then sync.
Line up accounts by email, then display name, before your first full sync.
Everything lives in Settings Center
We360.ai brings Jira integration setup into one Settings Center panel. Connect once, configure the sync direction and field mapping, and the scheduled sync runs daily by default.
Jira connection via OAuth or an API token
Sync Direction: Bidirectional, Inbound only, or Outbound only
Field toggles for what syncs each way, plus a Story Points Field ID
Project Mappings by Jira project key, with optional auto-create on import
Scheduled sync daily by default, plus on-demand Trigger Sync and a near real-time webhook
If something looks off, check these three things first.
Most sync issues trace back to credentials, mapping, or permissions. Here's what to check before contacting support.
1
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.
2
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.
3
API calls fail
Confirm the Keka API key has Mark Attendance privileges enabled.
**Still Stuck?** Email support@we360.ai for integration support. For Keka's own API, contact support@keka.com.
Using another HR System? Start here.
We360.ai also pushes attendance to GreytHR and Zoho People, so you can standardize on whichever HR system your team already uses.
GreytHR
Full attendance policy compliance, leave health, and org-wide visibility. Always audit-ready.
Zoho People
Clean, reconciled attendance exports that feed directly into payroll. Zero manual reconciliation.
All integrations
Live shift adherence, overtime alerts, and cross-site attendance. So every shift runs smooth.
Security & Compliance
Built for Enterprise IT Secure, Compliant, and Scalable
Ensures Privacy and Security with Encrypted Data, Secure Connections, and Multi-Standard Compliance
256-Bit
Encryption
99.9%
Uptime SLA
24/7
Monitoring
Flexible Pricing for Global Teams
Dual-currency billing. No hidden professional services fees. Starts with a risk-free 14-day trial.
Pro
Perfect for small teams and startups
₹599
/user/month
Most Used Features
- Scheduling & Attendance
- Workload Balance & Analysis
- Productivity Goal Setting & Tracking
- Reports (Automatic)
- Website Utilization
- Alerts
Pro + AI
For growing businesses with advanced needs
₹799
/user/month
Everything in Pro, Plus
- AI Workplace Assessment
- AI Based Industry Benchmarking
- AI Based Risk Scoring
Enterprise
Tailored solutions for large organizations
Custom
Most Advanced Features
- Up to 2 Year Data Retention
- ActiveDirectory Integration
- Single Sign On
- Team Based Timezones
- 25+ Alerts
- Screenshot Capture Frequency (60/hr)
- On Premise Deployment
The questions productivity buyers actually ask.
Find quick answers to common questions about We360.ai
Does We360.ai integrate with Jira?
Yes. We360.ai syncs projects, tasks, and worklogs with Jira. You connect it in Settings, Integrations, on the Jira tile.
Which direction does the data flow?
It's configurable. Choose Bidirectional, Inbound only (Jira to We360.ai), or Outbound only (We360.ai to Jira).
Do I need an API token, or can I use OAuth?
Either. OAuth is recommended and needs no tokens. An API token works too, using a Jira Base URL, a service account email, and an API token.
How are Jira and We360.ai users matched?
By email, falling back to display name. Run Auto-Map to We360.ai Users to line up accounts before your first full sync.
Do worklogs sync both ways?
No. We360.ai time entries push to Jira as worklogs, outbound only. Status is inbound-only, from Jira to We360.ai.
How often does the sync run?
Daily by default. Use Trigger Sync for an on-demand run, or set up the webhook for near-real-time inbound updates.
Is the Jira integration included in every paid plan?
Native SaaS integrations are included on every paid plan.
Keep your team in Jira. Keep the data in We360.ai.
Native SaaS integrations are included on every paid plan.