volterra

What this skill does

# Volterra

Volterra provides a distributed

Official docs: https://www.volterra.io/docs/

## Volterra Overview

- **Customer Edge (CE) Site**
  - **Device**
- **RE Site**
- **Name Server**
- **Origin Pool**
- **Origin Server**
- **DNS Domain**
- **App Firewall**
- **TLS Configuration**
- **Service Policy Set**
- **Advertise Policy**
- **Security Policy**
- **Network Policy**
- **HTTP Load Balancer**
- **TCP Load Balancer**
- **UDP Load Balancer**
- **Virtual Host**
- **Route**
- **WAF**
- **API Protection**
- **Data Guard Profile**
- **Service Domain**
- **VoltAD Domain**
- **Global Network**
- **VPC**
- **Azure VNet**
- **AWS VPC**
- **Transit VPC**
- **Inside VIP**
- **Outside VIP**
- **Interface**
- **Static Route**
- **BGP Configuration**
- **VPC Network**
- **Hub**
- **Spoke**
- **Transit Hub**
- **Transit Spoke**
- **Cloud Link**
- **Billing Account**
- **Namespace**
- **User**
- **API Credential**
- **Tenant**
- **Project**
- **Role**
- **Authentication Policy**
- **Authorization Policy**
- **Alert Policy**
- **Log Receiver**
- **Monitoring Metric Policy**
- **Upgrade Policy**
- **Image**
- **Hardware**
- **Location**
- **Resource Group**
- **Object Group**
- **Prefix List**
- **Asn List**
- **Threat List**
- **Virtual Network**
- **Firewall**
- **Subnet**
- **Network Interface**
- **Public IP Address**
- **Route Table**
- **Network Security Group**
- **Disk**
- **Load Balancer**
- **Backend Pool**
- **Health Probe**
- **Load Balancing Rule**
- **Virtual Machine**
- **Virtual Machine Scale Set**
- **Availability Set**
- **Container Registry**
- **Kubernetes Cluster**
- **Node Pool**
- **Application Gateway**
- **SQL Database**
- **SQL Server**
- **Cosmos DB Account**
- **Cosmos DB Database**
- **Cosmos DB Container**
- **Storage Account**
- **Blob Container**
- **Queue**
- **Table**
- **File Share**
- **Virtual WAN**
- **VPN Gateway**
- **VPN Site**
- **VPN Connection**
- **Express Route Circuit**
- **Express Route Connection**
- **Network Watcher**
- **Packet Capture**
- **Flow Log**
- **Traffic Analytics**
- **Security Center**
- **Security Alert**
- **Security Recommendation**
- **Automation Account**
- **Runbook**
- **Logic App**
- **Event Grid Topic**
- **Event Grid Subscription**
- **Key Vault**
- **Secret**
- **Certificate**
- **Policy Definition**
- **Policy Assignment**
- **Resource Policy**
- **Management Group**
- **Subscription**
- **Resource Lock**
- **Cost Management**
- **Budget**
- **Reservation**
- **Advisor Recommendation**
- **Monitor**
- **Activity Log**
- **Diagnostic Setting**
- **Metric Alert**
- **Action Group**
- **Autoscale Setting**
- **Service Health Alert**
- **Log Analytics Workspace**
- **Data Collection Rule**
- **Virtual Machine Extension**
- **Virtual Desktop**
- **Application Group**
- **Workspace**
- **Host Pool**
- **Image Definition**
- **Image Version**
- **Shared Image Gallery**
- **Network Function**
- **Network Function Definition**
- **Network Function Instance**
- **Service Function Chain**
- **Service Function Forwarder**
- **Service Function**
- **Traffic Steering Policy**
- **Traffic Classifier**
- **Traffic Action**
- **Traffic Filter**
- **Traffic Mirroring Session**
- **Traffic Mirroring Target**
- **Traffic Mirroring Filter**
- **Network Tap**
- **Network Tap Rule**
- **Network Packet Broker**
- **Network Packet Broker Rule**
- **Network Packet Broker Filter**
- **Network Packet Broker Target**
- **Network Packet Broker Session**
- **Network Packet Broker Mirroring Session**
- **Network Packet Broker Mirroring Target**
- **Network Packet Broker Mirroring Filter**
- **Network Packet Broker Tap**
- **Network Packet Broker Tap Rule**
- **Network Packet Broker Packet Capture**
- **Network Packet Broker Packet Capture Rule**
- **Network Packet Broker Packet Capture Filter**
- **Network Packet Broker Packet Capture Target**
- **Network Packet Broker Packet Capture Session**
- **Network Packet Broker Packet Capture Mirroring Session**
- **Network Packet Broker Packet Capture Mirroring Target**
- **Network Packet Broker Packet Capture Mirroring Filter**
- **Network Packet Broker Packet Capture Tap**
- **Network Packet Broker Packet Capture Tap Rule**

Use action names and parameters as needed.

## Working with Volterra

This skill uses the Membrane CLI to interact with Volterra. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

### Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

```bash
npm install -g @membranehq/cli@latest
```

### Authentication

```bash
membrane login --tenant --clientName=<agentType>
```

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

```bash
membrane login complete <code>
```

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

### Connecting to Volterra

Use `membrane connection ensure` to find or create a connection by app URL or domain:

```bash
membrane connection ensure "https://www.volterra.io/" --json
```
The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

#### 1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

```bash
npx @membranehq/cli connection get <id> --wait --json
```

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

- **`READY`** — connection is fully set up. Skip to **Step 2**.
- **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
  - `clientAction.type` — the kind of action needed:
    - `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
    - `"provide-input"` — more information is needed (e.g. which app to connect to).
  - `clientAction.description` — human-readable explanation of what's needed.
  - `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
  - `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

  After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

- **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

### Searching for actions

Search using a natural language description of what you want to do:

```bash
membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json
```

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and `outputSchema` (what it returns).

## Popular actions

Use `npx @membranehq/cli@latest action list --intent=QUERY --connectionId=CONNECTION_ID --json` to discover available actions.

### Running actions

```bash
membrane action run <actionId> --connectionId=CONNECTION_ID --json
```

To pass JSON parameters:

```bash
membrane action run <actionId> --connectionId=C