Appearance
Ably
undefined
| Detail | Value |
|---|---|
| Category | Communication |
| Base URL | https://rest.ably.io |
| Authentication | API Key |
| Endpoints | 6 |
| Connector key | ably |
Using Ably in a workflow
- Go to Connections and click New Connection.
- Pick Ably 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 | Publish Message |
GET | Get Message History |
GET | Get Presence |
GET | List Channels |
GET | Request Token |
GET | Get Stats |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Publish Message
| Detail | Value |
|---|---|
| Operation ID | publish_message_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ably connection from the Connection dropdown.
- In the Operation dropdown, select
publish_message_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 Ably API reference.
GET
Get Message History
| Detail | Value |
|---|---|
| Operation ID | get_message_history_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ably connection from the Connection dropdown.
- In the Operation dropdown, select
get_message_history_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 Ably API reference.
GET
Get Presence
| Detail | Value |
|---|---|
| Operation ID | get_presence_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ably connection from the Connection dropdown.
- In the Operation dropdown, select
get_presence_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 Ably API reference.
GET
List Channels
| Detail | Value |
|---|---|
| Operation ID | list_channels_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ably connection from the Connection dropdown.
- In the Operation dropdown, select
list_channels_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 Ably API reference.
GET
Request Token
| Detail | Value |
|---|---|
| Operation ID | request_token_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ably connection from the Connection dropdown.
- In the Operation dropdown, select
request_token_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 Ably API reference.
GET
Get Stats
| Detail | Value |
|---|---|
| Operation ID | get_stats_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ably connection from the Connection dropdown.
- In the Operation dropdown, select
get_stats_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 Ably API reference.