Skip to main content

​
What this does

A connector lets one workspace use a provider account. The provider sends credentials directly to agentsfleet after browser approval. Use a secret instead when you must paste a static API key yourself.

​
Before you begin

You must own the account that holds the workspace. You also need permission to connect the provider account. Supported providers are GitHub, Slack, Zoho Desk, Jira, and Linear. Connect apps lists the providers offered by the platform. Opening this page creates no connection. Connected means the workspace holds saved authorization. Each card shows its account label when available. The page does not contact providers to check access. Provider calls can still fail if access expires or is revoked. A connection grants only the approved permissions. It does not add every action the provider offers; for example, the current Zoho Desk connection supports reading organization data. If a provider needs platform setup, choose Request access to register your interest. This does not connect the provider.

​
Steps

  1. Open the account menu and choose Connect apps in the dashboard.
  2. Choose a provider and click Connect.
  3. Approve the requested access on the provider’s website.
  4. Save a fleet that uses the provider, then approve its integration grant from the setup checks or Approvals.
The workspace owns the connector. Each fleet needs a separate approved grant before it can use the connection. If setup remains installing after approval, run agentsfleet resume <FLEET_ID>. Copy <FLEET_ID> from agentsfleet list. A connected Slack workspace also lets a fleet answer mentions in a channel. Posting that answer needs no grant, because agentsfleet posts it itself. See Answer mentions in Slack. A fleet that answers in Slack and also calls another provider still needs that provider’s approved grant. For example, it needs a GitHub grant to open a draft pull request.

​
Verify it works

The provider state should be connected. A fleet without an approved grant cannot use the connector.

​
Common problems

not_connected means no saved connection is available. Start the connection again from the dashboard. If the browser return fails or exceeds 25 seconds, return to Connect apps from the recovery page. Check its status, then start a fresh attempt if needed. Never reuse a previous callback URL. If a provider rejects saved access, reconnect it and retry the fleet action. The connection page cannot detect revocation before a provider call. When an expiring access token is rejected, the next connector call uses the saved refresh token. A revoked refresh token requires reconnection. One GitHub App installation can belong to only one workspace. Another workspace receives 403 and keeps no new connection.

​
Remove or undo

Disconnect the connector from Connect apps. agentsfleet removes the saved connection and stops routing that provider’s events to the workspace. Deleting the connector’s secret, such as github, does the same. Revoke the application from the provider’s account settings. The next connector call fails until you reconnect with valid access. Remove any fleet integration grants that should no longer use the provider. Revoking a connector does not delete fleet history.