Linode (Akamai)

Cloud computing API for managing instances, volumes, networking, and Kubernetes clusters.

Detail	Value
Category	Cloud & Infra
Base URL	https://api.linode.com/v4
Authentication	OAuth2
Endpoints	6
Connector key	linode

Using Linode (Akamai) in a workflow

1. Go to Connections and click New Connection.
2. Pick Linode (Akamai) from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /linode/instances	List Linode instances
POST /linode/instances	Create a Linode instance
GET /linode/instances/{linodeId}	Get a Linode instance
DELETE /linode/instances/{linodeId}	Delete a Linode instance
GET /volumes	List volumes
GET /regions	List available regions

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /linode/instances

List Linode instances

Detail	Value
Operation ID	cloud.listInstances
Method	GET
Path	/linode/instances

Parameters

Name	Location	Type	Required
page	query	integer	No
page_size	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Linode (Akamai) connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listInstances.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Linode (Akamai) API reference.

POST /linode/instances

Create a Linode instance

Detail	Value
Operation ID	cloud.createInstance
Method	POST
Path	/linode/instances

Parameters

No parameters.

Request Body

Field	Type
region	string
type	string
image	string
root_pass	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Linode (Akamai) connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.createInstance.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Linode (Akamai) API reference.

GET /linode/instances/{linodeId}

Get a Linode instance

Detail	Value
Operation ID	cloud.getInstance
Method	GET
Path	/linode/instances/{linodeId}

Parameters

Name	Location	Type	Required
linodeId	path	integer	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Linode (Akamai) connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.getInstance.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Linode (Akamai) API reference.

DELETE /linode/instances/{linodeId}

Delete a Linode instance

Detail	Value
Operation ID	cloud.deleteInstance
Method	DELETE
Path	/linode/instances/{linodeId}

Parameters

Name	Location	Type	Required
linodeId	path	integer	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Linode (Akamai) connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.deleteInstance.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Linode (Akamai) API reference.

GET /volumes

List volumes

Detail	Value
Operation ID	cloud.listVolumes
Method	GET
Path	/volumes

Parameters

Name	Location	Type	Required
page	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Linode (Akamai) connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listVolumes.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Linode (Akamai) API reference.

GET /regions

List available regions

Detail	Value
Operation ID	cloud.listRegions
Method	GET
Path	/regions

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Linode (Akamai) connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listRegions.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Linode (Akamai) API reference.