TailscaleInstall

Summary

Set subnet routes for a specific device within a Tailscale tailnet by sending a list of CIDR subnet routes to advertise from that device.

Inputs

• Authentication (required) — Choose the authentication method (API Key or OAuth2) to access the Tailscale API.
• Tailnet Name or ID (required) — Select the tailnet (organization) name or ID. Use the default tailnet '-' or specify an expression to select a particular tailnet.
• Device Name or ID (required) — Select the device by name or ID on which to set the routes. Options can be loaded dynamically or specified via expression.
• Routes (required) — List one or more subnet routes in CIDR notation to advertise for this device within the tailnet.

Output shape

A single response object reflecting the API's acknowledgement or updated device routes.

The operation sends a POST request to the endpoint for the specified device's routes and does not declare a transformed output post-receive mapping, so the raw response from Tailscale API is returned. The routes array sent is extracted from the user input collection of route CIDRs.

Examples

Example 1: Set subnet routes 10.0.0.0/8 and 192.168.1.0/24 on device 'node123' in tailnet 'example-tailnet' using API key authentication.

Authentication = API Key; Tailnet = 'example-tailnet'; Device Name or ID = 'node123'; Routes = [{CIDR: 10.0.0.0/8}, {CIDR: 192.168.1.0/24}]

Links

• n8n community nodes installation guide