Commands

integration

Work with Sentry integrations

Commands

`sentry integration list [<org/project>]`

List installed integrations

Arguments:

Argument	Description
`[<org/project>]`	<org>/ (all), <org>/<name> or <name> (a project, else matching names), or a name glob (<org>/web-*)

Options:

Option	Description
`-n, --limit <limit>`	Maximum number of integrations to list (default: "25")
`-f, --fresh`	Bypass cache, re-detect projects, and fetch fresh data
`-c, --cursor <cursor>`	Navigate pages: "next", "prev", "first" (or raw cursor string)

Examples:

# List installed integrations (auto-detect org)
sentry integration list

# List integrations in a specific org
sentry integration list my-org/

# Fetch the next page
sentry integration list my-org/ -c next

# Only integrations whose name or provider matches a glob
sentry integration list 'my-org/git*'

# Integrations named like 'GitHub' (fuzzy when nothing matches exactly)
sentry integration list my-org/githb

# Output as JSON
sentry integration list --json

`sentry integration delete [<org>/]<integration-id>`

Remove an installed integration

Arguments:

Argument	Description
`[<org>/]<integration-id>`	[<org>/]<integration-id> - Integration to remove

Options:

Option	Description
`-y, --yes`	Skip confirmation prompt
`-f, --force`	Force the operation without confirmation
`-n, --dry-run`	Show what would happen without making changes

Examples:

# Remove an integration (auto-detect org)
sentry integration delete 12345

# Preview removing an integration
sentry integration delete my-org/12345 --dry-run

# Remove without the confirmation prompt
sentry integration delete my-org/12345 --yes

All commands support --json for machine-readable output and --fields to select specific JSON fields.

Permissions

Removing an integration needs the org:integrations permission, which Sentry grants to org owners and managers. If your CLI login predates that scope, sentry integration delete asks you to re-authorize before removing anything. This only happens in interactive runs: with --yes or --json the CLI never starts the authorization flow, so run it once without those flags first.

Installing new integrations from the CLI is not supported yet.