# Slack

Configure Slack notifications

* [`sfp server slack delete`](#sfp-server-slack-delete)
* [`sfp server slack list`](#sfp-server-slack-list)
* [`sfp server slack manifest`](#sfp-server-slack-manifest)
* [`sfp server slack setup`](#sfp-server-slack-setup)
* [`sfp server slack status`](#sfp-server-slack-status)
* [`sfp server slack test`](#sfp-server-slack-test)
* [`sfp server slack update`](#sfp-server-slack-update)

## `sfp server slack delete`

Delete (deactivate) Slack workspace configuration

```
USAGE
  $ sfp server slack delete [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>]
    [--team-id <value>] [--all] [-f] [--loglevel trace|debug|info|warn|error|fatal]

FLAGS
  -e, --email=<value>              Email address for authenticated user. Ignored if --application-token is provided. Can
                                   be set via SFP_SERVER_USER env var.
  -f, --force                      Skip confirmation prompt
  -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).
      --all                        Delete all workspace configurations
      --loglevel=<option>          [default: info] logging level
                                   <options: trace|debug|info|warn|error|fatal>
      --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
      --team-id=<value>            Specific Team ID to delete

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Delete (deactivate) Slack workspace configuration

EXAMPLES
  $ sfp server slack delete

  $ sfp server slack delete --team-id T01ABC23DEF

  $ sfp server slack delete --all --force
```

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

## `sfp server slack list`

List all configured Slack workspaces

```
USAGE
  $ sfp server slack list [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>] [--all]
    [--loglevel trace|debug|info|warn|error|fatal]

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).
      --all                        Show all workspaces including inactive ones
      --json                       Output as JSON
      --loglevel=<option>          [default: info] logging level
                                   <options: trace|debug|info|warn|error|fatal>
      --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

DESCRIPTION
  List all configured Slack workspaces

EXAMPLES
  $ sfp server slack list

  $ sfp server slack list --all

  $ sfp server slack list --json
```

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

## `sfp server slack manifest`

Generate Slack app manifest for bot setup

```
USAGE
  $ sfp server slack manifest [--json] [-o <value>] [--app-name <value>] [--loglevel trace|debug|info|warn|error|fatal]

FLAGS
  -o, --output=<value>     [default: slack-app-manifest.json] Output file path for manifest
      --app-name=<value>   [default: codev] Slack app display name
      --loglevel=<option>  [default: info] logging level
                           <options: trace|debug|info|warn|error|fatal>

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Generate Slack app manifest for bot setup

EXAMPLES
  $ sfp server slack manifest

  $ sfp server slack manifest --output manifest.json

  $ sfp server slack manifest --app-name "codev"
```

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

## `sfp server slack setup`

Set up Slack bot integration with SFP server

```
USAGE
  $ sfp server slack setup [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>]
    [--manual] [--skip-test] [--loglevel trace|debug|info|warn|error|fatal]

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).
      --loglevel=<option>          [default: info] logging level
                                   <options: trace|debug|info|warn|error|fatal>
      --manual                     Manual setup mode - provide tokens directly
      --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
      --skip-test                  Skip connection test after setup

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Set up Slack bot integration with SFP server

EXAMPLES
  $ sfp server slack setup

  $ sfp server slack setup --manual

  $ sfp server slack setup --email admin@example.com
```

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

## `sfp server slack status`

Check Slack bot connection status

```
USAGE
  $ sfp server slack status [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>] [-d]
    [--loglevel trace|debug|info|warn|error|fatal]

FLAGS
  -d, --detailed                   Show detailed status information
  -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).
      --json                       Output as JSON
      --loglevel=<option>          [default: info] logging level
                                   <options: trace|debug|info|warn|error|fatal>
      --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

DESCRIPTION
  Check Slack bot connection status

EXAMPLES
  $ sfp server slack status

  $ sfp server slack status --detailed

  $ sfp server slack status --json
```

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

## `sfp server slack test`

Send a test message via Slack bot

```
USAGE
  $ sfp server slack test [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>] [-c
    <value>] [-m <value> | -q <value>] [-i] [--loglevel trace|debug|info|warn|error|fatal]

FLAGS
  -c, --channel=<value>            Channel or user to send test message to (e.g., #general, @username)
  -e, --email=<value>              Email address for authenticated user. Ignored if --application-token is provided. Can
                                   be set via SFP_SERVER_USER env var.
  -i, --interactive                Interactive mode - choose from test scenarios
  -m, --message=<value>            Custom message to send
  -q, --query=<value>              Test AI query to process
  -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).
      --loglevel=<option>          [default: info] logging level
                                   <options: trace|debug|info|warn|error|fatal>
      --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
  Send a test message via Slack bot

EXAMPLES
  $ sfp server slack test

  $ sfp server slack test --channel general

  $ sfp server slack test --channel @username --message "Custom test message"

  $ sfp server slack test --channel "#random" --query "What is the build status?"
```

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

## `sfp server slack update`

Update Slack bot tokens and configuration

```
USAGE
  $ sfp server slack update [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>]
    [--bot-token <value>] [--app-token <value>] [--signing-secret <value>] [--team-id <value>] [--team-name <value>]
    [--all] [--from-env] [--loglevel trace|debug|info|warn|error|fatal]

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).
      --all                        Update all tokens interactively
      --app-token=<value>          New App-Level Token for Socket Mode (xapp-...)
      --bot-token=<value>          New Bot User OAuth Token (xoxb-...)
      --from-env                   Update from environment variables
      --loglevel=<option>          [default: info] logging level
                                   <options: trace|debug|info|warn|error|fatal>
      --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
      --signing-secret=<value>     New Signing Secret
      --team-id=<value>            Slack Team/Workspace ID (starts with T)
      --team-name=<value>          Slack Workspace name

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Update Slack bot tokens and configuration

EXAMPLES
  $ sfp server slack update

  $ sfp server slack update --bot-token xoxb-new-token

  $ sfp server slack update --app-token xapp-new-token

  $ sfp server slack update --signing-secret new-secret

  $ sfp server slack update --all
```

*See code:* [*src/commands/server/slack/update.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/sfp-community/cli-reference-v51-release-v3/server/slack.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.