Appearance
Steam
undefined
| Detail | Value |
|---|---|
| Category | Gaming |
| Base URL | https://api.steampowered.com |
| Authentication | API Key (Query) |
| Endpoints | 6 |
| Connector key | steam |
Using Steam in a workflow
- Go to Connections and click New Connection.
- Pick Steam 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 | Player Summaries |
GET | Friend List |
GET | Owned Games |
GET | Achievements |
GET | App List |
GET | News |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Player Summaries
| Detail | Value |
|---|---|
| Operation ID | player_summaries_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Steam connection from the Connection dropdown.
- In the Operation dropdown, select
player_summaries_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 Steam API reference.
GET
Friend List
| Detail | Value |
|---|---|
| Operation ID | friend_list_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Steam connection from the Connection dropdown.
- In the Operation dropdown, select
friend_list_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 Steam API reference.
GET
Owned Games
| Detail | Value |
|---|---|
| Operation ID | owned_games_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Steam connection from the Connection dropdown.
- In the Operation dropdown, select
owned_games_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 Steam API reference.
GET
Achievements
| Detail | Value |
|---|---|
| Operation ID | achievements_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Steam connection from the Connection dropdown.
- In the Operation dropdown, select
achievements_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 Steam API reference.
GET
App List
| Detail | Value |
|---|---|
| Operation ID | app_list_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Steam connection from the Connection dropdown.
- In the Operation dropdown, select
app_list_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 Steam API reference.
GET
News
| Detail | Value |
|---|---|
| Operation ID | news_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Steam connection from the Connection dropdown.
- In the Operation dropdown, select
news_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 Steam API reference.