> 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/reference/work-and-time-management/user-interfaces/portal/settings-center/integrations.md).

# Integrations

We360.ai integration settings for connecting HR systems, collaboration and project tools, and the data API.

The **Integrations** settings view manages the *connections* between We360.ai and the external systems your organization already uses. It's the conceptual counterpart to the step-by-step setup guide in the Administration space; for how to configure each connection, see [Administration → Integrations](https://docs.we360.ai/administration/settings-center/integrations).

* **HR & attendance systems**: Keep attendance in sync with your HRMS. Push punch logs to GreytHR, Zoho People, and Keka; and fetch attendance and employee attributes from Keka.
* **Collaboration & project tools**: Reflect Microsoft Teams meeting time in productivity analytics, and sync projects, tasks, and worklogs with Jira.
* **Direct API access**: Generate an access token to pull We360.ai data into your own scripts, dashboards, or reporting tools.
* **Custom integrations**: We360.ai also builds tailored integrations—including additional HRMS systems such as Workday, payroll pipelines, project and task platforms, and case-management systems. Contact the We360.ai team to discuss your requirements.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.we360.ai/reference/work-and-time-management/user-interfaces/portal/settings-center/integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
