feat(integrations): add the lfx-slack bundle with Web API actions on connections

[erichare]

feat(integrations): add the lfx-slack bundle with Web API actions on connections

Base: feat/int-11-lfx-microsoft (INT-11). That branch bases on feat/int-5-oauth-broker (#14935); retarget to release-1.13.0 once #14906..#14935 and INT-11 merge.

Restacked on INT-11

This branch was built independently from the INT-5 tip (5615cd03a3) and then merged with
feat/int-11-lfx-microsoft, which shares every bundle registration seam. Review this PR's own diff
against feat/int-11-lfx-microsoft, not against feat/int-5-oauth-broker — the merge commit carries
the resolutions and its message lists them one by one. In short: INT-11's entry comes first in every
append-only list (pyproject.toml x3, bundle_profiles.json, release_inventory_contract.json,
migration_table.json, connection-oauth.mdx); the duplicated "Develop/connection-oauth" sidebar
entry was reduced to INT-11's copy inside Authentication and authorization, beside the Entra
runbook it links to; enterprise-hardened.lock.json was regenerated with
manage_bundle_profiles.py compile, not hand-merged; and uv.lock needed no re-resolution
(uv lock --offline and uv lock --check both accept it unchanged, 857 packages, nothing fetched).

Two problems only the combined tree can surface, both fixed in the merge commit:

• scripts/ci/check_capability_manifests.py — added by this PR, generic over every bundle — reached
  lfx-microsoft's manifest for the first time and rejected it nine times. Eight are INT-11's
  deliberate offline_access deviation (Entra never echoes the scope and the resolver computes
  required - granted literally, so transcribing the matrix would fail every Microsoft resolution;
  already pinned by src/bundles/microsoft/tests/test_capabilities_manifest_contract.py); the ninth is
  the short "Microsoft 365" provider label the bundle ships everywhere against the matrix's longer
  one. Neither bundle's shipped behaviour was changed. Instead the checker gained a
  DELIBERATE_DEVIATIONS table recording the exact expected values, so any other drift still fails
  and a deviation that has since converged is reported as stale rather than silently accepted.
  Mutation-checked, and covered by six new tests.
• INT-11's docs pages link to /bundles-microsoft, /entra-app-registration and /connection-oauth
  absolutely; those slugs exist only on the next version, so docs $ npm run build failed with four
  broken links. Converted to relative .mdx links — the same form this PR already had to use for
  /bundles-slack (see the note below). Worth folding back into INT-11 if that branch moves.

Summary

• Adds src/bundles/slack (distribution lfx-slack) with the seven actions the INT-1 discovery gate froze in design/dedicated-integrations/matrices/slack.json: Slack: Search / Read Thread / Send Message / Create Canvas (as user) and Slack: Post Message / Add Reaction / List Channel Members (as app).
• All seven run on the Slack Web API through slack_sdk, per decisions/substrate-slack.md (Option B) and the matrix's substrate_notes. slack_sdk and aiohttp are new dependencies; aiohttp is declared explicitly because AsyncWebClient imports it and cross-bundle-test.yml installs only declared deps.
• capabilities.v1.json is lifted mechanically from the matrix (ids, display names, identities, required and conditional scopes, deployment contexts, component classes) and declares the two named auth profiles the connection contract requires: slack-user-oauth and slack-bot-install. Policy keys are integrations.slack.<user|bot>.<verb>.
• Adds a Slack error normalizer. Slack answers HTTP 200 with {"ok": false, "error": ...}, so lfx's status-code-only fallback would have reported an expired token or a missing scope as provider-unavailable and the frontend's code-keyed reconnect/grant affordances would never fire. invalid_auth/token_expired/token_revoked/account_inactive/not_authed → auth-expired; missing_scope (with needed) → scope-missing; ratelimited/HTTP 429 → rate-limited with Retry-After; not_allowed_token_type/channel_not_found/… → action-unsupported; everything else → provider-unavailable.
• Adds an additive optional ResolvedCredential.identity (lfx) populated from the connection row's executing_identity (langflow-base). Slack user and bot tokens share scope names — chat:write is both a User Token Scope and a Bot Token Scope — so granted_scopes cannot tell them apart. A bot capability handed a user connection (or the reverse) now fails closed with connection-not-authorized before the first HTTP request. BUNDLE_API_VERSION stays 1; the changelog entry is required only because lfx/integrations is an in-scope surface.
• An auth-expired rejection spends the one reactive re-resolve CredentialLease allows and retries once. That is how a rotated Slack token is picked up: Slack tokens do not expire unless the app opted into rotation, so a rejection is the only signal.
• Runs the full INT-11 registration checklist: root pyproject.toml markers + uv.lock; bundle_profiles.json (enterprise-hardened) + recompiled enterprise-hardened.lock.json; release_inventory_contract.json for python-default and python-full, plus the source_roots entry test_contract_required_files_exist_in_sources needs; migration_table.json rows for the seven classes; the Slack sidebar group (the icon already existed); docs page, bundle list, graduated-install map, docs sidebar.
• Adds scripts/ci/check_capability_manifests.py (+ tests), generic over every bundle that declares integrations: it proves each shipped capabilities.v1.json still agrees with its discovery-gate matrix. Extra capabilities and auth profiles are tolerated so TRG-5 can add its slack-app-token profile on top.
• The Web API response each component memoizes is cleared in _pre_run_setup, the framework's per-build reset hook. Without that, a Slack action inside a Loop (or any rebuilt vertex — Graph._set_cache_to_vertices_in_cycle forces output.cache=False while Vertex.build reuses one custom_component) would run once and then report that first response for every later iteration: N green statuses, one message in the channel. Sharing between a component's two outputs within one build is unchanged.
• The identity guard runs inside the integration_action span, so a fail-closed connection-not-authorized denial is counted in telemetry like any other integration error. It still fires before any HTTP request.
• Registers docs/docs/Develop/connection-oauth.mdx in the docs sidebar — it was unreachable — and extends its Slack section with both redirect URL forms, the per-action scope table for each identity, and a worked two-registration LANGFLOW_CONNECTION_OAUTH_REGISTRATIONS example.

Verification

Bundle suite, run exactly the way .github/workflows/cross-bundle-test.yml does (a clean venv holding only in-repo lfx + the bundle + pytest), on both PR-matrix Python legs:

uv venv --python 3.13 && uv pip install ./src/lfx ./src/bundles/slack pytest pytest-asyncio tomli
lfx extension validate src/bundles/slack/src/lfx_slack
  -> validate: ok (8 file(s) scanned)
python -m pytest src/bundles/slack/tests -q -m "not api_key_required"
  -> 56 passed, 3 deselected

# same, --python 3.10
  -> validate: ok (8 file(s) scanned);  56 passed, 3 deselected

The 3 deselected are the opt-in live-workspace suite (api_key_required).

lfx package suite (isolated, from src/lfx):

uv sync --dev --extra otel
uv run --no-sync pytest tests/unit/integrations \
    tests/integration/extension/test_pilot_slack_upgrade.py \
    tests/unit/extension tests/unit/services/connection -q
  -> 747 passed, 2 skipped

(The 2 skips are test_pilot_slack_upgrade.py's distribution checks, which self-skip when lfx-slack is absent from the isolated lfx venv — the same way test_pilot_paddle_upgrade.py does.)

Backend and release tooling, from the repo root:

uv run --no-sync pytest scripts/ci/ -q
  -> 208 passed   (200 before the restack; +8 for the deviation-table tests)
uv run --no-sync pytest src/backend/tests/unit/api/v1/test_connections.py \
    src/backend/tests/unit/api/v1/test_connection_identity.py \
    src/backend/tests/unit/services/connection \
    src/backend/tests/unit/test_bundle_lfx_pin.py \
    src/backend/tests/unit/test_build_component_index.py \
    src/backend/tests/unit/test_lfx_bundles_extras.py -q
  -> 64 passed, 4 skipped
uv run --no-sync python scripts/ci/check_capability_matrices.py        -> Capability matrices are complete.
uv run --no-sync python scripts/ci/check_capability_manifests.py       -> agree with their matrices (2 checked)
uv run --no-sync python scripts/ci/check_execution_principal_matrix.py -> matrix is complete
uv run --no-sync python scripts/ci/manage_bundle_profiles.py check     -> Bundle profiles and locks passed
uv run --no-sync python scripts/ci/sync_bundle_lfx_pin.py 1.13.0       -> unchanged: slack
uv run --no-sync python scripts/ci/check_components_frozen.py          -> no additions beyond the frozen baseline
uv run --no-sync python scripts/migrate/check_bare_names.py            -> ok
uv run --no-sync python scripts/migrate/check_migration_append_only.py --base feat/int-11-lfx-microsoft
  -> ok (entries 1027, +28)
uv run --no-sync python scripts/migrate/check_bundle_api_changelog.py --base 5615cd03a3 -> ok (both bundles' entries present)
uv run --no-sync python scripts/ci/bundle_release_plan.py plan --base-ref 5615cd03a3   -> "status": "ready"
uv sync --frozen                                                       -> ok, no re-resolution
uv lock --check --offline                                              -> Resolved 857 packages

(The 4 backend skips are pre-existing and unrelated: test_build_component_index.py self-skips with "build_component_index.py script not found".)

The release-inventory rows were also checked against a real built wheel, since check_release_inventory.py needs an installed wheel shape (in an editable checkout it reports missing required_files for every bundle, lfx-openai and lfx-google included):

uv build --wheel src/bundles/slack
  -> entry_points.txt: [langflow.extensions] lfx-slack = lfx_slack
  -> all three python-default required_files present in the wheel

Frontend and docs:

src/frontend $ npx jest src/utils/__tests__/sidebarBundles.test.ts  -> 6 passed (4 Slack/base + 2 Microsoft)
docs $ npm run build   -> Generated static files; 0 broken links, and no broken anchor
                          reported on the `next` docs version  (re-run after the restack)

Ruff (check + format --check) is clean on every changed Python path; detect-secrets-hook is clean with no .secrets.baseline additions.

Notes for the reviewer

• End-to-end runs still wait on INT-6. Graph.execution_principal defaults to ExecutionPrincipal.unknown(), and authorize_principal denies unknown for user and instance connections, so every Slack component run from the canvas, /api/v1/run, or a deployment fails closed until INT-6 stamps the principal. Only lfx run with LF_CONNECTION__SLACK__<NAME> works end to end today. INT-8 likewise has to ship the connection_ref renderer before the connection field is settable from the canvas; until then set it through tweaks or the API. The bundle is fully unit-tested against a fake resolver.
• Ticket QA lines about pinned MCP are superseded. Per DECISIONS.md, INT-9 ships the generic pinned mode separately in 1.13 and its Slack sample stacks on this branch: it adds pin fields plus a recorded, clearly-synthetic tools/list fixture to one existing capability (slack.user.search is the natural target, and keeps its component_ref). This PR ships no MCP substrate, and substrate-slack.md / estimate.md are amended by INT-9's PR, not this one.
• TRG-5 stacks on this branch and adds a third slack-app-token profile to the same capabilities.v1.json. The new manifest checker deliberately allows extra profiles and capabilities so that lands without a checker change.
• SSRF. SLACK_API_BASE_URL is a module constant and no component exposes a URL, host, or proxy input, so there is no user-controllable request target. lfx.utils.ssrf_transport builds httpx clients with DNS pinning and AsyncWebClient speaks aiohttp, for which lfx ships no equivalent; removing the surface entirely is the stronger guarantee. Two tests pin it (the constant, and "no component declares a request-target input"). If we would rather add an aiohttp connector to lfx.utils.ssrf_transport, that is a BUNDLE_API-surface change and belongs in its own PR.
• Backend locales/en.json is deliberately untouched. scripts/gp/extract_backend_strings.py walks lfx.components and reaches bundle components only through the lfx.components.<provider> compatibility shims that exist for components that moved out of the tree. lfx-slack is new and has no shim, and gp-backend-check.yml regenerates and auto-commits en.json on every PR touching src/bundles/**, so hand-written Slack keys would be deleted on the next run. paddle, confluent, valkey and nextplaid have no keys either.
• Restack note (done). INT-11 added the identical "Develop/connection-oauth" entry to docs/sidebars.js. The restack keeps one copy — INT-11's, inside Authentication and authorization — so this PR no longer touches that part of the sidebar at all. Everything else this PR adds to a shared file is append-only and alphabetically placed.
• docs/docs/Develop/connection-oauth.mdx is extended strictly by appending. The Slack redirect-URL and per-action scope material is a new trailing section, per the cross-ticket convention for this page; no existing text is edited.
• The slack and microsoft rows in extensions-bundle-list.mdx link relatively on purpose. Every other row uses an absolute slug, but /bundles-slack and /bundles-microsoft exist only on the next docs version, so the absolute form fails the build: Docusaurus found broken links! - Broken link on source page path = /next/extensions-bundle-list. Verified by trying it. Normalize it only when 1.13 is cut and the slug exists in a released version.
• Deviations from the matrix's schema.outputs, all deliberate: scalar rows (has_more, next_cursor, canvas_id) are folded into one Data output per component, because Langflow edges are typed and a bare bool/str output cannot be consumed downstream. The reactions.add input the matrix calls name is exposed as emoji_name, because Component.name is the registry-name override and an input called name would be silently shadowed by the class attribute; the Web API parameter is still sent as name.
• The two matrix deviations above are now pinned by src/bundles/slack/tests/test_slack_matrix_schema.py, which compares the shipped components' input and output names against matrices/slack.json with the deviations listed explicitly and asserted exhaustive. check_capability_manifests.py cannot do this itself: the capability manifest carries no schema, only the matrix does.
• src/backend/tests/unit/services/connection/test_oauth_providers.py now pins that the bundle's two auth profiles declare the same authorize and token URLs providers.endpoints hardcodes, so INT-8's picker and the broker cannot drift apart silently.
• _base.py, _chat.py, _client.py sit at the package root, not in components/slack/: lfx extension validate scans the bundle directory and reports a shared abstract Component base there as build-method-missing.
• Sample workspace IDs in fixtures and tests are deliberately non-hex (C0SLACKDEMO, not C0123456789) so detect-secrets does not read them as high-entropy strings. .secrets.baseline needed no new entries.
• Not exercised: no live Slack workspace was available, so tests/test_slack_live.py has never run against real Slack. It is marked api_key_required, self-skips without LANGFLOW_SLACK_LIVE_USER_TOKEN / LANGFLOW_SLACK_LIVE_BOT_TOKEN / LANGFLOW_SLACK_LIVE_CHANNEL, and is deselected in CI. The hosted Langflow-owned Slack apps (confidential + a second PKCE app for Desktop) and the Marketplace listing that lifts the conversations.replies rate tier remain external dependencies.

Follow-ups (not in this PR)

• EE oss-version re-pin once the INT stack merges, which also re-verifies enterprise-hardened.lock.json through scripts/check-oss-compat.sh. EE docs/connectors.md currently over-claims first-party Slack support and should be reconciled with these seven actions at the same time.
• INT-7 consumes the declared policy_keys; INT-7/INT-8 deliver the Desktop hiding of bot actions by filtering on deployment_contexts. This PR only declares them.
• Backend locales/en.json keys for the seven components. DECISIONS.md assigns the fix: include Google as a default partner bundle #14220 locale mirroring to INT-11; see the note above for why hand-writing them here would be undone by gp-backend-check.yml. Until INT-8's baseline lands, the Slack palette strings are English-only, as paddle's and confluent's are.
• An lfx follow-up (not caused by this diff): in a full langflow install, python -c "import lfx_slack" raises ImportError from a partially initialized lfx.custom.custom_component.component, while import lfx_google succeeds. It reproduces with no Slack code at all (import lfx.io, lfx.schema.data; from lfx.custom.custom_component.component import Component) and does not affect the real loader path — load_installed_extensions reports lfx-slack ok, 7 components, 0 errors.

Post-review changes: 354709002e merges INT-11's fix to scripts/gp/extract_backend_strings.py — the extractor now also walks installed extension bundles through lfx.extension.load_installed_extensions() — which closes the "Backend locales/en.json keys for the seven components" follow-up above. locales/en.json conflicted on the merge and was resolved by re-running the generator rather than by hand-merging either side, so the seven Slack components' 101 rows are generated and the auto-bake job will keep them instead of deleting them. Nothing is removed and no value changes relative to the merged-in branch; --check is clean immediately after the run. src/bundles/slack/tests in the clean lfx-only venv is unchanged at 56 passed / 3 deselected.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (1)

• release-.*

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 47ea2282-42e8-4888-8187-cd90c849fed0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

✅ Test Coverage Advisor

No source changes detected without accompanying tests. Thanks for keeping coverage up! 🎉

Advisory check only — never blocks merge.

[github-actions]

Frontend Unit Test Coverage Report

Coverage Summary

Lines	Statements	Branches	Functions
	55.64% (84764/152331)	72.45% (12551/17322)	50.87% (2000/3931)

Unit Test Results

Tests	Skipped	Failures	Errors	Time
6644	0 💤	0 ❌	0 🔥	22m 15s ⏱️

[github-actions]

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.21%. Comparing base (45e4ead) to head (3547090).

Additional details and impacted files

@@                      Coverage Diff                      @@
##           feat/int-11-lfx-microsoft   #14962      +/-   ##
=============================================================
- Coverage                      65.26%   65.21%   -0.05%     
=============================================================
  Files                           2519     2520       +1     
  Lines                         263172   263190      +18     
  Branches                       36824    39272    +2448     
=============================================================
- Hits                          171763   171649     -114     
- Misses                         89189    89321     +132     
  Partials                        2220     2220              

Flag	Coverage Δ
backend	74.17% <ø> (-0.04%)	⬇️
frontend	62.36% <100.00%> (-0.07%)	⬇️
lfx	65.09% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...ckend/base/langflow/services/connection/service.py	58.56% <ø> (ø)
src/frontend/src/utils/styleUtils.ts	95.01% <100.00%> (+<0.01%)	⬆️
src/lfx/src/lfx/integrations/models.py	87.70% <100.00%> (+0.10%)	⬆️

... and 40 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.