Skip to main content

Slack

Fancified

Slack for fancy-flow — as four imported, versioned packages, one per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs change.

Runtime Package Install
Authoring surface (every host) @particle-academy/slack-ui npm install @particle-academy/slack-ui
Node @particle-academy/slack-js npm install @particle-academy/slack-js
PHP 8.4+ particle-academy/slack-php composer require particle-academy/slack-php
Python 3.11+ fancy-slack pip install fancy-slack

The ui package is the editor surface and is React on every host — a PHP or Python project installs it and its own runtime package, and never the js one.

What it costs you

One dependency: @particle-academy/fancy-connector-core (or particle-academy/fancy-connector-core on Composer), which the js and php packages pull in themselves. The Python package has zero runtime dependencies.

No Slack SDK. Plain HTTP, deliberately: a vendor SDK is third-party code subject to the kit's full approval bar, and one per provider is hundreds of dependencies nobody is tracking.

Setting it up

Everything below is generated from provider/manifest.json, so it cannot disagree with what the packages do.

Credentials

A Slack connection holds 5 values.

Two kinds of value, and mixing them up matters. A provider credential is ONE value for the whole installation — an OAuth app's client secret serves every connected account. An account credential is one per connected account. A host that stores the second where it stores the first lets one account's credentials reach another's.

Field Scope Secret Where it comes from
Client ID per installation not secret The Slack app client ID shared by the installation.
Client secret per installation secret The matching Slack app client secret used by OAuth V2.
Bot access token per connected account secret The workspace installation's rotating bot token. Token rotation must be enabled; the token expires after 12 hours.
Refresh token per connected account secret The workspace installation's single-use refresh token. Persist Slack's replacement after every refresh.
Signing secret (optional) per installation secret The Slack app's signing secret, from Basic Information. One value for the whole app, not per workspace. Required only by the block_actions trigger.

Authorising

Slack uses OAuth2 (authorization_code). The package DECLARES the exchange; the HOST performs it — a consent screen needs a browser, a redirect URI and somewhere to persist the result, and all three belong to the host.

The refresh tokens ROTATE, and they are single use. Every refresh returns a new one and spends the one submitted, so replaying a spent token revokes the ENTIRE grant — the user is signed out, with nothing in the failure that says why.

Two consequences, both of which a host gets wrong by default:

  1. Do not RETRY a failed refresh with the same token. A response that arrived but was not persisted — a crash between the reply and the write — turns the reflexive retry into a replay.
  2. Do not refresh CONCURRENTLY. Two workers refreshing at once means one of them replays.

Persist the returned token before using the access token it came with.

The estate

Slack has a test estate on the same host, reached with credentials from a SEPARATE test account you register. Selecting sandbox mode uses those credentials.

Install the app into a dedicated development workspace or Slack developer sandbox. Messages are real inside that workspace, but its users and data are separate from production. Developer sandboxes expire by default and have feature and integration limits.

What it can do

Actions

message_post — Slack message

Post a text message to a Slack channel or conversation.

POST /api/chat.postMessage · unsafe to replay — a retried durable run does it TWICE

Input Required What it is
channel yes The encoded channel, private group, direct-message or group-message conversation ID visible to the installed app.
text yes The message's top-level text. Keeping meaningful text here also gives screen readers a complete fallback when richer blocks are added elsewhere.
blocks no Optional Block Kit layout: a JSON array of blocks, including buttons. Message text is still required and is what screen readers and notifications show.

message_update — Slack message update

Replace the text and blocks of a Slack message the app posted.

POST /api/chat.update · idempotent — safe to replay

Input Required What it is
channel yes The conversation ID holding the message, as returned when it was posted or carried in a click.
ts yes The message's ts, its stable identifier within the channel.
text yes The replacement top-level text, kept as the accessible fallback for the blocks.
blocks no Optional replacement Block Kit layout: a JSON array of blocks.

user_lookup_by_email — Slack user lookup by email

Find the Slack user in this workspace who has a given email address.

GET /api/users.lookupByEmail · reads only — safe to replay

Input Required What it is
email yes The email address to look up. Requires the users:read.email scope.

Triggers

block_actions — Slack button click

Start when someone clicks a button or picks from a menu in a Slack message the app posted.

Delivered by webhook, and the signature is verified before anything runs.

You have to set this up with the provider first:

In the Slack app's Interactivity & Shortcuts settings, turn interactivity on and set the Request URL to the route your host mounts for this trigger, then put the app's signing secret (Basic Information) on the connection as signingSecret. Slack shows the user an error unless the request is answered with a 200 within 3 seconds, so the host must acknowledge FIRST and run the graph after.

Run it before you have credentials

Every operation ships a faker, whether or not Slack has a sandbox. Set a node's mode to fake and it returns the shape Slack actually publishes — the same field names, deterministically — so you can wire the downstream nodes before touching an account, a key, or a network.

This repository is generated

provider/ is the source. Everything under packages/ is emitted from it and must not be hand-edited — CI regenerates and diffs on every push, and the next protocol sync destroys anything it finds. See AGENTS.md.

Two namespaces, which do not match on purpose

The repo is github.com/Fancy-Friends/slack; the packages publish under particle-academy. Nothing derives one from the other — the names come from weaver's friends.json and nowhere else.

Licence

MIT.

Metadata

Release files for fancy-slack 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 fancy-slack 0.3.0
File Size Uploaded Provenance Actions
fancy_slack-0.3.0.tar.gz 26.5 kB Without provenance Details for fancy_slack-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fancy-slack 0.3.0
File Interpreter ABI Platform Actions
fancy_slack-0.3.0-py3-none-any.whl Python 3 none any Details for fancy_slack-0.3.0-py3-none-any.whl

Total release size: 56.6 kB

Release files / fancy_slack-0.3.0.tar.gz

Download URL fancy_slack-0.3.0.tar.gz
Size 26.5 kB
Tags Source
SHA-256 checksum
How to use checksums
40661e80c5c5857ffa4cce5d02e4d4e1051e17c2941d2ae77c8bd29454e9d9dd
BLAKE2b-256 checksum
How to use checksums
33683616152ce234aed5a9671ded93d5b21b788ba613be0c0c86a18eb0f790a3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

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

Download URL fancy_slack-0.3.0-py3-none-any.whl
Size 30.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
acabd060a1440d56195d4ab778647a4a22d1b67c1c5fd49147dbeba43ceeb499
BLAKE2b-256 checksum
How to use checksums
e7671561d0bfcf147666a46b21453d5f3e8bf3d6aaf0fbdaf9a7f6921a5b586e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

Security for fancy-slack 0.3.0

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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