Create and operate isolated Smol Cloud machines, run bounded commands, transfer files, and inspect account and usage information.
Create one bounded Smol Cloud machine in the stopped state with explicit resources, a finite auto-stop interval and deletion TTL, and an explicit outbound network policy. Published ports remain authenticated by default. The conservative blocked default denies egress and may prevent uncached image pulls; unrestricted networking and unauthenticated public ingress each require explicit opt-in.
Permanently delete one Smol Cloud machine by its exact machine ID. This irreversible operation removes all machine-local storage, ends its storage billing, and requires explicit confirmation. Export important data before calling this tool. Do not automatically retry after an ambiguous failure.
Download and offload one file from an exact cloud machine. Downloads are limited to 10 MB by Composio policy, and the read resets the machine's auto-stop idle timer.
Run one bounded foreground argv command on an exact hosted Smol Cloud machine. Execution can auto-start billable compute and can modify or delete guest data. Output is text-only, streaming and background execution are disabled, and the action never retries automatically.
Get the connected account's status, plan, effective machine limits, billing-period usage, and spend in integer micros.
Get metered usage for the connected account's provider-defined period, keeping the requested and consumed metric windows distinct.
Get configuration, lifecycle state, and readiness for one cloud machine by its exact machine id, not by name.
Get billing-period usage and cost in integer micros for one exact machine ID. CPU and memory metering can lag by several minutes while a machine is running, so mid-life usage and cost are a lower bound until metering rolls up; stop and delete trigger a final sample. Deleted machine usage remains available for the provider-documented 30-day lookup period.
List cloud machines owned by the connected account, optionally requiring all supplied labels to match.
Start one stopped cloud machine by exact machine ID. A detached start returns before readiness and requires polling GET_MACHINE until ready=true.
Stop compute for one cloud machine by exact id while preserving its filesystem. Stopping does not delete the machine: stored disk can continue billing and the machine can continue occupying a plan slot until deletion.
Upload a file of at most 8,000,000 bytes to a safe relative guest path on one cloud machine identified by its exact machine ID. This can replace existing guest data and resets the machine's auto-stop idle timer.
The Smol Machines integration connects your Dench AI CRM directly to Smol Machines, so agents can read and act on your Smol Machines data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
12 actions are available for agents to invoke on your behalf. Every call runs through Smol Machines's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Smol Machines and click Connect — you'll authorize access through Smol Machines's own sign-in flow. No API keys or code required.
Ask an agent to use Smol Machines in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Smol Machines integration connects your AI CRM to Smol Machines, so AI agents can work with your Smol Machines 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 Smol Machines integration currently exposes 12 actions, including Create Machine, Delete Machine, Download File, Execute Command, Get Account, and Get Account Usage. Agents invoke them on your behalf from chat or from automations.
No. You connect Smol Machines from your Dench workspace using Smol Machines's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Smol Machines's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Smol Machines connection from your workspace settings at any time.