BrightData icon

BrightData

Interact with Bright Data to scrape websites or use existing datasets from the marketplace to generate adapted snapshots

Actions14

Overview

The node interacts with the Bright Data platform, specifically allowing users to work with marketplace datasets. The "Get Snapshot Metadata" operation retrieves metadata information about a specific snapshot from the Bright Data marketplace dataset service. This is useful when you want to inspect details about a particular snapshot before processing or delivering its content.

Practical examples include:

  • Checking the status and properties of a data snapshot before downloading or further processing.
  • Validating that a snapshot exists and is accessible.
  • Retrieving metadata such as creation date, size, or other descriptive attributes related to the snapshot.

Properties

Name Meaning
Snapshot ID The unique identifier of the snapshot to operate on. This is required to specify which snapshot's metadata should be retrieved.

Output

The output JSON contains the metadata details of the specified snapshot. This typically includes fields describing the snapshot’s attributes such as its ID, creation time, status, size, and possibly other descriptive information provided by the Bright Data API.

If the node supports binary data output (not explicitly shown in the provided code), it would relate to snapshot content or parts, but for this operation, the focus is purely on metadata in JSON form.

Dependencies

  • Requires an API key credential for authenticating requests to the Bright Data API.
  • The node makes HTTP requests to https://api.brightdata.com.
  • Proper configuration of the API key credential within n8n is necessary for successful operation.

Troubleshooting

  • Common issues:

    • Invalid or missing Snapshot ID: Ensure the Snapshot ID is correctly provided and corresponds to an existing snapshot.
    • Authentication errors: Verify that the API key credential is valid and has the necessary permissions.
    • Network or API errors: Check connectivity and API availability; the node is configured to ignore HTTP status errors, so inspect returned error messages carefully.

  • Error messages:

    • "Snapshot not found": Indicates the Snapshot ID does not exist or is inaccessible.
    • "Unauthorized": Suggests invalid or missing API credentials.
    • Other HTTP errors may indicate rate limits, server issues, or malformed requests.

Resolving these usually involves verifying input parameters, credentials, and network conditions.

Links and References

Discussion