# Integration

Configure external integrations

* [`sfp server integration create`](#sfp-server-integration-create)
* [`sfp server integration delete`](#sfp-server-integration-delete)
* [`sfp server integration get`](#sfp-server-integration-get)
* [`sfp server integration list`](#sfp-server-integration-list)

## `sfp server integration create`

Create an integration for specific projects or globally

```
USAGE
  $ sfp server integration create --provider <value> --auth-type <value> [--json] [--repository <value>] [-e <value>] [-t
    <value>] [--sfp-server-url <value>] [--project <value>... | --global] [--token <value>] [--client-id <value>]
    [--client-secret <value>]

FLAGS
  -e, --email=<value>              Email address for authenticated user. Ignored if --application-token is provided. Can
                                   be set via SFP_SERVER_USER env var.
  -t, --application-token=<value>  Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
                                   (CLI flags take precedence over env vars).
      --auth-type=<value>          (required) Authentication type (e.g., pat, oauth, app)
      --client-id=<value>          OAuth client ID
      --client-secret=<value>      OAuth client secret
      --global                     Store as global integration (available to all projects)
      --project=<value>...         Project identifier (can be specified multiple times)
      --provider=<value>           (required) Integration provider (e.g., github)
      --repository=<value>         The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
                                   for Azure DevOps
      --sfp-server-url=<value>     URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
                                   config:set server-url
      --token=<value>              Personal access token for PAT auth

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Create an integration for specific projects or globally
```

*See code:* [*src/commands/server/integration/create.ts*](https://source.flxbl.io/flxbl/sfp-pro)

## `sfp server integration delete`

Delete an integration

```
USAGE
  $ sfp server integration delete -i <value> [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url
    <value>]

FLAGS
  -e, --email=<value>              Email address for authenticated user. Ignored if --application-token is provided. Can
                                   be set via SFP_SERVER_USER env var.
  -i, --id=<value>                 (required) Integration ID to delete
  -t, --application-token=<value>  Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
                                   (CLI flags take precedence over env vars).
      --repository=<value>         The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
                                   for Azure DevOps
      --sfp-server-url=<value>     URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
                                   config:set server-url

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Delete an integration

EXAMPLES
  $ sfp server integration delete --id <integration-id>

  $ sfp server integration delete --id <integration-id> --json
```

*See code:* [*src/commands/server/integration/delete.ts*](https://source.flxbl.io/flxbl/sfp-pro)

## `sfp server integration get`

Get integration credentials by project

```
USAGE
  $ sfp server integration get [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>]
    [--provider <value>] [--project <value>]

FLAGS
  -e, --email=<value>              Email address for authenticated user. Ignored if --application-token is provided. Can
                                   be set via SFP_SERVER_USER env var.
  -t, --application-token=<value>  Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
                                   (CLI flags take precedence over env vars).
      --project=<value>            Filter by project identifier
      --provider=<value>           Filter by provider (e.g., github)
      --repository=<value>         The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
                                   for Azure DevOps
      --sfp-server-url=<value>     URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
                                   config:set server-url

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Get integration credentials by project
```

*See code:* [*src/commands/server/integration/get.ts*](https://source.flxbl.io/flxbl/sfp-pro)

## `sfp server integration list`

List all integrations

```
USAGE
  $ sfp server integration list [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>] [-p
    <value>]

FLAGS
  -e, --email=<value>              Email address for authenticated user. Ignored if --application-token is provided. Can
                                   be set via SFP_SERVER_USER env var.
  -p, --provider=<value>           Filter by provider (github, jira)
  -t, --application-token=<value>  Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
                                   (CLI flags take precedence over env vars).
      --repository=<value>         The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
                                   for Azure DevOps
      --sfp-server-url=<value>     URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
                                   config:set server-url

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List all integrations

EXAMPLES
  $ sfp server integration list

  $ sfp server integration list --provider github

  $ sfp server integration list --json
```

*See code:* [*src/commands/server/integration/list.ts*](https://source.flxbl.io/flxbl/sfp-pro)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flxbl.io/flxbl/sfp/cli-reference-v51-release-v3/server/integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.