Skip to main content

Python Slack Hooks

Pypi - Badge PyPI - Version Codecov
Python Versions

This library defines the contract between the Slack CLI and Bolt for Python.

Overview

This library enables inter-process communication between the Slack CLI and applications built with Bolt for Python.

When used together, the CLI delegates various tasks to the Bolt application by invoking processes ("hooks") and then making use of the responses provided by each hook's stdout.

For a complete list of available hooks, read the Supported Hooks section.

Requirements

The latest minor version of Bolt v1 is recommended.

Usage

A Slack CLI-compatible Slack application includes a ./slack.json file that contains hooks specific to that project. Each hook is associated with commands that are available in the Slack CLI. By default, get-hooks retrieves all of the supported hooks and their corresponding scripts as defined in this library.

The CLI will always use the version of the python-slack-hooks that is specified in the project's requirements.txt.

Supported Hooks

The hooks currently supported for use within the Slack CLI include check-update, doctor, get-hooks, get-manifest, and start:

Hook Name CLI Command File Description
check-update slack update check_update.py Checks the project's Slack dependencies to determine whether or not any libraries need to be updated.
doctor slack doctor doctor.py Returns runtime versions and other system dependencies required by the application.
get-hooks All get_hooks.py Fetches the list of available hooks for the CLI from this repository.
get-manifest slack manifest get_manifest.py Converts a manifest.json file into a valid manifest JSON payload.
start slack run start.py While developing locally, the CLI manages a socket connection with Slack's backend and utilizes this hook for events received via this connection.

Overriding Hooks

To customize the behavior of a hook, add the hook to your application's /slack.json file, and provide a corresponding script to be executed.

When commands are run, the Slack CLI will look to the project's hook definitions and use those instead of what's defined in this library, if provided.

Below is an example /slack.json file that overrides the default start:

{
  "hooks": {
    "get-hooks": "python3 -m slack_cli_hooks.hooks.get_hooks",
    "start": "python3 app.py"
  }
}

Contributing

Contributions are always welcome! Please review the contributing guidelines for more information.

Release files for slack-cli-hooks 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for slack-cli-hooks 0.3.0
File Size Uploaded
slack_cli_hooks-0.3.0.tar.gz 9.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for slack-cli-hooks 0.3.0
File Interpreter ABI Platform
slack_cli_hooks-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 20.9 kB

Release files / slack_cli_hooks-0.3.0.tar.gz

Download URL slack_cli_hooks-0.3.0.tar.gz
Size 9.8 kB
Tags Source
SHA-256 checksum
How to use checksums
88e1e78528d94d686bdb46a6242d023975479472b97625aa73c1c953775d5663
BLAKE2b-256 checksum
How to use checksums
4a02abc3639125c62f756e852bb0d72aebc778b1d798b4561cfea44bf6062b7b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Feb 5, 2026.

Transparency log

Release files / slack_cli_hooks-0.3.0-py3-none-any.whl

Download URL slack_cli_hooks-0.3.0-py3-none-any.whl
Size 11.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3639d4f5b56f822da7fb93660996849df5d2b8544cca968a46ee012b89c94fd1
BLAKE2b-256 checksum
How to use checksums
0f45e183cc4e65ae3e092b89134f4016fa83982318a8ea1a3bb6c5769adf4033
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Feb 5, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page