Pilvio is a cloud service provider offering virtual machines, object storage, and full API support for resource management and automation.
Pilvio is a cloud service provider offering virtual machines, object storage, and full API support for resource management and automation. On Nagent, Pilvio is exposed as a fully-configurable developer tools integration that any agent can call — 10 actions, and API key authentication. No code is required to wire Pilvio into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Pilvio 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 Pilvio 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 Pilvio, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PILVIO_CHECK_ACTIVE_CAMPAIGNSTool to check for active campaigns. Use when you need to verify whether any campaigns are currently active.
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
PILVIO_GET_USER_INFOTool to retrieve information about the authenticated user. Use when you need to fetch the current user's profile after authentication.
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
PILVIO_LIST_BILLING_ACCOUNTSTool to list billing accounts. Use when you need to fetch all billing accounts for management or reporting. Use after authenticating your Pilvio API key.
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
PILVIO_LIST_CREDIT_CARDSTool to list credit cards attached to a billing account. Use after confirming the billing account ID. Example: "Retrieve cards for billing_account_id 'ba_1234567890abcdef'."
Input parameters
Path parameter. The ID of the billing account to list credit cards for.
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
PILVIO_LIST_INVOICESTool to retrieve a list of invoices. Use after authentication to fetch and filter invoices for a billing account.
Input parameters
Number of invoices per page.
Pagination offset (zero-based).
Filter invoices by status.
ISO 8601 timestamp (inclusive) to filter invoices created on or before this date.
ISO 8601 timestamp (inclusive) to filter invoices created on or after this date.
Billing account ID to retrieve invoices for.
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
PILVIO_LIST_LOCATIONSTool to retrieve the list of available data center locations. Use after authentication to see where you can deploy resources.
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
PILVIO_LIST_VM_RESOURCE_POOLSTool to retrieve the list of available VM resource pools. Use after authentication to determine where you can provision VMs.
Input parameters
Page number for pagination (1-based)
Number of items per page
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
PILVIO_LIST_VMSTool to retrieve a list of all virtual machines. Use after authenticating to fetch your VMs.
Input parameters
Sort by field
Maximum results per page
Pagination offset
Filter by project id
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
PILVIO_LIST_VM_SNAPSHOTSTool to list snapshots (replicas) of a specific VM. Use this to get all point-in-time snapshots or backups for a virtual machine.
Input parameters
UUID of the VM to fetch replicas/snapshots for
Type of replica to list: 'snapshot' or 'backup'. Defaults to 'snapshot'
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
PILVIO_UPDATE_USER_PROFILETool to update the authenticated user's profile. Use after obtaining a valid API key when you need to modify profile details (e.g., change email or name).
Input parameters
User's email address
User's username (required for identification)
User's last name
User's first name
User's phone number
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 47 agents privately built on Nagent that already use Pilvio.
Build on Nagent
Connect Pilvio 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 Pilvio, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Pilvio is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Pilvio is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Pilvio 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 Pilvio event fires, the agent kicks off automatically.
Every Pilvio 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 Pilvio ships with 10 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Pilvio together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Pilvio-based workflows tailored to your business.