Docker Hub is a service provided by Docker for finding and sharing container images with your team.
Docker Hub is a service provided by Docker for finding and sharing container images with your team. On Nagent, Docker Hub is exposed as a fully-configurable developer tools integration that any agent can call — 24 actions, and API key authentication. No code is required to wire Docker Hub into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Docker Hub to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Docker Hub into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Docker Hub, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DOCKER_HUB_ADD_ORG_MEMBERInvite a user to join a Docker Hub organization. Sends an invitation email to the specified user (by Docker ID or email). The user must accept the invitation to become a member. Requires owner or admin privileges on the target organization.
Input parameters
Name of the Docker Hub organization to invite a user to. Must be an organization you have owner/admin access to.
Role to assign to the invited member. Valid values: 'member' (read access), 'editor' (read/write access), 'owner' (full admin access).
Optional team name within the organization to add the member to.
Docker ID (username) or email address of the user to invite to the organization.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_CREATE_ORGANIZATIONCreate a new Docker Hub organization. Note: This endpoint requires JWT authentication obtained via /v2/users/login and may have restricted access.
Input parameters
Company name associated with the organization
Unique slug for the organization. Must be lowercase letters, numbers, '.', '_' or '-' only; at least 2 characters long.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_CREATE_REPOSITORYCreates a new Docker Hub repository under the specified namespace. Use this to programmatically create public or private repositories for storing Docker images. Requires proper authentication with write permissions to the namespace.
Input parameters
The repository name (must be lowercase; can contain letters, numbers, '.', '_', or '-')
The Docker Hub username or organization name under which to create the repository Must match the authenticated Docker Hub account identity; mismatches cause authorization failures.
If true, creates a private repository (requires paid plan). Defaults to false (public).
Short description of the repository (max 100 characters)
Full description or README content for the repository (supports Markdown)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_CREATE_WEBHOOKCreate a webhook on a Docker Hub repository to receive notifications on image push events. This is a two-step process: 1. Create the webhook with a name 2. Add a hook URL to the webhook Requires admin permissions on the repository.
Input parameters
The URL that will receive HTTP POST requests when the webhook is triggered (must be publicly accessible) Must use HTTPS. Failed deliveries are silent — no error is returned if the endpoint is unreachable.
The Docker Hub namespace (your username or organization name) where the repository exists Must be lowercase letters, numbers, and hyphens only.
The name of the repository to add the webhook to. Must be a repository you have admin access to Must be lowercase letters, numbers, and hyphens only.
A descriptive name for the webhook (e.g., 'CI trigger', 'deploy-notification')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_DELETE_IMAGEDelete one or more images from your Docker Hub namespace using the bulk delete API. IMPORTANT REQUIREMENTS: - You must own the namespace (your username or an organization you admin) - You cannot delete images from 'library' (official Docker images) - Images are identified by SHA256 digest (get from LIST_IMAGES action) USAGE: 1. First use LIST_IMAGES to get image digests for your repository 2. Then call this action with the namespace, repository, and digest(s) Example: DELETE_IMAGE( namespace="myusername", manifests=\[{"repository": "myapp", "digest": "sha256:abc123..."}\] ). WARNING: Deletion is permanent and irreversible — obtain explicit user confirmation before calling this action.
Input parameters
If true, validates the request without actually deleting images. Useful for testing what would be deleted
List of image manifests to delete. Each manifest specifies a repository name and SHA256 digest. Maximum 100 manifests per request
Your Docker Hub username or organization name. Must be a namespace you have write access to. Note: You cannot delete images from 'library' (official images)
List of warning types to ignore. Options: 'is_active' (ignore active image warnings), 'current_tag' (ignore current tag warnings)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_DELETE_ORGANIZATIONPermanently deletes a Docker Hub organization. Requires owner permissions on the organization. This action is idempotent - deleting a non-existent organization returns success (404 treated as success). WARNING: Deletion is irreversible and removes all associated repositories, teams, and members.
Input parameters
The unique slug/name of the organization to delete. Must be an organization you have owner permissions on. Supports lowercase letters, numbers, underscores, hyphens, and dots.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_DELETE_REPOSITORYPermanently deletes a Docker Hub repository and all its images/tags. WARNING: This action is irreversible. All images, tags, and metadata will be permanently removed. This operation is idempotent - deleting a non-existent repository returns success. You must have admin/owner permissions on the repository to delete it.
Input parameters
The Docker Hub namespace (username or organization name) that owns the repository to delete
The name of the repository to delete. Must be the repository name without the namespace prefix
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_DELETE_TAGPermanently delete a specific tag from a Docker Hub repository. Requirements: - Must have write/admin access to the repository - The namespace must be your username or an organization you belong to - This action is irreversible - the tag will be permanently removed Note: Cannot delete tags from official Docker Hub images (library namespace).
Input parameters
Tag name to delete from the repository
Docker Hub namespace (your username or organization name). Must have write access to the repository.
Name of the repository containing the tag to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_DELETE_TEAMPermanently deletes a team from a Docker Hub organization. This operation is idempotent - deleting a non-existent team will succeed silently. Requires organization admin permissions. Use DOCKER_HUB_LIST_TEAMS to find available teams before deletion.
Input parameters
Slug/identifier of the Docker Hub organization owning the team (e.g., 'my-org')
Slug/identifier of the team to delete (e.g., 'dev-team')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_DELETE_WEBHOOKDeletes a specific webhook from a Docker Hub repository. Use this tool to remove webhook configurations from repositories you own or have admin access to. This is useful for cleaning up outdated, misconfigured, or no longer needed webhooks. Prerequisites: - You must have admin access to the repository - The repository and webhook must exist - Use the list webhooks action first to get the webhook ID Returns a success message if the webhook was deleted, or an error if the webhook doesn't exist or you lack permission to delete it.
Input parameters
The Docker Hub namespace (username or organization name) that owns the repository. Must be a namespace you have admin access to.
The name of the repository containing the webhook to delete. The repository must exist under the specified namespace.
The unique numeric identifier of the webhook to delete. You can obtain webhook IDs by using the list webhooks action first.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_GET_IMAGERetrieve details about a specific platform-specific image variant by its digest. This tool searches through repository tags to find and return metadata for an image matching the specified SHA256 digest. Returns architecture, OS, size, status, and timestamps. Use LIST_IMAGES first to discover available digests, then use this tool to get details about a specific image variant. Example: GET_IMAGE(namespace="library", repository="ubuntu", digest="sha256:a4453623f2f8319cfff65c43da9be80fe83b1a7ce689579b475867d69495b782")
Input parameters
Content digest (SHA256) of the image to retrieve. Must start with 'sha256:' followed by 64 hexadecimal characters. Use LIST_IMAGES to discover available digests for a repository. Distinct from the numeric image_id used by DOCKER_HUB_DELETE_IMAGE — these formats are not interchangeable.
User or organization namespace that owns the repository. Use 'library' for official Docker images (e.g., ubuntu, alpine, nginx)
Name of the repository within the namespace
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_GET_REPOSITORYRetrieves detailed information about a specific Docker Hub repository. Use this to get repository metadata including description, star/pull counts, permissions, and configuration. Works with both public and private repositories (authentication required for private repos).
Input parameters
The user or organization namespace that owns the repository (e.g., 'library' for official images, or a username/org name)
The name of the repository to retrieve (e.g., 'ubuntu', 'nginx', 'alpine')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_GET_TAGTool to retrieve details of a specific Docker Hub repository tag. Use after confirming the namespace, repository, and tag name.
Input parameters
Specific tag name to retrieve details for
User or organization namespace that owns the repository. Use 'library' for official Docker images.
Name of the repository within the namespace
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_GET_TEAMRetrieve details of a specific team (group) within a Docker Hub organization. Returns the team's ID, name, and description. Requires organization membership with appropriate permissions to view team details.
Input parameters
The slug/name of the organization that owns the team (e.g., 'my-organization')
The slug/name of the team (group) to retrieve (e.g., 'developers')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_GET_WEBHOOKRetrieves details of a specific Docker Hub webhook by its ID. Use this tool when you need to inspect an existing webhook's configuration, including its target URL, configured events, and active status. You must have admin or write access to the repository to retrieve webhook details. Prerequisites: - You must have admin or write access to the repository - The webhook ID must exist (can be obtained from the list webhooks action) Returns the webhook's ID, name, target URL, events, active status, and timestamps.
Input parameters
The Docker Hub namespace (username or organization name) that owns the repository. Must be a namespace you have admin/write access to.
The name of the repository containing the webhook. The repository must exist under the specified namespace.
The unique numeric ID of the webhook to retrieve. Can be obtained from the list webhooks action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_LIST_ORG_ACCESS_TOKENSTool to list all organization access tokens for a Docker Hub organization. Use when you need to view or audit access tokens associated with an organization. Requires appropriate organization permissions to view tokens.
Input parameters
The name of the organization whose access tokens are to be listed. You must have appropriate permissions to view tokens for this organization.
Page number for paginated results (1-indexed, must be >= 1)
Number of results per page (1-100, default 10)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_LIST_ORGANIZATIONSList Docker Hub organizations that the authenticated user belongs to. Returns a paginated list of organizations with details like name, company, and badge status; some metadata fields may be absent — use org name for follow-up detail calls when complete metadata is required. An empty result is valid and indicates the user belongs to no organizations. Use this to discover which organizations a user has access to before performing org-specific operations.
Input parameters
Page number for pagination (1-indexed)
Number of results per page (1-100)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_LIST_ORG_MEMBERSLists members of a Docker Hub organization with their roles and details. Use this tool to: - Audit organization membership - View member roles (owner, member) - Check team assignments for members - Export organization member lists Requirements: - You must have access to the organization (owner or member role) - Authentication via Personal Access Token (PAT) which is exchanged for JWT Note: This endpoint requires organization-level access and proper authentication.
Input parameters
Name of the Docker Hub organization to list members from. Must be an organization you have access to (owner or member role).
Page number for pagination (1-indexed). Use with page_size to navigate large member lists.
Number of members to return per page (1-100). Default is 25.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_LIST_REPOSITORIESTool to list repositories under a namespace. Use when you need to enumerate repositories within a specific Docker Hub namespace, with optional filtering and pagination.
Input parameters
Page number (1-indexed, must be >= 1)
Sort key for ordering results. Valid values: 'name', 'last_updated', 'pull_count'. Prefix with '-' for descending order (e.g., '-last_updated' for newest first).
The user or organization namespace to list repositories from
Number of results per page (1-100, default 25)
Comma-separated list of media types to filter repositories
Comma-separated list of content types to filter repositories that contain at least one artifact of those types
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_LIST_TEAM_MEMBERSList members of a Docker Hub team (group) within an organization. Returns a paginated list of team members with their user details. Requires organization membership with appropriate permissions to view team members.
Input parameters
Page number for paginated results (starts at 1)
Filter members by username, full name, or email (optional)
Name of the Docker Hub organization (e.g., 'my-organization')
Number of results per page (1-100, default 25)
Name of the team (group) within the organization (e.g., 'developers')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_LIST_TEAMSList all teams (groups) within a Docker Hub organization. Requires organization membership with appropriate permissions. Teams in Docker Hub are called 'groups' in the API.
Input parameters
Page number for paginated results (1-indexed)
Number of results per page (1-100)
The slug/name of the organization whose teams are to be listed. You must be a member of this organization.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_LIST_WEBHOOKSLists all webhooks configured for a Docker Hub repository. Use this tool to retrieve webhook configurations for repositories you own or have admin access to. Webhooks are triggered when specific events occur in the repository (e.g., image push). Prerequisites: - You must have admin or write access to the repository - The repository must exist under the specified namespace Returns a paginated list of webhooks with their IDs, names, target URLs, configured events, and status.
Input parameters
Page number for paginated results. Starts at 1. If not specified, returns the first page.
The Docker Hub namespace (username or organization name) that owns the repository. Must be a namespace you have admin/write access to.
Number of webhooks to return per page. Defaults to the API's default page size if not specified.
The name of the repository to list webhooks for. The repository must exist under the specified namespace.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_REMOVE_ORG_MEMBERRemove a member from a Docker Hub organization. This action revokes the user's access to the organization and all its repositories. Requires organization admin privileges. The operation is idempotent - removing a non-member will not cause an error.
Input parameters
The unique name (namespace) of the Docker Hub organization from which to remove the member. Must be an organization you have admin access to.
The Docker Hub username of the member to remove from the organization. This user must currently be a member of the specified organization.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
DOCKER_HUB_REMOVE_TEAM_MEMBERRemove a user from a Docker Hub organization team (group). Use this action to revoke a user's membership from a specific team. The operation is idempotent - removing a user who is not a member will succeed silently.
Input parameters
Name of the Docker Hub organization that owns the team
Docker Hub username of the member to remove from the team
Slug (URL-friendly name) of the team/group within the organization. This is typically the lowercase team name with spaces replaced by hyphens.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 94 agents privately built on Nagent that already use Docker Hub.
Build on Nagent
Connect Docker Hub to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Docker Hub, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Docker Hub is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Docker Hub is connected, you configure its 24 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Docker Hub steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Docker Hub event fires, the agent kicks off automatically.
Every Docker Hub action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Docker Hub ships with 24 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Docker Hub together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Docker Hub-based workflows tailored to your business.