Actions17
Overview
This node interacts with the Petstore API to find pets filtered by their status. It is useful in scenarios where you want to retrieve a list of pets based on whether they are available, pending adoption, or sold. For example, an animal shelter could use this node to display all currently available pets for adoption on their website or to track pets that have been sold.
Properties
| Name | Meaning |
|---|---|
| Status | Status values that need to be considered for filter. Options: Available, Pending, Sold. |
Output
The node outputs JSON data representing the list of pets matching the selected status. Each item in the output typically contains details about a pet such as its id, name, category, photo URLs, tags, and status. The exact structure follows the Petstore API response schema for pets.
No binary data output is produced by this node.
Dependencies
- Requires access to the Petstore API at
https://petstore3.swagger.io/api/v3. - Optionally requires an API authentication token configured in n8n credentials (referred generically as "an API key credential").
- Uses standard HTTP headers for JSON content negotiation (
AcceptandContent-Typeset toapplication/json).
Troubleshooting
- Common issues:
- Network connectivity problems preventing access to the Petstore API.
- Invalid or missing API authentication token if the API requires it.
- Incorrect status value selection (should be one of available, pending, or sold).
- Error messages:
- HTTP 401 Unauthorized: Check that the API authentication token is correctly configured.
- HTTP 400 Bad Request: Verify that the status parameter is valid and properly formatted.
- HTTP 500 Internal Server Error: Indicates an issue on the Petstore API side; retry later or contact API provider.
Links and References
- Petstore API Documentation
- n8n HTTP Request Node Documentation (for understanding how API requests are made)