Appearance
Stream Chat
undefined
| Detail | Value |
|---|---|
| Category | Communication |
| Base URL | https://chat.stream-io-api.com |
| Authentication | API Key (Query) |
| Endpoints | 6 |
| Connector key | stream-chat |
Using Stream Chat in a workflow
- Go to Connections and click New Connection.
- Pick Stream Chat from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Query Channels |
GET | Send Message |
GET | Query Users |
GET | Update Users |
GET | Send Reaction |
GET | Delete Channel |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Query Channels
| Detail | Value |
|---|---|
| Operation ID | query_channels_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stream Chat connection from the Connection dropdown.
- In the Operation dropdown, select
query_channels_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stream Chat API reference.
GET
Send Message
| Detail | Value |
|---|---|
| Operation ID | send_message_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stream Chat connection from the Connection dropdown.
- In the Operation dropdown, select
send_message_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stream Chat API reference.
GET
Query Users
| Detail | Value |
|---|---|
| Operation ID | query_users_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stream Chat connection from the Connection dropdown.
- In the Operation dropdown, select
query_users_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stream Chat API reference.
GET
Update Users
| Detail | Value |
|---|---|
| Operation ID | update_users_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stream Chat connection from the Connection dropdown.
- In the Operation dropdown, select
update_users_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stream Chat API reference.
GET
Send Reaction
| Detail | Value |
|---|---|
| Operation ID | send_reaction_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stream Chat connection from the Connection dropdown.
- In the Operation dropdown, select
send_reaction_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stream Chat API reference.
GET
Delete Channel
| Detail | Value |
|---|---|
| Operation ID | delete_channel_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stream Chat connection from the Connection dropdown.
- In the Operation dropdown, select
delete_channel_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stream Chat API reference.