interloper-slack
Slack notifications for interloper runs: a SlackHook that posts a run
outcome to a channel, and the SlackConnection that holds the bot token.
The hook is the notification counterpart to core's WebhookHook — same
events, but the payload is a message a human reads rather than a document a
service parses.
Setup
- Create a Slack app (From scratch) at api.slack.com/apps.
- Under OAuth & Permissions, add these bot token scopes:
chat:write— post the notificationchannels:read,groups:read— populate the channel picker
- Install to Workspace and copy the bot user token (
xoxb-…). - Invite the bot to each channel it posts to (
/invite @your-app). Slack rejectschat.postMessagewithnot_in_channelotherwise.
One connection serves the whole workspace; each hook picks its own channel.
Usage
import interloper as il
from interloper_slack import SlackConnection, SlackHook
hook = SlackHook(
connection=SlackConnection(bot_token="xoxb-..."),
channel="C0123456789",
watches=[my_source],
events=["run_failed"],
)
The token also loads from the environment (SLACK_BOT_TOKEN), so
SlackConnection() works with no arguments.
events defaults to ["run_failed"] like every hook — the alert most teams
want. Add "run_completed" for a full-chatter channel.
In a deployed instance you configure this through the UI instead: add a Slack connection, then a Slack hook watching the source or job you care about. The scheduler's hook evaluator fires it on terminal runs.
Message shape
❌ *Facebook Ads* failed
Run `9f3c…` · partition `2026-07-30`
HTTPStatusError: 429 Too Many Requests
The headline also travels as the message's text, so notification previews
and screen readers get the outcome without parsing blocks.
Notes
Every Slack call goes through the connection's client — a cached_property
il.RESTClient with il.HTTPBearerAuth, like every other connection in the
workspace. That client owns the base URL, the token, and the connection pool,
so callers name a path and nothing else; the channel picker paginates with
il.JSONCursorPaginator over Slack's response_metadata.next_cursor.
The client is sync, where most connections' are async. The two consumers are a hook firing (sync by contract) and a form lookup — neither has independent requests to overlap, and the API process runs sync providers in a thread, so it never blocks the event loop.
The one thing the framework can't cover is that Slack answers a rejected
call with HTTP 200 and {"ok": false, "error": "..."}, so raise_for_status()
alone lets failures pass silently. Each call site checks ok itself and raises
RuntimeError with Slack's own error code — the same shape as the other
connections that face an in-body error flag. For the paginated picker that
check lives in the data_selector, since paginate only raises for HTTP
status.
A failed firing is recorded on the hook's firing claim (as hook_failed) and
is not retried.
Metadata
Release files for interloper-slack 0.101.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| interloper_slack-0.101.1.tar.gz | 6.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| interloper_slack-0.101.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.3 kB
Release files / interloper_slack-0.101.1.tar.gz
| Download URL | interloper_slack-0.101.1.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
932be3ded02cdb162497029169fa351c7be7df5eab123f69cbfa0fe75ba682ba
|
|
BLAKE2b-256 checksum How to use checksums |
3325d6db3ca9fb83016cfa16df8a041fdccb1d5a8d8b4b3873cdbd90657adabb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / interloper_slack-0.101.1-py3-none-any.whl
| Download URL | interloper_slack-0.101.1-py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
217105dd17fa3f744ee2a91094f8fc39938f53d9986734fdcf11395c87f30201
|
|
BLAKE2b-256 checksum How to use checksums |
115312b4e1989d0c4cb6e096eac932560622df08311f7bdbc6a92e591eaddc34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
