---
name: "Slack (workspace apps)"
description: Build and deploy Slack apps, manifests, workflows, and functions through the official Slack CLI.
version: 1
situations: slack app, manifest, workflow, slack function, deploy
requires-secrets:
requires-packages:
requires-connector: slack-workspace
---

# Slack CLI (workspace apps)

Runs through Slack's official CLI in your **bash** tool, for **building and deploying Slack apps**.

**This is not the way to read or send Slack messages.** 00 has a first-class Slack channel for that —
if the operator wants you to talk in Slack, point them at **Settings → Channels → Slack** instead of
reaching for this CLI. Using an app-development tool to scrape a workspace is the wrong shape and it
will need permissions nobody intended to grant.

## First, know which workspace

```
slack auth list
```

Not authorized? **Skill store → Slack → Connect** — the login asks the operator to paste a
`/slackauthticket` command into Slack and hand a challenge code back.

## Read

```
slack app list
slack manifest info
slack function list
slack trigger list
slack activity --tail        # live app logs; stop it when you have what you need
```

## Build and deploy

```
slack create my-app --template …
slack run                    # local dev instance, tied to this terminal
slack deploy                 # ask first — this installs into a real workspace
slack trigger create --trigger-def triggers/example.ts
```

`slack deploy` and `slack install` change what a workspace's members can see and run. Name the app
and the workspace, and wait for a yes.

## Never without being asked in this turn

`slack app delete`, `slack uninstall`, deleting triggers or datastores, and deploying to a workspace
the operator did not name.