Google Maps Scraper icon

Google Maps Scraper

Interact with Google Maps Scraper API for scraping Google Maps data

Actions4

Overview

This node integrates with a Google Maps Scraper API to manage scraping jobs that collect data from Google Maps based on specified keywords and locations. The "Job" resource's "Get" operation retrieves detailed information about a specific scraping job by its unique Job ID.

Typical use cases include:

  • Monitoring the status and details of a previously created scraping job.
  • Fetching metadata or results summary for a particular job to decide further processing.
  • Integrating Google Maps data scraping workflows into automated pipelines where job management is required.

For example, after creating a scraping job to find coffee shops in New York, you can use this node operation to get the current status, progress, or other details of that job by providing its Job ID.

Properties

Name Meaning
Job ID The unique identifier of the scraping job to retrieve information for. Example: 6f0c1af8-3c4e-4742-84bb-590938ae8930

Output

The output JSON contains the full details of the requested scraping job as returned by the Google Maps Scraper API. This typically includes fields such as job name, status, creation date, keywords used, search parameters, and possibly progress or result summaries.

Example output structure (simplified):

{
  "id": "job-id-string",
  "name": "Coffee shops in New York",
  "status": "completed",
  "date": "2024-01-01T12:00:00Z",
  "keywords": ["coffee shop"],
  "lang": "en",
  "zoom": 15,
  "lat": "40.7128",
  "lon": "-74.0060",
  "fast_mode": false,
  "radius": 10,
  "depth": 1,
  "email": false,
  "max_time": 3600,
  "proxies": []
}

No binary data is output for this operation.

Dependencies

  • Requires an API key credential for the Google Maps Scraper API.
  • The node expects the base URL of the API to be configured in the credentials.
  • Network access to the Google Maps Scraper API endpoint is necessary.

Troubleshooting

  • Missing or invalid Job ID: If the Job ID parameter is empty or invalid, the node throws an error indicating that the Job ID is required. Ensure the Job ID is correctly provided, usually obtained from a previous job creation or listing operation.
  • Invalid base URL: If the configured API base URL is malformed, the node will throw an error. Verify the API base URL in the credentials configuration.
  • API request failures: Network issues, invalid API keys, or server errors may cause HTTP request failures. Check API credentials, network connectivity, and API service status.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion