> ## Documentation Index
> Fetch the complete documentation index at: https://felan.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect source control, communication, issue tracking, documentation, design, test management, and event providers to Felan.

Integrations give Felan team-scoped access to external services. Connections select provider skills that delegated agents can use according to their permissions. The page has two peer views: **Connections** manages configured providers and recovery states, while **Catalog** shows integrations available to add.

## Set up a connection

<Steps>
  <Step title="Select a team">
    Select the Felan team that should own the connection.
  </Step>

  <Step title="Open Integrations">
    Choose **Integrations** from the main navigation. The page opens **Connections** when the team has a configured provider; otherwise it opens **Catalog**.
  </Step>

  <Step title="Connect or configure">
    In **Catalog**, open an integration with **View details**. In **Connections**, open a provider with **Manage**, **Continue setup**, or **Reauthorize**. OAuth providers use **Connect**; credential-based and app-based providers use **Configure**.
  </Step>

  <Step title="Complete provider setup">
    Finish the provider authorization or enter the requested team credential. Some providers then ask you to select projects, repositories, or a channel within the external service.
  </Step>
</Steps>

OAuth refresh is managed by the connection service. Custom credentials are stored encrypted. Removing a connection disables it for the whole Felan team.

## Available integrations

The provider ID is the compatibility identifier used by runtime catalogs, API filters, webhooks, and automation event providers.

| Integration                                                                       | Provider ID               | Connection method                   | Supported role                     |
| --------------------------------------------------------------------------------- | ------------------------- | ----------------------------------- | ---------------------------------- |
| [Asana](/docs/integrations/asana)                                                      | `asana`                   | OAuth                               | Tasks and events                   |
| [Azure DevOps](/docs/integrations/azure-devops)                                        | `azure-devops`            | Organization URL and PAT            | Boards and Test Plans              |
| [Bitbucket Server](/docs/integrations/bitbucket-server)                                | `bitbucket-server`        | Base URL and PAT                    | Self-hosted source control         |
| [ClickUp](/docs/integrations/clickup)                                                  | `clickup`                 | OAuth                               | Tasks                              |
| [Confluence](/docs/integrations/confluence)                                            | `confluence`              | OAuth                               | Read-only documentation            |
| [Figma](/docs/integrations/figma)                                                      | `figma`                   | OAuth                               | Read-only design context           |
| [GitHub](/docs/integrations/github)                                                    | `github`                  | Authorization flow                  | Source control and events          |
| [GitHub Enterprise Cloud](/docs/integrations/github-enterprise-cloud)                  | `github-enterprise-cloud` | Tenant GitHub App                   | Data-residency source control      |
| [GitLab](/docs/integrations/gitlab)                                                    | `gitlab`                  | OAuth                               | Source control, issues, and events |
| [Jira Cloud](/docs/integrations/jira)                                                  | `jira`                    | OAuth                               | Issues and events                  |
| [Jira Server or Data Center](/docs/integrations/jira#jira-server-or-data-center-setup) | `jira-server`             | Base URL and credential             | Self-hosted issues and events      |
| [Linear](/docs/integrations/linear)                                                    | `linear`                  | OAuth                               | Issues and events                  |
| [Microsoft Teams](/docs/integrations/teams)                                            | `teams`                   | Felan Teams app and connection code | Team messaging                     |
| [Notion](/docs/integrations/notion)                                                    | `notion`                  | OAuth                               | Read-only documentation            |
| [Slack](/docs/integrations/slack)                                                      | `slack`                   | OAuth                               | Team messaging                     |
| [Supabase](/docs/integrations/supabase)                                                | `supabase`                | OAuth                               | Read-only database research        |
| [Testiny](/docs/integrations/testiny)                                                  | `testiny`                 | API key and project ID              | Test cases and plans               |
| [Vercel](/docs/integrations/ci-cd#provider-native-events)                              | `vercel`                  | Webhook secret                      | Deployment events                  |
| [Zephyr Scale](/docs/integrations/zephyr)                                              | `zephyr`                  | API token and project key           | Test cases and folders             |

## How Felan uses connections

Felan selects integration skills from active provider IDs and projects only the required credentials into isolated agent workspaces. Supabase receives a `database:read` OAuth token and selected project reference; its bundled CLI calls the provider's read-only SQL endpoint. A provider connection makes its capability available; Felan still follows the request, persona boundaries, and confirmation rules before performing external writes.

For custom CI events, use the [team event endpoint](/docs/integrations/ci-cd). For public API authentication and team scoping, see [Authentication](/docs/api-reference/authentication).