Slack¶
Establishes a secure connection between Salt and Slack through Carbon’s integrations. This node configures and authorizes the Slack integration, enabling your workspace to ingest and use Slack content (messages, files, threads) in downstream steps.
Usage¶
Use this node when you need to connect a Slack workspace so its content can be indexed and made available for search, retrieval, or analysis within your workflow. Typically placed early in a pipeline before nodes that browse, query, or process connected Carbon data sources.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| authentication | True | Not specified | Initiates and stores the authorization required to access Slack via Carbon. Usually handled through an OAuth-style connect flow. | Connect Slack account |
| workspace_selection | False | Not specified | Option to select or confirm which Slack workspace to connect if multiple are available for the user. | acme-inc.slack.com |
| sync_scope | False | Not specified | Controls which Slack resources to sync (e.g., channels, threads, files). The exact options depend on your Carbon configuration and Slack permissions. | Public channels, selected private channels |
| filters | False | Not specified | Optional filters for limiting synced data by channel, date range, or other attributes. | Channels: #product, #eng; Date range: last 90 days |
| reindexing_behavior | False | Not specified | Settings related to initial sync and periodic re-sync, including whether to perform a full or incremental update. | Incremental sync every 24 hours |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| connection | Not specified | A handle or reference to the established Slack integration in Carbon, used by downstream nodes to query or fetch content. | carbon_connection_reference |
| status | Not specified | High-level status of the connection (e.g., connected, pending authorization, failed). | connected |
Important Notes¶
- This node specifically targets the Slack integration in Carbon; the integration type is fixed to Slack.
- Slack authorization may require workspace admin approval depending on your organization’s policies.
- The amount and type of data available (public channels, private channels, DMs) is governed by granted permissions and Carbon’s configured scopes.
- Initial syncs can take time depending on workspace size and selected scope; downstream nodes may not see data until indexing completes.
- Ensure your environment is configured to reach the Carbon service and that the user has a valid Carbon token.
Troubleshooting¶
- Authorization failed: Re-run the connect flow and ensure you are signed in to the correct Slack workspace with required permissions.
- No data appears after connecting: Verify sync scope and filters, then allow time for initial indexing to complete. Check connection status in your Carbon dashboard.
- Missing private channels or DMs: Confirm the integration was granted the necessary permissions and that access to those resources is allowed by your Slack admins.
- Intermittent errors or rate limits: Reduce sync scope or frequency and try again later; Slack APIs enforce rate limits.
- Downstream nodes report missing source: Ensure this Slack connection output is correctly wired into nodes that read from Carbon data sources.