> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Linode (Akamai Cloud)

The Linode (Akamai Cloud) connector lets your AI agent act in each user's Linode (Akamai Cloud) account. Each user connects their own Linode (Akamai Cloud) access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 60 tools.

**Authentication:** Bearer Token
**Categories:** Developer Tools
**Tools:** 60: 33 read, 20 write, 7 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=LINODE)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Linode (Akamai Cloud) connection

   In **AgentKit > Connections**, create a Linode (Akamai Cloud) connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'linode'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Linode (Akamai Cloud):', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'linode_account_get',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "linode"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Linode (Akamai Cloud):", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="linode_account_get",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Linode (Akamai Cloud) credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'linode_account_get',
  toolInput: {},
  connector: 'linode',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="linode_account_get",
    tool_input={},
    connection_name="linode",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `linode_account_get`

Get Account · Read-only

Get the account contact details, balance and active services.
Returns an object with active_promotions, active_since, address_1, address_2, balance, balance_uninvoiced, billing_source, capabilities, city, company, and more.
Use linode_account_get for billing and contact info. Use linode_profile_get for the token user.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `linode_domain_get`

Get Domain · Read-only

Get one DNS domain with its SOA email, type and status.
Returns an object with axfr_ips, description, domain, expire_sec, group, id, master_ips, refresh_sec, retry_sec, soa_email, and more.
Use linode_domain_get for one domain. Use linode_domain_records_list for its records.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain_id` (`integer`, required): Domain ID, from linode_domains_list. Example: 1234

Example input: `{"domain_id":1234}`

### `linode_domain_records_list`

List DNS Records · Read-only

List the DNS records of a domain.
Returns data[] (each with created, id, name, port, priority, protocol, service, tag) plus page, pages, results.
Use linode_domain_records_list to find a record ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain_id` (`integer`, required): Domain ID, from linode_domains_list. Example: 1234
- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{"domain_id":1234}`

### `linode_domains_list`

List Domains · Read-only

List the domains in the Linode DNS Manager.
Returns data[] (each with axfr_ips, description, domain, expire_sec, group, id, master_ips, refresh_sec) plus page, pages, results.
Use linode_domains_list to find a domain ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{}`

### `linode_event_get`

Get Event · Read-only

Get one event with its action, status, progress and entity.
Returns an object with action, created, details, duration, entity, id, message, percent_complete, rate, secondary_entity, and more.
Use linode_event_get to poll the progress of an operation.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `event_id` (`integer`, required): Event ID. Example: 123

Example input: `{"event_id":123}`

### `linode_events_list`

List Events · Read-only

List account events (actions such as Linode boots, creates and deletes), newest first.
Returns data[] (each with action, created, details, duration, entity, id, message, percent_complete) plus page, pages, results.
Use linode_events_list to follow async operations. Use linode_event_get for one event.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{}`

### `linode_firewall_devices_list`

List Firewall Devices · Read-only

List the Linodes and NodeBalancers a firewall is assigned to.
Returns data[] (each with created, entity, id, updated) plus page, pages, results.
Use linode_firewall_devices_list to see what a firewall protects.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `firewall_id` (`integer`, required): Firewall ID, from linode_firewalls_list. Example: 1234
- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{"firewall_id":1234}`

### `linode_firewall_get`

Get Firewall · Read-only

Get one Cloud Firewall with its rules and status.
Returns an object with created, entities, id, label, rules, status, tags, updated.
Use linode_firewall_get for one firewall.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `firewall_id` (`integer`, required): Firewall ID, from linode_firewalls_list. Example: 1234

Example input: `{"firewall_id":1234}`

### `linode_firewalls_list`

List Firewalls · Read-only

List Cloud Firewalls.
Returns data[] (each with created, entities, id, label, rules, status, tags, updated) plus page, pages, results.
Use linode_firewalls_list to find a firewall ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{}`

### `linode_image_get`

Get Image · Read-only

Get one image.
Returns an object with capabilities, created, created_by, deprecated, description, eol, expiry, id, image_sharing, is_public, and more.
Use linode_image_get for one image.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `image_id` (`string`, required): Image ID. Example: linode/ubuntu24.04

Example input: `{"image_id":"<image_id>"}`

### `linode_images_list`

List Images · Read-only

List public distribution images and your private images.
Returns data[] (each with capabilities, created, created_by, deprecated, description, eol, expiry, id) plus page, pages, results.
Use linode_images_list to pick an image ID for linode_instance_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{}`

### `linode_instance_backups_list`

List Linode Backups · Read-only

List the automatic backups and snapshot of a Linode.
Returns an object with automatic, snapshot.
Use linode_instance_backups_list to find a backup to restore.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456

Example input: `{"linode_id":123456}`

### `linode_instance_configs_list`

List Linode Configs · Read-only

List the configuration profiles (kernel, devices, interfaces) of a Linode.
Returns data[] (each with comments, devices, helpers, id, interfaces, kernel, label, memory_limit) plus page, pages, results.
Use linode_instance_configs_list to inspect boot settings.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456
- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{"linode_id":123456}`

### `linode_instance_disks_list`

List Linode Disks · Read-only

List the disks of a Linode.
Returns data[] (each with created, disk_encryption, filesystem, id, label, size, status, updated) plus page, pages, results.
Use linode_instance_disks_list to find a disk ID for linode_image_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456
- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{"linode_id":123456}`

### `linode_instance_firewalls_list`

List Linode Firewalls · Read-only

