Add User Device
Register a human user's mobile device token with Cloud 66. This changes the user's UI notification destination. Cloud 66 currently supports iOS devices; Android is documented but not currently available.
Deploy and manage applications, stacks, servers, databases, networking, and users across cloud providers with Cloud 66.
Register a human user's mobile device token with Cloud 66. This changes the user's UI notification destination. Cloud 66 currently supports iOS devices; Android is documented but not currently available.
Cancel an existing Cloud 66 deployment. This irreversibly stops the deployment operation but does not delete its deployment history.
Clear all application caches for a Cloud 66 stack and return the accepted asynchronous job by default. Cache removal cannot be undone.
Finalize a rollout application variant and make it the active production version. This immediately changes which application version serves production traffic and cannot be undone by this action.
Create a scheduled backup task for a Cloud 66 stack. Cloud 66 only acknowledges that the task was queued; this action does not wait for or claim backup completion.
Call Cloud 66's documented cluster-creation route with no parameters. Cloud 66 currently documents this operation as unavailable and returning HTTP 501 Not Implemented; this action reports that condition as an error, not success.
Start an interactive Cloud 66 container session. A successful result confirms only that the asynchronous action was accepted; it does not confirm that the session is ready.
Create a database in a Cloud 66 server group, optionally grant database users access, and by default wait for asynchronous completion.
Create a database user in a Cloud 66 server group. By default, wait for the asynchronous action to finish and return only after Cloud 66 reports successful completion.
Create an elastic address failover group between distinct primary and secondary Cloud 66 stacks.
Add a firewall rule to a Cloud 66 stack using a numeric protocol code and at least one destination field. Returns the accepted asynchronous action; the action ID is not the created firewall-rule ID.
Create a gateway for a Cloud 66 account using bastion-server connection metadata without accepting private-key content. Cloud 66 confirms success without returning the new gateway ID; call CLOUD_66_LIST_GATEWAYS afterward.
Submit a Let's Encrypt SSL-certificate creation request for a Cloud 66 stack. Manual certificate and private-key uploads are excluded. A successful result confirms request acceptance only, not completed certificate provisioning.
Create and build a Docker stack. A non-terminal result confirms acceptance only because Cloud 66 does not return a documented stack UID that can safely route action-status polling.
Permanently delete all tags from one Cloud 66 server or load balancer. This removes the entity's entire tag set, not one selected tag, and cannot be undone; verify the entity type and ID first.
Permanently delete a preview application variant from a Cloud 66 stack. This operation only applies to preview variants and cannot be undone.
Permanently delete a Cloud 66 database and all of its data. This cannot be undone. By default, wait for the asynchronous action to finish and fail unless Cloud 66 confirms successful completion.
Permanently remove a database user from every associated database. This cannot be undone. By default, wait for Cloud 66's asynchronous deletion to finish and fail if the terminal action reports failure.
Permanently delete a Cloud 66 elastic address (failover group). This cannot be undone. The failover group must be detached from all stacks before deletion.
Permanently delete an environment variable from a Cloud 66 stack by its key/name. This irreversible operation cannot recover the deleted value; verify the stack UID and key before calling it.
Permanently delete a gateway from a Cloud 66 account. This irreversible operation cannot be undone; verify both the account ID and gateway ID first.
Permanently delete an SSL certificate from a Cloud 66 stack. Verify the stack and certificate identifiers before this irreversible operation. A successful result confirms request acceptance only, not completed removal.
Disable replication to a Cloud 66 slave database server and return the accepted irreversible asynchronous job by default.
Retrieve detailed information for a specific Cloud 66 account.
Call Cloud 66's unauthenticated basic ping endpoint and return its acknowledgement. A successful response confirms only that this endpoint answered; it does not validate the connected OAuth account or guarantee broader API availability.
Get information about a single Cloud 66 backup.
Get the public download URL for a Cloud 66 backup file.
Get regions and server sizes for one cloud provider available to the connected Cloud 66 account.
Return Cloud 66 cloud-provider reference data needed to select valid cloud, region, and server-size values. Use cloud and filter to limit the response.
Return status, health, capacity, and node details for a Kubernetes cluster.
Get runtime information for a specific container in a Cloud 66 stack.
Get a specific Cloud 66 container session by session ID, or the most recent session for a service. Requires SSH key download permission on the stack.
Verify the Cloud 66 connection and return the authenticated user and current account identity.
Get information about a single deployment in a Cloud 66 stack.
Get one environment variable's name and metadata from a Cloud 66 stack by numeric ID. Current and historical values are never returned.
Get information about a specific firewall rule in a Cloud 66 stack.
Return the Nginx modules supported by Cloud 66 stack configuration.
Gets one page of information about a specific process in a Cloud 66 stack; Cloud 66 normally returns up to 30 items per page.
Get information about a single server in a Cloud 66 stack.
Get information about a single setting for a server in a Cloud 66 stack.
Get one SSL certificate from a Cloud 66 stack by certificate identifier.
Retrieve detailed configuration, deployment status, and health for a Cloud 66 stack.
Return the current state and result of one asynchronous Cloud 66 stack action.
Return the configuration for a named alert on a Cloud 66 stack.
Get a single setting for a Cloud 66 stack by its setting identifier.
Get detailed information about a Cloud 66 user by user ID.
Queue an external backup import for a Cloud 66 stack. Cloud 66 only acknowledges that the import was queued; this action does not wait for or claim import completion.
Lists accounts that the current authenticated user can access. Each call returns one page, normally up to 30 items.
Returns all active, rollout, and preview application variants for a specified Cloud 66 stack.
Get backup files for a Cloud 66 stack backup. Each call returns one page, normally up to 30 items.
Gets backups for a Cloud 66 stack. Each call returns one page, normally up to 30 items.
Get cloud providers available to the connected Cloud 66 account, with their regions and server sizes. Each call returns one page, normally up to 30 items.
Return one documented page of Kubernetes clusters accessible to the user. Each call returns one page, currently up to 100 clusters. This documented route returned an HTML 404 in prior probing, so availability may depend on the account or provider deployment.
Gets containers for a Cloud 66 stack, optionally filtered by server. Each call returns one page, normally up to 30 items.
Gets one page of database-user names and metadata for a Cloud 66 server group. Passwords and password hashes are never requested or returned. Cloud 66 normally returns up to 30 items per page.
Returns one page of databases associated with a Cloud 66 server group; Cloud 66 normally returns up to 30 items per page.
Gets one page of deployments for a Cloud 66 stack; Cloud 66 normally returns up to 30 items per page.
Gets one page of DNS providers configured for SSL certificate management; Cloud 66 normally returns up to 30 items per page.
Return Cloud 66's documented elastic-address failover groups. This documented route returned an HTML 404 in prior probing without a scope or paid-tier signal, so its availability is unresolved.
Get one page of environment-variable names and metadata for a Cloud 66 stack. Current and historical values are never returned. Cloud 66 normally returns up to 30 items per page.
Gets one page of firewall rules for a Cloud 66 stack; Cloud 66 normally returns up to 30 items per page.
Gets one page of gateway metadata for a Cloud 66 account. Private-key content is never returned. Cloud 66 normally returns up to 30 items per page.
Gets one page of image repositories for a Cloud 66 stack; Cloud 66 normally returns up to 30 items per page.
Gets one page of jobs configured on a Cloud 66 stack, including each job's command and run_on server-target context. Cloud 66 normally returns up to 30 items per page.
Return one documented page of Cloud 66 notification records. Each call returns one page, normally up to 30 items. This documented route returned an HTML 404 in prior probing, so availability may depend on the account or provider deployment.
Gets one page of processes for a Cloud 66 stack, optionally filtered by server; Cloud 66 normally returns up to 30 items per page.
Gets one page of server groups for a Cloud 66 stack; Cloud 66 normally returns up to 30 items per page.
Returns one page of settings for a server, including optional IDs, timestamps, and warnings when Cloud 66 provides them; Cloud 66 normally returns up to 30 items per page.
Gets one page of servers for a Cloud 66 stack; Cloud 66 normally returns up to 30 items per page.
Gets one page of services for a Cloud 66 stack; Cloud 66 normally returns up to 30 items per page.
Gets one page of SSL certificate metadata for a Cloud 66 stack. Certificate and private-key material is never returned. Cloud 66 normally returns up to 30 items per page.
Retrieve one page of asynchronous actions performed for a Cloud 66 stack, optionally filtered by caller reference; Cloud 66 normally returns up to 30 items per page.
Returns the alert configurations and notification channels for a specified stack.
Returns one page of settings for a Cloud 66 stack, including their values and read-only status; Cloud 66 normally returns up to 30 items per page.
Retrieves stack objects accessible to the current user. Each call returns one page, currently up to 100 stacks.
Gets one page of tags for a Cloud 66 server or load balancer, identified by entity type and ID. Cloud 66 normally returns up to 30 items per page.
Gets one page of users in the connected Cloud 66 account, including account roles and access-profile details when available. Cloud 66 normally returns up to 30 items per page.
Update a Let's Encrypt SSL certificate using Cloud 66's PATCH method. Manual certificate and private-key uploads are excluded. Cloud 66 does not distinguish PATCH from PUT semantics. Success confirms request acceptance only.
Pause a Cloud 66 service or process workload. Services require service_name, server_uid, or both; processes require process_name, server_uid, or both. By setting all_workloads=true without either selector, the action broadly pauses every workload of the selected type across the stack. Pausing workloads is disruptive; the accepted asynchronous job is returned by default.
Promote a Cloud 66 slave database server to a standalone master and return the accepted irreversible asynchronous job by default.
Update a Let's Encrypt SSL certificate using Cloud 66's PUT method. Manual certificate and private-key uploads are excluded. Cloud 66 does not distinguish PUT from PATCH semantics. Success confirms request acceptance only.
Queue an irreversible reboot of selected Kubernetes cluster servers. A non-terminal result confirms acceptance only because Cloud 66 does not return a documented stack UID that can safely route action-status polling.
Initiate an irreversible reboot of one Cloud 66 server. A successful result confirms acceptance only; this endpoint does not confirm that the server finished rebooting.
Reboot all servers or one server group in a Cloud 66 stack using a parallel or serial strategy, and by default wait for documented asynchronous completion.
Redeploy a Cloud 66 stack. This changes its running deployment and returns the accepted asynchronous action by default because deployments commonly outlast the tool execution window.
Replace all tags on one Cloud 66 server or load balancer with the supplied non-empty tag set.
Restart every component of a Cloud 66 stack and return the accepted asynchronous job by default. The restart is disruptive.
Restart a Cloud 66 container, service, or process workload. Containers require container_id. Services require service_name, server_uid, or both; processes require process_name, server_uid, or both. Set all_workloads=true without either selector to restart every workload of the selected type across the stack. Restarts are disruptive and irreversible once initiated; the accepted asynchronous job is returned by default.
Resume a Cloud 66 service or process workload. Services require service_name, server_uid, or both; processes require process_name, server_uid, or both. By setting all_workloads=true without either selector, the action broadly resumes every workload of the selected type across the stack. Resuming workloads is disruptive; the accepted asynchronous job is returned by default.
Re-synchronize a PostgreSQL or MySQL Cloud 66 slave database server with its master and return the accepted asynchronous job by default. The replica's current data may be replaced.
Trigger the provider-configured scaling operation for a process on a Cloud 66 stack and, by default, poll until Cloud 66 confirms success. This tool cannot set a desired process count; scaling behavior comes from the process's existing Cloud 66 configuration.
Enable or disable maintenance mode for a Cloud 66 stack. By default this returns the accepted asynchronous job because Cloud 66 can take 70-120 seconds to mark it complete.
Stop a container in a Cloud 66 stack. This changes the container's running state and can interrupt workloads.
Apply alert configurations to every stack in a Cloud 66 application group and report successes, non-applicable alerts, and failures.
Change the percentage of production traffic sent to a canary rollout application variant. This action applies only to canary deployments.
Update an elastic address's primary or secondary stack assignment, or switch which stack currently receives traffic. Provide at least one of primary_stack_uid, secondary_stack_uid, or current_stack.
Update a Cloud 66 gateway's bastion-server metadata without accepting or returning private-key content. Provide at least one of name, username, address, ttl, or private_ip.
Update one server setting in a Cloud 66 stack and, by default, poll the asynchronous action until Cloud 66 confirms success.
Update one or more Cloud 66 stack alert configurations. Only specified alerts are changed; other stack alert settings remain unchanged.
Update one Cloud 66 stack setting and, by default, poll the asynchronous action until Cloud 66 confirms success.
Incrementally add or delete tags on one Cloud 66 server or load balancer. Deleting a tag that is not present is ignored; Cloud 66 performs deletions before additions.
Update a Cloud 66 user's access profile. This changes account permissions and stack roles for a human user; verify the target user and intended access before calling. Cloud 66 ignores user fields outside access_profile.
The Cloud 66 integration connects your Dench AI CRM directly to Cloud 66, so agents can read and act on your Cloud 66 data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
102 actions are available for agents to invoke on your behalf. Every call runs through Cloud 66's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Cloud 66 and click Connect — you'll authorize access through Cloud 66's own sign-in flow. No API keys or code required.
Ask an agent to use Cloud 66 in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Cloud 66 integration connects your AI CRM to Cloud 66, so AI agents can work with your Cloud 66 data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Cloud 66 integration currently exposes 102 actions, including Add User Device, Cancel Deployment, Clear Stack Caches, Commit Application Variant, Create Backup Task, and Create Cluster. Agents invoke them on your behalf from chat or from automations.
No. You connect Cloud 66 from your Dench workspace using Cloud 66's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Cloud 66's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Cloud 66 connection from your workspace settings at any time.