Integrations

Connect We360.ai to your HRMS, collaboration, and project tools from the Integrations settings tab—push and fetch attendance, track meetings, and sync project tasks.

The Integrations tab connects your We360.ai workspace to the HR, collaboration, and project-management tools your organization already uses—so attendance, meetings, and tasks move between systems automatically, without manual exports. For a conceptual overview of how these connections fit together, see the Integrations reference.

Configuring integrations requires Super Admin access.

How integrations work

Each integration appears as a card on the Integrations tab. Select Configure on a card to open its setup panel, enter the connection details from the third-party service, then Save. Once connected, the card shows an Enabled status and its button changes to Edit Configuration. Every card also links to a step-by-step Integration Guide.

Most integrations share two common settings:

• Auto Run: runs the integration automatically on a schedule (for example, pushing the previous day's punch logs each day). This can't be changed after the initial setup, so set it correctly the first time.
• Unique Identification Key: the field used to match employees between We360.ai and the other system: Email, Email Prefix, Employee ID, or Employee ID Prefix. Pick the identifier both systems share.

Some integrations (such as GreytHR) can also be run manually for a past date, alongside the automatic schedule.

Available integrations

Integration	What it does	Setup guide
Microsoft Teams	Records time spent in Microsoft Teams meetings so productivity reports reflect it accurately.	Microsoft Teams
GreytHR Push Punch Logs	Sends employee punch-in / punch-out times to GreytHR each day.	GreytHR Push Punch Logs
Zoho Push Punch Logs	Sends employee punch-in / punch-out times to Zoho People each day.	Zoho Push Punch Logs
Keka Push Punch Logs	Sends employee punch-in / punch-out times to Keka each day.	In-app guide
Keka Fetch Attendance	Pulls first-in / last-out attendance from Keka; appears in the Daily Attendance and Integration reports.	Keka Fetch Attendance
Keka User Attribution Sync	Syncs employee attributes from Keka onto matching We360.ai users.	In-app guide

To connect any of these, you will need credentials from the third-party service (for example, a client ID and secret, an API key, or a service-account token). The linked setup guides list exactly what to obtain and where to enter it.

Jira

The Jira integration is in Alpha and under active development—its behavior may change.

The Jira integration keeps projects, tasks, and worklogs in sync between We360.ai and Jira. You can:

• Connect using OAuth 2.0 (recommended, for Jira Cloud) or an API token (for Jira Server / Data Center).
• Choose a sync direction: two-way, inbound only (Jira → We360.ai), or outbound only (We360.ai → Jira).
• Select which fields sync: summary, description, status, assignee, story points, due date, comments, worklogs, and attachments.
• Map Jira projects and users to their We360.ai equivalents, or create them automatically on import.
• Optionally enable a real-time webhook so Jira changes appear in We360.ai immediately, rather than waiting for the next scheduled sync.

Setup actions include Test Connection and Trigger Sync, plus a Recent Sync Errors view to help confirm everything is working.

Programmatic API access

The Integrations tab is for connecting packaged tools. To pull We360.ai data into your own scripts or reporting tools, use the REST API with an access token instead—see OAuth for Direct API Access.

Need another system

Additional HRMS integrations (such as Workday) can be enabled for your workspace by the We360.ai team. Contact the We360.ai support team to discuss a custom integration.