List the Cloud Firewalls assigned to a Linode.
Returns data[] (each with created, entities, id, label, rules, status, tags, updated) plus page, pages, results.
Use linode_instance_firewalls_list for one Linode. Use linode_firewalls_list for all firewalls.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456
- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{"linode_id":123456}`

### `linode_instance_get`

Get Linode · Read-only

Get one Linode instance with its status, specs, IPs and backups setting.
Returns an object with alerts, backups, capabilities, created, disk_encryption, group, has_user_data, host_uuid, hypervisor, id, and more.
Use linode_instance_get for one Linode.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456

Example input: `{"linode_id":123456}`

### `linode_instance_ips_get`

Get Linode IPs · Read-only

Get the IPv4 and IPv6 addresses of a Linode.
Returns an object with ipv4, ipv6.
Use linode_instance_ips_get to find a server address.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456

Example input: `{"linode_id":123456}`

### `linode_instance_stats_get`

Get Linode Stats · Read-only

Get CPU, disk IO and network usage of a Linode for the last 24 hours.
Returns an object with cpu, io, netv4, netv6, title.
Use linode_instance_stats_get to check load. Use linode_instance_transfer_get for monthly transfer.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456

Example input: `{"linode_id":123456}`

### `linode_instance_transfer_get`

Get Linode Transfer · Read-only

Get the network transfer a Linode used this month against its quota.
Returns an object with billable, quota, used.
Use linode_instance_transfer_get to watch transfer usage.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456

Example input: `{"linode_id":123456}`

### `linode_instance_volumes_list`

List Linode Volumes · Read-only

List the Block Storage volumes attached to a Linode.
Returns data[] (each with created, encryption, filesystem_path, hardware_type, id, io_ready, label, linode_id) plus page, pages, results.
Use linode_instance_volumes_list for one Linode. Use linode_volumes_list for all volumes.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456
- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{"linode_id":123456}`

### `linode_instances_list`

List Linodes · Read-only

List the Linode instances you can access, with status, type, region and IPs.
Returns data[] (each with alerts, backups, capabilities, created, disk_encryption, group, has_user_data, host_uuid) plus page, pages, results.
Use linode_instances_list to find a Linode ID. Use linode_instance_get for one Linode.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{}`

### `linode_invoices_list`

List Invoices · Read-only

List the account invoices.
Returns data[] (each with billing_source, date, id, label, subtotal, tax, tax_summary, total) plus page, pages, results.
Use linode_invoices_list to review billing.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{}`

### `linode_lke_cluster_get`

Get Kubernetes Cluster · Read-only

Get one LKE cluster with its version, region and status.
Returns an object with apl_enabled, control_plane, created, id, k8s_version, label, region, stack_type, subnet_id, tags, and more.
Use linode_lke_cluster_get for one cluster.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cluster_id` (`integer`, required): Cluster ID. Example: 12345

Example input: `{"cluster_id":12345}`

### `linode_lke_cluster_pools_list`

List Kubernetes Node Pools · Read-only

List the node pools of an LKE cluster with their node counts and types.
Returns data[] (each with autoscaler, count, disk_encryption, disks, id, k8s_version, label, labels) plus page, pages, results.
Use linode_lke_cluster_pools_list to check cluster capacity.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cluster_id` (`integer`, required): Cluster ID. Example: 12345

Example input: `{"cluster_id":12345}`

### `linode_lke_clusters_list`

List Kubernetes Clusters · Read-only

List LKE Kubernetes clusters.
Returns data[] (each with apl_enabled, control_plane, created, id, k8s_version, label, region, stack_type) plus page, pages, results.
Use linode_lke_clusters_list to find a cluster ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `linode_nodebalancer_get`

Get NodeBalancer · Read-only

Get one NodeBalancer with its IPs, region and transfer.
Returns an object with client_conn_throttle, created, hostname, id, ipv4, ipv6, label, lke_cluster, region, tags, and more.
Use linode_nodebalancer_get for one NodeBalancer.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `node_balancer_id` (`integer`, required): NodeBalancer ID. Example: 12345

Example input: `{"node_balancer_id":12345}`

### `linode_nodebalancers_list`

List NodeBalancers · Read-only

List NodeBalancers (load balancers).
Returns data[] (each with client_conn_throttle, created, hostname, id, ipv4, ipv6, label, lke_cluster) plus page, pages, results.
Use linode_nodebalancers_list to find a NodeBalancer.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{}`

### `linode_profile_get`

Get Profile · Read-only

Get the profile of the user who owns the token.
Returns an object with authentication_type, authorized_keys, email, email_notifications, ip_whitelist_enabled, lish_auth_method, referrals, restricted, timezone, two_factor_auth, and more.
Use linode_profile_get to check the connection and see who the token acts as.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `linode_regions_list`

List Regions · Read-only

List the data center regions and the services each offers.
Returns data[] (each with capabilities, country, id, label, monitors, placement_group_limits, resolvers, site_type) plus page, pages, results.
Use linode_regions_list to pick a region ID for new resources.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `linode_tags_list`

List Tags · Read-only

List the tags on the account.
Returns data[] (each with label) plus page, pages, results.
Use linode_tags_list to see how resources are grouped.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{}`

### `linode_types_list`

List Linode Plans · Read-only

List Linode plan types with CPU, memory, disk, transfer and price.
Returns data[] (each with addons, class, disk, gpus, id, label, memory, network_out) plus page, pages, results.
Use linode_types_list to pick a type ID for linode_instance_create or linode_instance_resize.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `linode_volume_get`

