Vulbox icon

Vulbox

Interact with Vulbox

Actions10

VPN → List

AI-generated

Overview

This node interacts with the Vulbox platform, specifically allowing users to list VPN resources among others. The "List" operation for the VPN resource fetches a paginated list of VPN entries from Vulbox, optionally filtered by a search term. This is useful for scenarios where you want to retrieve and process VPN-related data such as monitoring VPN configurations, auditing VPN usage, or integrating VPN information into workflows.

Practical examples:

  • Automatically retrieving all VPNs in batches for reporting or compliance checks.
  • Searching VPNs by name or other attributes to trigger alerts or updates.
  • Integrating VPN data into dashboards or other systems via n8n workflows.

Properties

Name Meaning
Page The page number of results to retrieve (pagination). Defaults to 1.
Size Number of items per page to return. Defaults to 100.
Search A string value to filter the VPN list by matching text.
Return Full Response Boolean flag indicating whether to return the full API response or just the data array.

Output

The node outputs JSON data representing the list of VPNs retrieved from Vulbox. The structure typically includes an array of VPN objects with their respective properties as returned by the Vulbox API.

If "Return Full Response" is set to true, the output will include the entire API response, which may contain metadata such as pagination info, status codes, or additional fields beyond the VPN list.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Vulbox API using an API key credential configured in n8n.
  • The node depends on the Vulbox API service being available and accessible.
  • No additional external dependencies are required beyond the Vulbox API credentials.

Troubleshooting

  • Empty results: If no VPNs are returned, verify that the page and size parameters are correct and that the search term matches existing VPN entries.
  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions to access VPN data.
  • API rate limits: Frequent requests might hit Vulbox API rate limits; consider adding delays or reducing request frequency.
  • Invalid parameter values: Passing non-numeric values for page or size can cause errors; ensure these are numbers.
  • Full response flag confusion: Setting "Return Full Response" to true changes the output format; downstream nodes must handle this accordingly.

Links and References

Discussion