Create a VPS and roll a stack with Terraform — not tokens in the chat.
A Terraform connection points at modules you have approved. Automated processes can validate, plan, apply and show the result. Destroy stays off unless the connection allows it and a person has approved. Typical work: a Proxmox VM, deploying or upgrading a stack, preparing an environment. Provider credentials — including Proxmox API tokens — stay in the organization vault. The run can be local or over an existing SSH connection.
What Terraform does here
Terraform connector. It appears when deployed and the account has it.
Connections in admin
Register the connection, working directory and Terraform or OpenTofu binary. Secrets are not stored in the process diagram.
Proxmox VMs
Proxmox is a full provider path: API tokens and passwords go to secure credential store, never into Terraform vars or the request. An automated process can create or change a VM from an approved module.
Validate, plan, apply
Capabilities cover validate, plan, apply and show. Destroy is a separate, opt-in operation on that connection.
Allowlisted modules
Only listed modules and variable keys may run. Names that look like sensitive credentials are rejected — put those in the vault.
Local or over SSH
Terraform can run on the platform host or through an SSH connection to the machine that has the CLI and modules.
From a automated process step
On the canvas you pick the Terraform connection, module and operation. Organization rules and access still apply before it runs.
Explore more
WinRM / PSRP
WinRM and PowerShell Remoting (PSRP) are one Windows connection family. You store the host and choose WinRM or PSRP, keep passwords and certificates in the vault, then test the path or run approved Windows Ansible books. Same idea as SSH: a governed connection, not a shell in the request.
Ansible
Ansible connections bind inventory and playbooks into governed automated process steps. A run uses an approved playbook, sensitive credential-referenced credentials and organization policy. Chat does not get a free ansible-playbook shell.
SSH
SSH connections store host, port, user and keys in the vault. Automated processes run approved command profiles. A free-form remote command from the model is off; a named profile is used instead.
VPN
VPN connections (IPsec / IKEv2, SSTP or WireGuard, client or server role) sit in the same governed catalog as SSH and Ansible. From a server connection in admin you generate secrets once, then download ready profiles and install commands grouped by iPhone, Android, Windows and Ubuntu. Typical path: gateway first, then SSH, playbooks or Windows remoting on the far side.
Automated processes
An automated process is more than a diagram on a canvas. It defines what happens, in what order, under which conditions and when a person needs to step in. You can combine information retrieval, decisions, business-system actions, approval and delivery of the result into one repeatable process. Once designed, the AI can run that process consistently.
Connectors
The platform composes tools, capabilities and connections: MCP, REST, SQL, GitHub, SSH, Ansible, Terraform, WinRM/PSRP and other deployed connections. Calls go through organization policy and sensitive credential references.
Ready to move beyond the chatbot?
Build AI that understands your business, works with your knowledge, follows your processes and can actually finish the job. You decide which actions are allowed, when a person must step in and how much AI usage your organization can consume.