> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/administration/settings-center/integrations.md).

# Integrations

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](https://docs.we360.ai/reference/work-and-time-management/user-interfaces/portal/settings-center/integrations).

{% hint style="info" %}
Configuring integrations requires **Super Admin** access.
{% endhint %}

## 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](https://docs.we360.ai/deployment-and-it-ops/integrations/portal-integrations/microsoft-teams)                 |
| **GreytHR Push Punch Logs**    | Sends employee punch-in / punch-out times to GreytHR each day.                                           | [GreytHR Push Punch Logs](https://docs.we360.ai/deployment-and-it-ops/integrations/portal-integrations/greythr-push-punch-logs) |
| **Zoho Push Punch Logs**       | Sends employee punch-in / punch-out times to Zoho People each day.                                       | [Zoho Push Punch Logs](https://docs.we360.ai/deployment-and-it-ops/integrations/portal-integrations/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](https://docs.we360.ai/deployment-and-it-ops/integrations/portal-integrations/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

{% hint style="warning" %}
The Jira integration is in **Alpha** and under active development—its behavior may change.
{% endhint %}

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](https://docs.we360.ai/deployment-and-it-ops/integrations/oauth-for-direct-api-access/dynamic-report-api).

## 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](mailto:support@we360.ai) to discuss a custom integration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.we360.ai/administration/settings-center/integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.