Get Volume · Read-only

Get one Block Storage volume with its size, region and attached Linode.
Returns an object with created, encryption, filesystem_path, hardware_type, id, io_ready, label, linode_id, linode_label, region, and more.
Use linode_volume_get for one volume.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `volume_id` (`integer`, required): Volume ID, from linode_volumes_list. Example: 12345
- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{"volume_id":12345}`

### `linode_volumes_list`

List Volumes · Read-only

List Block Storage volumes.
Returns data[] (each with created, encryption, filesystem_path, hardware_type, id, io_ready, label, linode_id) plus page, pages, results.
Use linode_volumes_list to find a volume ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Example: 1
- `page_size` (`integer`, optional): Results per page, 25 to 500 (default 100). Example: 100

Example input: `{}`

### `linode_domain_create`

Create Domain · Write

Add a domain to the Linode DNS Manager as a master or slave zone.
Returns an object with axfr_ips, description, domain, expire_sec, group, id, master_ips, refresh_sec, retry_sec, soa_email, and more.
Use linode_domain_create to host DNS for a domain on Linode.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domain` (`string`, required): Domain name. Example: example.com
- `type` (`string`, required): Zone type. One of: master, slave. Example: master. One of: `master`, `slave`.
- `axfr_ips` (`array`, optional): The list of IPs that may perform a zone transfer for this domain. The total combined length of all data within this array cannot exceed 1000 characters. > 📘 > > This is potentially dangerous, and should be set to an empty list unless you intend to use it. Example: ["value"]
- `description` (`string`, optional): A description for this domain. This is for display purposes only. Example: Short description
- `expire_sec` (`integer`, optional): The amount of time in seconds that may pass before this domain is no longer authoritative. - Valid values are 0, 30, 120, 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200. - Any other value is rounded up to the nearest valid value. - A value of 0 is equivalent to the default value of 1209600. Example: 300
- `master_ips` (`array`, optional): The IP addresses representing the master DNS for this domain. At least one value is required for type slave domains. The total combined length of all data within this array cannot exceed 1000 characters. Example: ["value"]
- `refresh_sec` (`integer`, optional): The amount of time in seconds before this domain should be refreshed. - Valid values are 0, 30, 120, 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200. - Any other value is rounded up to the nearest valid value. - A value of 0 is equivalent to the default value of 14400. Example: 300
- `retry_sec` (`integer`, optional): The interval, in seconds, at which a failed refresh should be retried. - Valid values are 0, 30, 120, 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200. - Any other value is rounded up to the nearest valid value. - A value of 0 is equivalent to the default value of 14400. Example: 300
- `soa_email` (`string`, optional): SOA contact email; required for master zones. Example: admin@example.com
- `status` (`string`, optional): Used to control whether this domain is currently being rendered. One of: disabled, active. Example: active. One of: `disabled`, `active`.
- `tags` (`array`, optional): An array of tags applied to this object. Tags are for organizational purposes only. Example: ["example tag", "another example"]
- `ttl_sec` (`integer`, optional): "Time to Live" - the amount of time in seconds that this domain's records may be cached by resolvers or other domain servers. - Valid values are 0, 30, 120, 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200. - Any other value is rounded up to the nearest valid value. - A value of 0 is equivalent to the default value of 86400. Example: 300

Example input: `{"domain":"<domain>","type":"master"}`

### `linode_domain_record_create`

Create DNS Record · Write

Add a DNS record (A, AAAA, CNAME, MX, TXT, SRV, CAA, NS) to a domain.
Returns an object with created, id, name, port, priority, protocol, service, tag, target, ttl_sec, and more.
Use linode_domain_record_create to point a hostname somewhere.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domain_id` (`integer`, required): Domain ID, from linode_domains_list. Example: 1234
- `type` (`string`, required): Record type. One of: A, AAAA, NS, MX, CNAME, TXT, SRV, PTR, CAA. Example: A. One of: `A`, `AAAA`, `NS`, `MX`, `CNAME`, `TXT`, `SRV`, `PTR`, `CAA`.
- `name` (`string`, optional): Hostname relative to the domain; empty for the apex. Example: www
- `port` (`integer`, optional): The port this Record points to. Only valid and required for SRV record requests. Example: 80
- `priority` (`integer`, optional): The priority of the target host for this Record. Lower values are preferred. Only valid for MX and SRV record requests. Required for SRV record requests. Defaults to 0 for MX record requests. Must be 0 for Null MX records. Example: 50
- `protocol` (`string`, optional): The protocol this Record's service communicates with. An underscore (_) is prepended automatically to the submitted value for this property. Only valid for SRV record requests. Example: example
- `service` (`string`, optional): The name of the service. An underscore (_) is prepended and a period (.) is appended automatically to the submitted value for this property. Only valid and required for SRV record requests. Example: example
- `tag` (`string`, optional): The tag portion of a CAA record. Only valid and required for CAA record requests. One of: issue, issuewild, iodef. Example: issue. One of: `issue`, `issuewild`, `iodef`.
- `target` (`string`, optional): Record target, such as an IP address or hostname. Example: 203.0.113.10
- `ttl_sec` (`integer`, optional): "Time to Live" - the amount of time in seconds that this Domain's records may be cached by resolvers or other domain servers. Valid values are 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200 - any other value will be rounded to the nearest valid value. Example: 604800
- `weight` (`integer`, optional): The relative weight of this Record used in the case of identical priority. Higher values are preferred. Only valid and required for SRV record requests. Example: 50

Example input: `{"domain_id":1234,"type":"A"}`

### `linode_domain_record_update`

Update DNS Record · Write

Update a DNS record.
Returns an object with created, id, name, port, priority, protocol, service, tag, target, ttl_sec, and more.
Use linode_domain_record_update to change a record target or TTL.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain_id` (`integer`, required): Domain ID, from linode_domains_list. Example: 1234
- `record_id` (`integer`, required): Record ID from linode_domain_records_list. Example: 5678
- `name` (`string`, optional): Hostname relative to the domain. Example: www
- `port` (`integer`, optional): The port this Record points to. Only valid and required for SRV record requests. Example: {{port}}
- `priority` (`integer`, optional): The priority of the target host for this Record. Lower values are preferred. Only valid for MX and SRV record requests. Required for SRV record requests. Defaults to 0 for MX record requests. Must be 0 for Null MX records. Example: {{priority}}
- `protocol` (`string`, optional): The protocol this Record's service communicates with. An underscore (_) is prepended automatically to the submitted value for this property. Only valid for SRV record requests. Example: {{protocol}}
- `service` (`string`, optional): The name of the service. An underscore (_) is prepended and a period (.) is appended automatically to the submitted value for this property. Only valid and required for SRV record requests. Example: {{service}}
- `tag` (`string`, optional): The tag portion of a CAA record. Only valid and required for CAA record requests. One of: issue, issuewild, iodef. Example: {{tag}}. One of: `issue`, `issuewild`, `iodef`.
- `target` (`string`, optional): Record target. Example: 203.0.113.11
- `ttl_sec` (`integer`, optional): "Time to Live" - the amount of time in seconds that this Domain's records may be cached by resolvers or other domain servers. Valid values are 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200 - any other value will be rounded to the nearest valid value. Example: {{ttl_sec}}
- `weight` (`integer`, optional): The relative weight of this Record used in the case of identical priority. Higher values are preferred. Only valid and required for SRV record requests. Example: {{weight}}

