Slack¶
Provides a Carbon data connector for Slack. It identifies Slack as the target integration and delegates all configuration, authentication, and synchronization behavior to the shared Carbon data-connector base. Use it to bring messages and files from eligible Slack workspaces/channels into Salt’s Carbon data pipeline.
Usage¶
Use this node when you need to ingest or synchronize Slack content into your Carbon-managed datasets. Place it wherever your workflow selects/configures a data source before a sync, crawl, or indexing step that consumes a Carbon connector. This node is typically paired with subsequent Carbon operations (e.g., start sync, check status, index content) to complete the end-to-end ingestion flow.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| Not specified | False | Not specified | All input handling is provided by the shared Carbon connector base. This node’s only specialization is selecting Slack as the integration type. | Not specified |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| Not specified | Not specified | Outputs whatever the shared Carbon connector base provides for data connectors (e.g., a configured connector object or parameters for downstream Carbon nodes). | Not specified |
Important Notes¶
- This node selects Slack as the Carbon integration. All behavior (inputs, outputs, validation, and execution) is defined by the shared Carbon data connector base.
- Ensure your Slack workspace and channels are accessible and that the required permissions are granted in Slack before attempting a sync.
- You may need to complete an OAuth or token-based authorization flow outside this node, depending on your organization’s configuration.
Troubleshooting¶
- Authentication fails: Verify that your Slack app is installed in the target workspace and that the required scopes/permissions are granted. Reauthorize if needed.
- No data appears after running: Confirm channel access permissions, message retention policies, and that the configured workspace/channel IDs are correct.
- Permission errors: Check Slack admin policies and ensure the account or app used for authorization can read the intended channels and files.