> 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/deployment-and-it-ops/integrations-and-api-access/integrations/portal-integrations.md).

# Portal Integrations

Set up integrations that are available directly in the We360.ai portal.

Use portal integrations when you want a guided setup. They are the fastest way to connect supported services.

## Currently available in the portal

These integrations are currently available in **Settings → Integrations**:

* Microsoft Teams
* GreytHR Push Punch Logs
* Zoho Push Punch Logs
* Keka Push Punch Logs
* Keka Fetch Attendance
* Jira

## Documented guides

The following guides are documented right now:

<table data-view="cards"><thead><tr><th>Guide</th><th>Description</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Microsoft Teams</td><td>Connect Microsoft Teams to improve productivity analysis using meeting data.</td><td><a href="/deployment-and-it-ops/integrations-and-api-access/integrations/portal-integrations/microsoft-teams.md">Microsoft Teams</a></td></tr><tr><td>GreytHR Push Punch Logs</td><td>Push punch-in and punch-out logs from we360.ai to GreytHR.</td><td><a href="/deployment-and-it-ops/integrations-and-api-access/integrations/portal-integrations/greythr-push-punch-logs.md">GreytHR Push Punch Logs</a></td></tr><tr><td>Zoho Push Punch Logs</td><td>Push punch-in and punch-out logs from we360.ai to Zoho People.</td><td><a href="/deployment-and-it-ops/integrations-and-api-access/integrations/portal-integrations/zoho-push-punch-logs.md">Zoho Push Punch Logs</a></td></tr><tr><td>Keka Fetch Attendance</td><td>Fetch first-in and last-out attendance records from Keka into we360.ai.</td><td><a href="/deployment-and-it-ops/integrations-and-api-access/integrations/portal-integrations/keka-fetch-attendance.md">Keka Fetch Attendance</a></td></tr><tr><td>Jira</td><td>Sync projects, tasks, and worklogs between we360.ai and Jira.</td><td><a href="/deployment-and-it-ops/integrations-and-api-access/integrations/portal-integrations/jira.md">Jira</a></td></tr></tbody></table>

## When to use portal integrations

* You want the fastest setup path.
* You want configuration managed in the portal.
* You do not need a custom API workflow.

{% hint style="info" %}
More portal integration guides can be added here one by one. Keep prerequisites, setup, sync behavior, and troubleshooting together.
{% endhint %}


---

# 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/deployment-and-it-ops/integrations-and-api-access/integrations/portal-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.