Appearance
Docker Hub
Manage container repositories, images, and tags on Docker Hub.
| Detail | Value |
|---|---|
| Category | DevOps |
| Base URL | https://hub.docker.com/v2 |
| Authentication | Bearer Token |
| Endpoints | 8 |
| Connector key | docker-hub |
Using Docker Hub in a workflow
- Go to Connections and click New Connection.
- Pick Docker Hub 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 /repositories/{namespace} | List repositories |
GET /repositories/{namespace}/{repository} | Get repository details |
PATCH /repositories/{namespace}/{repository} | Update repository |
DELETE /repositories/{namespace}/{repository} | Delete repository |
GET /repositories/{namespace}/{repository}/tags | List image tags |
DELETE /repositories/{namespace}/{repository}/tags/{tag} | Delete a tag |
GET /repositories/{namespace}/{repository}/images | List images |
GET /orgs/{orgname} | Get organization details |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /repositories/{namespace}
List repositories
| Detail | Value |
|---|---|
| Operation ID | devops.listRepositories |
| Method | GET |
| Path | /repositories/{namespace} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Docker Hub connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listRepositories. - 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 Docker Hub API reference.
GET /repositories/{namespace}/{repository}
Get repository details
| Detail | Value |
|---|---|
| Operation ID | devops.getRepository |
| Method | GET |
| Path | /repositories/{namespace}/{repository} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Docker Hub connection from the Connection dropdown.
- In the Operation dropdown, select
devops.getRepository. - 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 Docker Hub API reference.
PATCH /repositories/{namespace}/{repository}
Update repository
| Detail | Value |
|---|---|
| Operation ID | devops.updateRepository |
| Method | PATCH |
| Path | /repositories/{namespace}/{repository} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Docker Hub connection from the Connection dropdown.
- In the Operation dropdown, select
devops.updateRepository. - 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 Docker Hub API reference.
DELETE /repositories/{namespace}/{repository}
Delete repository
| Detail | Value |
|---|---|
| Operation ID | devops.deleteRepository |
| Method | DELETE |
| Path | /repositories/{namespace}/{repository} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Docker Hub connection from the Connection dropdown.
- In the Operation dropdown, select
devops.deleteRepository. - 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 Docker Hub API reference.
GET /repositories/{namespace}/{repository}/tags
List image tags
| Detail | Value |
|---|---|
| Operation ID | devops.listTags |
| Method | GET |
| Path | /repositories/{namespace}/{repository}/tags |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Docker Hub connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listTags. - 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 Docker Hub API reference.
DELETE /repositories/{namespace}/{repository}/tags/{tag}
Delete a tag
| Detail | Value |
|---|---|
| Operation ID | devops.deleteTag |
| Method | DELETE |
| Path | /repositories/{namespace}/{repository}/tags/{tag} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Docker Hub connection from the Connection dropdown.
- In the Operation dropdown, select
devops.deleteTag. - 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 Docker Hub API reference.
GET /repositories/{namespace}/{repository}/images
List images
| Detail | Value |
|---|---|
| Operation ID | devops.listImages |
| Method | GET |
| Path | /repositories/{namespace}/{repository}/images |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Docker Hub connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listImages. - 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 Docker Hub API reference.
GET /orgs/{orgname}
Get organization details
| Detail | Value |
|---|---|
| Operation ID | devops.getOrganization |
| Method | GET |
| Path | /orgs/{orgname} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Docker Hub connection from the Connection dropdown.
- In the Operation dropdown, select
devops.getOrganization. - 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 Docker Hub API reference.