> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack: Get Channel Info

Look up a Slack target by ID and return metadata (name, privacy, member count). Accepts channel IDs (C/G/D) via conversations.info and user IDs (U/W) via users.info. Ideal for: resolving a manually-entered channel ID, validating bot access, dropdown lookups.

![Slack: Get Channel Info logo](https://ai-icon.b3.fun/logo/slack)
Catalog action Integrations slack

Look up a Slack target by ID and return metadata (name, privacy, member count). Accepts channel IDs (C/G/D) via conversations.info and user IDs (U/W) via users.info. Ideal for: resolving a manually-entered channel ID, validating bot access, dropdown lookups.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `slack-get-channel-info` |
| Category | Integrations |
| Connector | `slack` |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `slack`, `integration`, `read`, `chat` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `channel` | `string` | Yes | Channel or user ID to look up. Channel IDs \(C/G/D\) resolve via conversations.info; user IDs \(U/W\) resolve via users.info and return a synthetic channel with is_user: true. |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `success` | `boolean` | Yes | - |
| `data` | `object` | No | - |

## Examples

**Workflow node**

```json
{
  "type": "slack-get-channel-info",
  "payload": {
    "channel": "C0123456789"
  },
  "children": [],
  "connector": {
    "type": "slack",
    "id": "conn_slack"
  }
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/slack-get-channel-info/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "channel": "C0123456789"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.