Skip to main content
Use the @bijection/connectors/slack entrypoint to declare Slack resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

workspace

observations: Evidence-checked workspace

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: standard

Case: slack/workspace/observations/standard. Connection and resource configuration are declared by this exact case. Credential kind: slack. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: channels
Collection: messages
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Workspace-scoped channel and message observations. Signed events request refreshes. History is bounded and does not establish complete deletion coverage. Compiled declaration examples and configuration details are published in the connector reference. Configure the typed setup fields with bind and keep credentials in native credential custody. Use slack.credential("inventory-name") for a private credential reference. Compiled declaration examples and configuration details are published in the connector reference. This is a bundle of independently scheduled tables. Use defineSyncedTable({ source: workspace.tables.channels }) and the same constructor for messages. It promises no joint publication across those tables. Text commands accept { text: string } and require an application governing rule. They use single-attempt delivery: a successful send is attributable to its own retained response; a lost response remains unknown. The separately named audit stamp writes only the operation identity and can reconcile by exact equality, including duplicate detection. Neither command promises provider idempotency or request expiry. Package replay is not live qualification. See the generated catalog for exact declared scenarios and evidence status.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.