Example input: `{"domain_id":1234,"record_id":5678}`

### `linode_domain_update`

Update Domain · Write

Update a DNS domain settings.
Returns an object with axfr_ips, description, domain, expire_sec, group, id, master_ips, refresh_sec, retry_sec, soa_email, and more.
Use linode_domain_update to change SOA, TTLs, status or tags.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain_id` (`integer`, required): Domain ID, from linode_domains_list. Example: 1234
- `axfr_ips` (`array`, optional): The list of IPs that may perform a zone transfer for this domain. The total combined length of all data within this array cannot exceed 1000 characters. > 📘 > > This is potentially dangerous, and should be set to an empty list unless you intend to use it. Example: ["value"]
- `description` (`string`, optional): A description for this domain. This is for display purposes only. Example: {{description}}
- `domain` (`string`, optional): The domain this domain represents. domain labels cannot be longer than 63 characters and must conform to RFC1035. domains must be unique on Linode's platform, including across different Linode accounts; there cannot be two domains representing the same domain. Example: {{domain}}
- `expire_sec` (`integer`, optional): The amount of time in seconds that may pass before this domain is no longer authoritative. - Valid values are 0, 30, 120, 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200. - Any other value is rounded up to the nearest valid value. - A value of 0 is equivalent to the default value of 1209600. Example: {{expire_sec}}
- `master_ips` (`array`, optional): The IP addresses representing the master DNS for this domain. At least one value is required for type slave domains. The total combined length of all data within this array cannot exceed 1000 characters. Example: ["value"]
- `refresh_sec` (`integer`, optional): The amount of time in seconds before this domain should be refreshed. - Valid values are 0, 30, 120, 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200. - Any other value is rounded up to the nearest valid value. - A value of 0 is equivalent to the default value of 14400. Example: {{refresh_sec}}
- `retry_sec` (`integer`, optional): The interval, in seconds, at which a failed refresh should be retried. - Valid values are 0, 30, 120, 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200. - Any other value is rounded up to the nearest valid value. - A value of 0 is equivalent to the default value of 14400. Example: {{retry_sec}}
- `soa_email` (`string`, optional): Start of Authority email address. This is required for type master domains. Example: {{soa_email}}
- `status` (`string`, optional): Used to control whether this domain is currently being rendered. One of: disabled, active. Example: {{status}}. One of: `disabled`, `active`.
- `tags` (`array`, optional): An array of tags applied to this object. Tags are for organizational purposes only. Example: ["example tag", "another example"]
- `ttl_sec` (`integer`, optional): "Time to Live" - the amount of time in seconds that this domain's records may be cached by resolvers or other domain servers. - Valid values are 0, 30, 120, 300, 3600, 7200, 14400, 28800, 57600, 86400, 172800, 345600, 604800, 1209600, and 2419200. - Any other value is rounded up to the nearest valid value. - A value of 0 is equivalent to the default value of 86400. Example: {{ttl_sec}}
- `type` (`string`, optional): Whether this domain represents the authoritative source of information for the domain it describes (master), or whether it is a read-only copy of a master (slave). One of: master, slave. Example: {{type}}. One of: `master`, `slave`.

Example input: `{"domain_id":1234}`

### `linode_firewall_create`

Create Firewall · Write

Create a Cloud Firewall with inbound and outbound rules, optionally assigned to Linodes.
Returns an object with created, entities, id, label, rules, status, tags, updated.
Use linode_firewall_create to protect servers.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `label` (`string`, required): Firewall label. Example: web-fw
- `rules` (`object`, required): Rules object with inbound and outbound rule lists and inbound_policy/outbound_policy (ACCEPT or DROP). Example: {"inbound_policy": "DROP", "outbound_policy": "ACCEPT", "inbound": [{"action": "ACCEPT", "protocol": "TCP", "ports": "22,80,443", "addresses": {"ipv4": ["0.0.0.0/0"]}}], "outbound": []}
- `devices` (`object`, optional): Linodes or NodeBalancers to assign, as {"linodes": [ids], "nodebalancers": [ids]}. Example: {"linodes": [123456]}
- `tags` (`array`, optional): An array of tags applied to this object. Tags are for organizational purposes only. Example: ["example tag", "another example"]

Example input: `{"label":"<label>","rules":{}}`

### `linode_firewall_device_create`

Assign Firewall · Write

Assign a firewall to a Linode, NodeBalancer or interface.
Returns an object with created, entity, id, updated.
Use linode_firewall_device_create to protect another server with an existing firewall.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `firewall_id` (`integer`, required): Firewall ID, from linode_firewalls_list. Example: 1234
- `id` (`integer`, required): ID of the Linode, NodeBalancer or interface. Example: 123456
- `type` (`string`, required): Device type. One of: linode, nodebalancer, linode_interface. Example: linode. One of: `linode`, `nodebalancer`, `linode_interface`.

Example input: `{"firewall_id":1234,"id":123456,"type":"linode"}`

### `linode_firewall_rules_update`

Update Firewall Rules · Write

Replace the inbound and outbound rules of a firewall.
Returns an object with fingerprint, inbound, inbound_policy, outbound, outbound_policy, version.
Use linode_firewall_rules_update to open or close ports.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `firewall_id` (`integer`, required): Firewall ID, from linode_firewalls_list. Example: 1234
- `inbound` (`string`, optional): Inbound rules; each has action (ACCEPT or DROP), protocol, ports and addresses. This list replaces the current inbound rules. Example: [{"action": "ACCEPT", "protocol": "TCP", "ports": "22,443", "addresses": {"ipv4": ["0.0.0.0/0"]}, "label": "ssh-https"}]
- `inbound_policy` (`string`, optional): The default behavior for inbound traffic. This setting can be overridden by updating the inbound.action property of the Firewall Rule. One of: ACCEPT, DROP. Example: DROP. One of: `ACCEPT`, `DROP`.
- `outbound` (`string`, optional): Outbound rules in the same shape; replaces the current outbound rules. Example: []
- `outbound_policy` (`string`, optional): The default behavior for outbound traffic. This setting can be overridden by updating the outbound.action property of the Firewall Rule. One of: ACCEPT, DROP. Example: ACCEPT. One of: `ACCEPT`, `DROP`.

Example input: `{"firewall_id":1234}`

### `linode_image_create`

Create Image · Write

Capture a private image from a Linode disk.
Returns an object with capabilities, created, created_by, deprecated, description, eol, expiry, id, image_sharing, is_public, and more.
Use linode_image_create to save a golden image of a configured server.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `disk_id` (`integer`, required): ID of the disk to capture, from linode_instance_disks_list. Example: 123456
- `cloud_init` (`boolean`, optional): Whether this image supports cloud-init. Example: {{cloud_init}}
- `description` (`string`, optional): A detailed description of this image. Example: {{description}}
- `label` (`string`, optional): The short title for this image. If not provided, the disk's current label is used. Example: {{label}}
- `tags` (`array`, optional): Tags used for organizational purposes. A tag can be from 3 to 100 characters long, and an image can have a maximum of 500 total tags. Example: ["repair-image", "fix-1"]

Example input: `{"disk_id":123456}`

### `linode_instance_boot`

Boot Linode · Write

Boot a Linode that is offline.
Returns the JSON response from the API.
Use linode_instance_boot to start a stopped Linode.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456
- `config_id` (`integer`, optional): The Linode Config ID to boot into. Example: {{config_id}}

Example input: `{"linode_id":123456}`

### `linode_instance_clone`

Clone Linode · Write

Clone a Linode disks and configs into a new or existing Linode.
Returns an object with alerts, backups, capabilities, created, disk_encryption, group, has_user_data, host_uuid, hypervisor, id, and more.
Use linode_instance_clone to duplicate a server.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456
- `backups_enabled` (`boolean`, optional): If this field is set to true, the created Linode will automatically be enrolled in the Linode Backup service. This will incur an additional charge. Pricing is included in the response from List types. - Can only be included when cloning to a new Linode. Example: {{backups_enabled}}
- `body_linode_id` (`integer`, optional): If an existing Linode is the target for the clone, the ID of that Linode. The existing Linode must have enough resources to accept the clone. Example: {{linode_id}}
- `configs` (`array`, optional): An array of configuration profile IDs. - If the configs parameter __is not provided__, then __all configuration profiles and their associated disks will be cloned__ from the source Linode. Any disks specified by the disks parameter will also be cloned. - __If an empty array is provided__ for the configs parameter, then __no configuration profiles (nor their associated disks) will be cloned__ from the source Linode. Example: [1, 2]
- `disks` (`array`, optional): An array of disk IDs. - If the disks parameter __is not provided__, then __no extra disks will be cloned__ from the source Linode. All disks associated with the configuration profiles specified by the configs parameter will still be cloned. - __If an empty array is provided__ for the disks parameter, then __no extra disks will be cloned__ from the source Linode. Example: [1, 2]
- `label` (`string`, optional): Label for the new Linode. Example: web-1-clone
- `maintenance_policy` (`string`, optional): Defines the maintenance policy for the new Linode. If you don't provide it, the new Linode inherits the maintenance policy from the original Linode. Review maintenance policy documentation for more details. One of: linode/migrate, linode/power_off_on. Example: {{maintenance_policy}}. One of: `linode/migrate`, `linode/power_off_on`.
- `metadata` (`object`, optional): An object containing user-defined data relevant to the creation of Linodes. Example: {"key": "value"}
- `private_ip` (`boolean`, optional): If true, the created Linode will have private networking enabled and assigned a private IPv4 address. - Can only be provided when cloning to a new Linode. Example: {{private_ip}}
- `region` (`string`, optional): Region for the new Linode. Example: us-east
- `type` (`string`, optional): Plan type for the new Linode. Example: g6-standard-1

Example input: `{"linode_id":123456}`

### `linode_instance_create`

Create Linode · Write

Create a Linode instance in a region with a plan type, optionally from an image with a root password and SSH keys. This starts billing.
Returns an object with alerts, backups, capabilities, created, disk_encryption, group, has_user_data, host_uuid, hypervisor, id, and more.
Use linode_instance_create for a new server. Follow progress with linode_events_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `region` (`string`, required): Region ID from linode_regions_list. Example: us-east
- `type` (`string`, required): Plan type ID from linode_types_list. Example: g6-nanode-1
- `authorized_keys` (`array`, optional): SSH public keys to add to root. Example: ["ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAA... user@host"]
- `backup_id` (`integer`, optional): A Backup ID from another Linode's available backups. Your User must have read_write access to that Linode, the Backup must have a status of successful, and the Linode must be deployed to the same region as the Backup. Run List backups for a Linode's available backups. This field and the image field are mutually exclusive. Example: 1234
- `backups_enabled` (`boolean`, optional): If this field is set to true, the created Linode will automatically be enrolled in the Linode Backup service. This will incur an additional charge. The cost for the Backup service is dependent on the Type of Linode deployed. This option is always treated as true if the account-wide backups_enabled setting is true. See Get account settings for more information. Example: true
- `booted` (`boolean`, optional): This field defaults to true if the Linode is created with an Image or from a Backup. If it is deployed from an Image or a Backup and you wish it to remain offline after deployment, set this to false. Example: true
- `disk_encryption` (`string`, optional): Local disk encryption ensures that your data stored on Linodes is secured. Disk encryption protects against unauthorized data access by keeping the data encrypted if the disk is ever removed from the data center, decommissioned, or disposed of. The platform manages the encryption and decryption for you. By default, encryption is enabled on all Linodes. One of: enabled, disabled. Example: enabled. One of: `enabled`, `disabled`.
- `firewall_id` (`integer`, optional): The id of the Firewall to attach this Linode to upon creation. This firewall_id field is for Linodes using VLAN and legacy configuration interfaces only. Example: 12345
- `image` (`string`, optional): Image ID from linode_images_list. Example: linode/ubuntu24.04
- `label` (`string`, optional): Unique name for the Linode. Example: web-1
- `maintenance_policy` (`string`, optional): Defines the maintenance policy for this Linode. Choose from the following policies: - linode/migrate: Migrates the Linode to a new host while it remains fully operational (with some performance degradation). Recommended for maximizing availability. - linode/power_off_on: Powers off the Linode at the start of the maintenance event and reboots it once the maintenance finishes. Recommended for maximizing performance. One of: linode/migrate, linode/power_off_on. Example: linode/migrate. One of: `linode/migrate`, `linode/power_off_on`.
- `network_helper` (`boolean`, optional): Enables the Network Helper feature. The default value is determined by the network_helper setting in the account settings. This network_helper field is for Linodes using Linode interfaces only. Example: true
- `private_ip` (`boolean`, optional): If true, the created Linode will have private networking enabled and assigned a private IPv4 address. Example: True
- `root_pass` (`string`, optional): Root password for the new Linode; required when image is set. Use a strong password. Example: Str0ng-Pass!2026
- `stackscript_id` (`integer`, optional): A StackScript ID that will cause the referenced StackScript to be run during deployment of this Linode. A compatible image is required to use a StackScript. To get a list of available StackScript and their permitted Images, run List StackScripts. This field cannot be used when deploying from a Backup or a Private Image. Example: 10079
- `swap_size` (`integer`, optional): When deploying from an Image, this field is optional, otherwise it is ignored. This is used to set the swap disk size for the newly created Linode. Example: 512
- `tags` (`array`, optional): Tags to apply. Example: ["production"]

Example input: `{"region":"<region>","type":"<type>"}`

### `linode_instance_reboot`

Reboot Linode · Write

Reboot a Linode.
Returns the JSON response from the API.
Use linode_instance_reboot to restart a running Linode.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456
- `config_id` (`integer`, optional): The Linode Config ID to reboot into. If null or omitted, the last booted config will be used. If there was no last booted config and this Linode only has one config, it will be used. If a config cannot be determined, an error will be returned. Example: {{config_id}}

Example input: `{"linode_id":123456}`

### `linode_instance_resize`

Resize Linode · Write

Move a Linode to another plan type. The Linode goes offline during the resize.
Returns the JSON response from the API.
Use linode_instance_resize to scale a server up or down.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456
- `type` (`string`, required): Target plan type ID from linode_types_list. Example: g6-standard-2
- `allow_auto_disk_resize` (`boolean`, optional): Automatically resize disks when resizing a Linode. When resizing down to a smaller plan your Linode's data must fit within the smaller disk size. Example: {{allow_auto_disk_resize}}
- `migration_type` (`string`, optional): Type of migration used in moving to a new host or Linode type. warm: the Linode will not power down until the migration is complete. Warm migrations are not available for DC migrations. cold: the Linode will be powered down and migrated. When the migration is complete, the Linode will be powered on. One of: warm, cold. Example: {{migration_type}}. One of: `warm`, `cold`.

Example input: `{"linode_id":123456,"type":"<type>"}`

### `linode_instance_shutdown`

Shut Down Linode · Write

Shut down a Linode (billing continues while it is stopped).
Returns the JSON response from the API.
Use linode_instance_shutdown to stop a Linode.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456

Example input: `{"linode_id":123456}`

### `linode_instance_snapshot_create`

Create Linode Snapshot · Write

Take a manual snapshot backup of a Linode (backups must be enabled). It replaces the previous snapshot.
Returns an object with available, configs, created, disks, finished, id, label, status, type, updated.
Use linode_instance_snapshot_create before risky changes.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `label` (`string`, required): Snapshot label. Example: before-upgrade
- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456

Example input: `{"label":"<label>","linode_id":123456}`

### `linode_instance_update`

Update Linode · Write

Update a Linode label, tags, group, alert thresholds or watchdog setting.
Returns an object with alerts, backups, capabilities, created, disk_encryption, group, has_user_data, host_uuid, hypervisor, id, and more.
Use linode_instance_update to rename or retag a Linode. Use linode_instance_resize to change its plan.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456
- `alerts` (`object`, optional): Alert thresholds to change, such as cpu (percent), io, network_in, network_out and transfer_quota. Example: {"cpu": 90}
- `label` (`string`, optional): Provides a name for the Linode. If not provided, the API generates one for it. Linode labels have the following constraints: - It needs to begin and end with an alphanumeric character. - It can only consist of alphanumeric characters, hyphens (-), underscores (_) or periods (.). - Cannot have two hyphens (--), underscores (__) or periods (..) in a row. Example: {{label}}
- `tags` (`array`, optional): Tags to help you organize your content. Example: ["example tag", "another example"]
- `watchdog_enabled` (`boolean`, optional): The watchdog, named Lassie, is a Shutdown Watchdog that monitors your Linode and reboots it if it powers off unexpectedly. It works by issuing a boot job when your Linode powers off without a shutdown job being responsible. To prevent a loop, Lassie gives up if there have been more than 5 boot jobs issued within 15 minutes. Example: {{watchdog_enabled}}

Example input: `{"linode_id":123456}`

### `linode_volume_attach`

Attach Volume · Write

Attach a volume to a Linode in the same region.
Returns an object with created, encryption, filesystem_path, hardware_type, id, io_ready, label, linode_id, linode_label, region, and more.
Use linode_volume_attach to mount extra storage on a server.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `linode_id` (`integer`, required): Linode to attach to. Example: 123456
- `volume_id` (`integer`, required): Volume ID, from linode_volumes_list. Example: 12345
- `config_id` (`integer`, optional): The unique identifier assigned to the Linode configuration where you want to include this volume. Run the List configuration profiles operation and store the id for the target configuration. > 📘 > > - The configuration needs to belong to the Linode referenced by linode_id. > > - If you don't include this value, the API uses the last booted configuration. Example: {{config_id}}
- `persist_across_boots` (`boolean`, optional): If set to false, the volume won't be attached to the Linode configuration. In this case, more than eight volumes may be attached to a Linode if a Linode has 16GB of RAM or more. The number of volumes you can attach is equal to the number of GB of RAM that the Linode has, up to a maximum of 64. If you set this to false, you can't include a config_id and only the linode_id should be passed. Example: {{persist_across_boots}}

Example input: `{"linode_id":123456,"volume_id":12345}`

### `linode_volume_create`

Create Volume · Write

Create a Block Storage volume, optionally attached to a Linode. This starts billing.
Returns an object with created, encryption, filesystem_path, hardware_type, id, io_ready, label, linode_id, linode_label, region, and more.
Use linode_volume_create to add storage.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `label` (`string`, required): Volume label. Example: data-1
- `config_id` (`integer`, optional): When creating a volume attached to a Linode, this is the identifier of the Linode configuration profile (config) where the volume will live. Run the List configuration profiles operation and store the id for the applicable config. The following apply when adding a config_id: - The selected config needs to belong to the Linode referenced by linode_id in this request. Example: {{config_id}}
- `encryption` (`string`, optional): Enables encryption on the volume. Full disk encryption ensures the data stored on a block storage volume drive is secure. It protects against unauthorized access by keeping the data encrypted if the volume drive is removed from the data center, decommissioned, or disposed of. The platform automatically manages the encryption and decryption process for you. One of: enabled, disabled. Example: {{encryption}}. One of: `enabled`, `disabled`.
- `linode_id` (`integer`, optional): Linode to attach the new volume to. Example: 123456
- `region` (`string`, optional): Region ID; required unless linode_id is given. Example: us-east
- `size` (`integer`, optional): Size in GB (10 to 16384, default 20). Example: 20
- `tags` (`array`, optional): Any tags applied to this object. Use tags to label and organize your cloud computing resources. Example: ["example tag", "another example"]

Example input: `{"label":"<label>"}`

### `linode_volume_detach`

Detach Volume · Write

Detach a volume from its Linode.
Returns the JSON response from the API.
Use linode_volume_detach before moving or deleting a volume.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `volume_id` (`integer`, required): Volume ID, from linode_volumes_list. Example: 12345

Example input: `{"volume_id":12345}`

### `linode_volume_resize`

Resize Volume · Write

Grow a volume to a larger size (volumes cannot shrink).
Returns an object with created, encryption, filesystem_path, hardware_type, id, io_ready, label, linode_id, linode_label, region, and more.
Use linode_volume_resize to add space.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `size` (`integer`, required): New size in GB, larger than the current size. Example: 40
- `volume_id` (`integer`, required): Volume ID, from linode_volumes_list. Example: 12345

Example input: `{"size":40,"volume_id":12345}`

### `linode_domain_delete`

Delete Domain · Destructive

Delete a domain and all its records from the DNS Manager.
Returns the JSON response from the API.
Use linode_domain_delete only to stop hosting DNS for a domain.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `domain_id` (`integer`, required): Domain ID, from linode_domains_list. Example: 1234

Example input: `{"domain_id":1234}`

### `linode_domain_record_delete`

Delete DNS Record · Destructive

Delete a DNS record.
Returns the JSON response from the API.
Use linode_domain_record_delete to remove a record.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `domain_id` (`integer`, required): Domain ID, from linode_domains_list. Example: 1234
- `record_id` (`integer`, required): Record ID. Example: 5678

Example input: `{"domain_id":1234,"record_id":5678}`

### `linode_firewall_delete`

Delete Firewall · Destructive

Delete a firewall and remove it from all its devices.
Returns the JSON response from the API.
Use linode_firewall_delete to remove a firewall for good.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `firewall_id` (`integer`, required): Firewall ID, from linode_firewalls_list. Example: 1234

Example input: `{"firewall_id":1234}`

### `linode_image_delete`

Delete Image · Destructive

Delete a private image.
Returns the JSON response from the API.
Use linode_image_delete to remove an image you no longer need.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `image_id` (`string`, required): Private image ID. Example: private/12345

Example input: `{"image_id":"<image_id>"}`

### `linode_instance_delete`

Delete Linode · Destructive

Delete a Linode instance with its disks and backups. This cannot be undone.
Returns the JSON response from the API.
Use linode_instance_delete only to destroy a server for good.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456

Example input: `{"linode_id":123456}`

### `linode_instance_rebuild`

Rebuild Linode · Destructive

Rebuild a Linode from an image, wiping its disks.
Returns an object with alerts, backups, capabilities, created, disk_encryption, group, has_user_data, host_uuid, hypervisor, id, and more.
Use linode_instance_rebuild to reinstall the operating system. This erases all data on the Linode.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `image` (`string`, required): Image ID to rebuild from. Example: linode/ubuntu24.04
- `linode_id` (`integer`, required): Linode instance ID, from linode_instances_list. Example: 123456
- `root_pass` (`string`, required): New root password. Example: Str0ng-Pass!2026
- `authorized_keys` (`array`, optional): A list of public SSH keys that will be automatically appended to the root user's ~/.ssh/authorized_keys file when deploying from an Image. Example: ["ssh-rsa AAAA_valid_public_ssh_key_123456785== user@their-computer"]
- `booted` (`boolean`, optional): This field defaults to true if the Linode is created with an Image or from a Backup. If it is deployed from an Image or a Backup and you wish it to remain offline after deployment, set this to false. Example: true
- `disk_encryption` (`string`, optional): Local disk encryption ensures that your data stored on Linodes is secured. Disk encryption protects against unauthorized data access by keeping the data encrypted if the disk is ever removed from the data center, decommissioned, or disposed of. The platform manages the encryption and decryption for you. By default, encryption is enabled on all Linodes. One of: enabled, disabled. Example: enabled. One of: `enabled`, `disabled`.
- `maintenance_policy` (`string`, optional): Defines the maintenance policy for this Linode. Choose from the following policies: - linode/migrate: Migrates the Linode to a new host while it remains fully operational (with some performance degradation). Recommended for maximizing availability. - linode/power_off_on: Powers off the Linode at the start of the maintenance event and reboots it once the maintenance finishes. Recommended for maximizing performance. One of: linode/migrate, linode/power_off_on. Example: linode/migrate. One of: `linode/migrate`, `linode/power_off_on`.
- `stackscript_id` (`integer`, optional): A StackScript ID that will cause the referenced StackScript to be run during deployment of this Linode. A compatible image is required to use a StackScript. To get a list of available StackScript and their permitted Images, run List StackScripts. This field cannot be used when deploying from a Backup or a Private Image. Example: 10079
- `type` (`string`, optional): The ID of the Linode type to resize to with this request. Example: g6-standard-2

Example input: `{"image":"<image>","linode_id":123456,"root_pass":"<root_pass>"}`

### `linode_volume_delete`

Delete Volume · Destructive

Delete a detached volume and its data.
Returns the JSON response from the API.
Use linode_volume_delete only to destroy a volume for good.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `volume_id` (`integer`, required): Volume ID, from linode_volumes_list. Example: 12345

Example input: `{"volume_id":12345}`

## Related

Other Developer Tools connectors ([all 200](/agentkit/connectors/?category=developer-tools)):

- [GitHub](/agentkit/connectors/github/): Scalekit connector, OAuth, 217 tools
- [Datadog](/agentkit/connectors/datadog/): Scalekit connector, API key, 105 tools
- [Linear](/agentkit/connectors/linear/): Scalekit connector, OAuth, 64 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
