Actions5
Overview
The node interacts with the PaintSwap NFT marketplace to retrieve and analyze NFT sales and market data. Specifically, the "Get Collection Sales" operation fetches sales data for NFTs within a specified collection on the Ethereum blockchain. This is useful for users who want to monitor recent sales activity, analyze market trends, or gather data for collections they are interested in.
Practical examples include:
- Fetching recent sales of an NFT collection to track market demand.
- Filtering sales by specific token IDs within a collection.
- Sorting sales data in ascending or descending order by sale time or price.
- Limiting the number of sales fetched to manage data volume.
Properties
Name | Meaning |
---|---|
Collection Address | Ethereum address of the NFT collection contract to query sales from. |
Token IDs | Optional comma-separated list of token IDs to filter sales results (e.g., "123,456,789"). |
Number to Fetch | Number of sales records to retrieve, up to a maximum of 1000. |
Order Direction | Direction to order the sales results: "Ascending" or "Descending". |
Options | Additional options: • Simplify Output: Boolean flag to return only essential fields in the response. |
Output
The output is a JSON array where each item represents a sale record from the queried collection. The structure includes detailed information about each sale such as token ID, sale price, buyer, seller, timestamp, and other relevant metadata depending on the PaintSwap API response.
If the "Simplify Output" option is enabled, the response will contain a reduced set of key fields focusing on the most important sale details, making it easier to consume for common use cases.
The node does not output binary data.
Dependencies
- Requires access to the PaintSwap NFT marketplace API.
- Optionally requires an API authentication token configured in n8n credentials to increase request limits or access private endpoints.
- No additional environment variables are explicitly required based on the static code analysis.
Troubleshooting
Common issues:
- Invalid or missing collection address: Ensure the Ethereum address provided is correct and corresponds to an existing NFT collection.
- Exceeding maximum fetch limit: The node caps the number of sales fetched at 1000; requesting more may cause errors.
- Network or API errors: Temporary connectivity issues or API rate limits can cause failures.
Error messages:
"The operation \"getCollectionSales\" is not supported!"
— indicates an internal misconfiguration or unsupported operation selection.- API-related errors typically propagate with their message; enabling "Continue On Fail" allows processing subsequent items despite errors.
Resolutions:
- Verify input parameters carefully.
- Use valid Ethereum addresses.
- Respect API rate limits and pagination constraints.
- Enable "Continue On Fail" to handle partial failures gracefully.
Links and References
- PaintSwap NFT Marketplace
- Ethereum NFT standards and addresses documentation (for understanding collection addresses)
- n8n documentation on creating custom nodes and handling API integrations