- Category: developer tools
- Auth: API_KEY
- Composio-managed OAuth available? N/A
- Tools: 13
- Triggers: 0
- Slug:
RUNPOD - Version: 20261101_00
Tools
Create RunPod Cluster
Create RunPod Cluster
Slug:
RUNPOD_CREATE_CLUSTERTool to create a new GPU cluster for multi-node distributed computing workloads on RunPod. Use when you need to deploy multiple pods with shared configuration for parallel processing, ML training, or HPC workloads.Input Parameters
Optional list of environment variables to set in the container. Each entry should be a dict with ‘key’ and ‘value’ fields.
Type of cluster to create: APPLICATION for general-purpose workloads, TRAINING for ML training jobs, or SLURM for high-performance computing with SLURM scheduler.
Optional Docker image name to use for the pods. If not specified, the template’s default image is used.
Optional maximum deployment cost threshold. If specified, deployment will fail if the estimated cost exceeds this value.
String identifier for the GPU type to use in the cluster (e.g., ‘NVIDIA GeForce RTX 3070’, ‘NVIDIA A100 80GB PCIe’).
Optional template ID to use for pod configuration. References a pre-configured pod template with specific Docker image and settings.
Optional size in GB for the container disk. This is ephemeral storage that is reset when the pod restarts.
Output
Create Secret
Create Secret
Slug:
RUNPOD_CREATE_SECRETTool to create a new secure secret in RunPod for credential management. Use when you need to store sensitive values like API keys, passwords, or tokens that will be accessible in pods and endpoints via environment variables (RUNPOD_SECRET_<name>).Input Parameters
Unique identifier name for the secret. This name will be used to reference the secret in pods and endpoints (accessible via environment variable RUNPOD_SECRET_<name>). Must be unique within your account.
The secret value to store securely. This will be encrypted and stored securely by RunPod.
Optional human-readable description of what this secret is used for. Helps with secret management and documentation.
Output
Delete Container Registry Authentication
Delete Container Registry Authentication
Slug:
RUNPOD_DELETE_REGISTRY_AUTHTool to delete container registry authentication from RunPod. Use when you need to remove stored registry credentials.Input Parameters
The ID of the container registry authentication to delete. This is the unique identifier returned when the registry authentication was created.
Output
Delete Template
Delete Template
Slug:
RUNPOD_DELETE_TEMPLATETool to remove a RunPod template via GraphQL mutation. Use when you need to delete a template that is no longer needed. The template must not be in use by any pods or assigned to any serverless endpoints, otherwise the operation will fail.Input Parameters
The name of the template to delete. The template must not be in use by any pods or assigned to any serverless endpoints.
Output
Get GPU Types
Get GPU Types
Get authenticated user info
Get authenticated user info
Get Pod Details
Get Pod Details
List CPU Types
List CPU Types
Save Serverless Endpoint
Save Serverless Endpoint
Slug:
RUNPOD_SAVE_ENDPOINTTool to create or update a RunPod serverless endpoint with GPU configuration and scaling settings. Use when configuring new GPU-accelerated serverless endpoints or modifying existing endpoint parameters. Include ‘id’ parameter to update an existing endpoint, omit it to create a new one.Input Parameters
Endpoint ID to update an existing endpoint. If provided, the mutation will update the existing endpoint instead of creating a new one. Omit this field to create a new endpoint.
Name of the endpoint (required for creation). Must be a descriptive identifier for the serverless endpoint.
GPU type identifier for the endpoint (required for creation). Examples: ‘NVIDIA RTX A4000’, ‘NVIDIA A40’, ‘NVIDIA RTX A5000’. Specify the exact GPU model string from RunPod’s available GPU types.
Comma-separated list of data center locations where the endpoint should run. Example: ‘US-CA-1,US-OR-1’. If not specified, RunPod will choose automatically.
Type of autoscaling algorithm to use. Options: ‘QUEUE_DELAY’ (scale based on queue wait time), ‘REQUEST_COUNT’ (scale based on number of requests). QUEUE_DELAY is recommended for most use cases.
Template ID for the endpoint configuration (required for creation). This is the ID of a pre-configured template in your RunPod account.
Maximum number of workers (GPU instances) to scale up to. This is the upper limit for autoscaling. Must be >= workers_min.
Minimum number of workers (GPU instances) to keep running. Set to 0 to allow scaling down to zero when idle. Set to 1 or higher to maintain always-on capacity.
Idle timeout in seconds before workers are scaled down. Workers will be terminated after being idle for this duration. Common values: 5, 10, 30, 60.
Target value for the scaler. For QUEUE_DELAY: target delay in seconds before scaling up. For REQUEST_COUNT: target number of requests per worker. Common values: 1-10 for QUEUE_DELAY, 1-100 for REQUEST_COUNT.
Network volume ID to attach to the endpoint for persistent storage. If specified, this network volume will be mounted to all workers.
Output
Save Container Registry Authentication
Save Container Registry Authentication
Slug:
RUNPOD_SAVE_REGISTRY_AUTHTool to save container registry authentication credentials for accessing private Docker images in RunPod. Use when you need to store credentials for a private container registry.Input Parameters
A user-defined name for the container registry authentication credential. This name must be unique across all registry authentications in your account.
Output
Save Template
Save Template
Slug:
RUNPOD_SAVE_TEMPLATECreate or update a Runpod template with container configuration for pods or serverless endpoints; set the volume size to 0 for serverless templates. Updates also send Docker arguments and environment variables, defaulting to an empty string and empty list when omitted.Input Parameters
List of environment variables to set in the container. Each entry must have ‘key’ and ‘value’ fields. Pass empty array if no env vars needed.
Unique name for the template. Must be unique across your account. Used to identify the template for pod or serverless deployment.
Comma-separated list of ports to expose from the container. Format: ‘port/protocol’ or just ‘port’. Example: ‘8080/http,8888/http’
Markdown-formatted readme documentation for the template. Use this to document usage instructions, requirements, and configuration details.
Docker image to use for the template. Can be from Docker Hub or a private registry. Include the full image path with tag.
Additional Docker arguments to pass when starting the container. Use this for advanced Docker configuration. Leave empty if not needed.
ID of an existing template to update. Leave empty to create a new template. Provide the template ID to modify an existing template.
Network volume size in gigabytes for persistent storage. Set to 0 if no persistent volume is needed. For serverless templates, always use 0.
Whether this template is for serverless endpoints (true) or standard pods (false). Serverless templates must have volumeInGb set to 0.
Mount path for the network volume inside the container. Only applicable if volumeInGb > 0. Example: /workspace or /data
Container disk size in gigabytes. This is ephemeral storage that gets reset on pod restart. Minimum 10 GB recommended. Used for temporary files and cache.
Output
Update Registry Auth
Update Registry Auth
Update User Settings
Update User Settings
Slug:
RUNPOD_UPDATE_USER_SETTINGSUpdate the authenticated Runpod user’s SSH public key for pod access.Input Parameters
SSH public key to associate with the user account. This key will be used for SSH access to pods. Must be a valid SSH public key in OpenSSH format (e.g., ‘ssh-rsa AAAAB3…’ or ‘ssh-ed25519 AAAAC3…’).