Skip to main content
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

1

Select a team

Select the Felan team that should own the connection.
2

Open Integrations

Choose Integrations from the main navigation. The page opens Connections when the team has a configured provider; otherwise it opens Catalog.
3

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.
4

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.
OAuth refresh is managed by the connection service. Custom credentials are stored encrypted. Removing a connection disables it for the whole Felan team.

​
Communication channels

Onboarding uses the signed-in team owner’s email as the initial update destination and does not require a messaging integration. Open Integrations → Channels to add Slack, Microsoft Teams, or additional email recipients and choose which configured channel is primary. The selected primary channel receives automatic Felan updates; source-control connections remain a separate setup step.

​
Available integrations

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

​
How Felan uses connections

Felan selects integration skills from active provider IDs and projects only the required credentials into isolated agent workspaces. Axiom receives its customer API token and approved edge subdomain; its bundled CLI exposes only bounded read operations. Supabase receives a database:read OAuth token and selected project reference; its bundled CLI calls the provider’s read-only SQL endpoint. Jira Server receives its base URL and team credential for the bundled Jira Server CLI; Bitbucket Server credentials reach only the root agent, which owns repository publication, through the bundled Bitbucket Server CLI. Vercel agent access receives a scoped VERCEL_TOKEN for the official CLI, while a webhook-only Vercel setup does not select the Vercel skill. Remote MCP OAuth tokens remain in Nango and are fetched ephemerally by the parent runtime rather than projected into workspaces. A provider connection makes its capability available; Felan still follows the request, persona boundaries, and confirmation rules before performing external writes. To receive provider events or send events from a custom system, see Webhooks. For public API authentication and team scoping, see Authentication.