Actions10
Business → List
AI-generatedOverview
This node interacts with the Vulbox platform to list business-related data. Specifically, when using the "Business" resource with the "List" operation, it retrieves a paginated list of businesses from Vulbox. This is useful for scenarios where you want to fetch and process business entities managed or tracked within Vulbox, such as for security assessments, reporting, or integration with other systems.
Practical examples:
- Fetching a list of businesses to display in a dashboard.
- Searching businesses by name or keyword to filter relevant entities.
- Paginating through large sets of business records for batch processing.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of results to retrieve (default: 1). |
| Size | Number of items per page to return (default: 100). |
| Search | A search string to filter businesses by matching values. |
| Return Full Response | Whether to return the full API response including metadata instead of just the data array (true/false). |
Output
The output is a JSON array containing the list of businesses retrieved from Vulbox. Each item in the array represents a single business entity with its associated properties as returned by the Vulbox API.
If "Return Full Response" is enabled, the output includes the entire API response object, which may contain additional metadata such as pagination info, status codes, or other response details.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Vulbox API via an API key credential configured in n8n.
- The node depends on the Vulbox API service being available and accessible.
- No additional environment variables are required beyond the API authentication setup.
Troubleshooting
- Empty results: Ensure that the "Search" parameter is correctly specified or try increasing the "Size" or adjusting the "Page" number.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- API rate limits: If many requests are made rapidly, the Vulbox API might throttle requests; consider adding delays or handling retries.
- Invalid parameters: Confirm that numeric inputs like "Page" and "Size" are positive integers.
- Unexpected response structure: If "Return Full Response" is true, downstream nodes must handle the full response format rather than just the data array.
Links and References
- Vulbox Official Website
- Vulbox API Documentation (assumed URL for reference)