Actions14
- Marketplace Dataset Actions
- Web Scraper Actions
- Web Unlocker Actions
Overview
The "Get Snapshot Parts" operation within the "Marketplace Dataset" resource of this node allows users to retrieve detailed parts or segments of a specific snapshot from a dataset marketplace. This is useful when working with large datasets that are divided into multiple parts, enabling selective access or processing of individual snapshot components.
Common scenarios include:
- Downloading or analyzing specific portions of a dataset snapshot without handling the entire dataset.
- Integrating partial snapshot data into workflows for data transformation or enrichment.
- Managing large data snapshots efficiently by fetching only required parts.
For example, a user might have a snapshot ID representing a dataset of web-scraped product listings and want to fetch just one part containing data for a particular category or region.
Properties
| Name | Meaning |
|---|---|
| Snapshot ID | The unique identifier of the snapshot to operate on. Required to specify which snapshot's parts to retrieve. |
Output
The node outputs JSON data representing the parts of the specified snapshot. Each item in the output typically contains metadata or content related to a part of the snapshot, such as part identifiers, URLs, sizes, or other relevant details.
If the snapshot parts include binary data (e.g., files or compressed archives), the node may also output binary fields corresponding to those parts, allowing downstream nodes to process or store them accordingly.
Dependencies
- Requires an API key credential for authenticating requests to the Bright Data API.
- The node communicates with the Bright Data API endpoint at
https://api.brightdata.com. - Proper configuration of the API key credential in n8n is necessary for successful operation.
Troubleshooting
- Missing or invalid Snapshot ID: Ensure the Snapshot ID property is provided and correctly references an existing snapshot. Errors related to missing IDs will prevent retrieval.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions to access marketplace datasets.
- Network or API errors: Since the node ignores HTTP status errors by default, check the raw response or logs if unexpected results occur.
- Empty or incomplete snapshot parts: Confirm that the snapshot ID corresponds to a snapshot with available parts; some snapshots may not have parts or may be empty.
Links and References
- Bright Data API Documentation — For detailed information about endpoints and authentication.
- n8n Documentation — For guidance on setting up credentials and using custom nodes.