Google Maps Scraper icon

Google Maps Scraper

Interact with Google Maps Scraper API for scraping Google Maps data

Actions4

Overview

This node interacts with a Google Maps Scraper API to manage scraping jobs related to Google Maps data. Specifically, the Delete Job operation allows users to delete a specific scraping job by its ID. This is useful for cleaning up old or unwanted scraping tasks, managing quota, or removing irrelevant data collection jobs.

Typical use cases include:

  • Removing completed or failed scraping jobs to keep the job list manageable.
  • Automating cleanup of jobs after processing their results.
  • Managing job lifecycle programmatically within an n8n workflow.

Example: You have a workflow that scrapes coffee shop data from Google Maps and after downloading the results, you want to delete the job to avoid cluttering your job list.

Properties

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

Output

The output JSON object confirms the deletion of the job and includes:

  • success: A boolean indicating if the deletion was successful (true).
  • jobId: The ID of the deleted job.
  • message: A confirmation message string, e.g., "Job deleted successfully".

No binary data is output for this operation.

Example output:

{
  "success": true,
  "jobId": "6f0c1af8-3c4e-4742-84bb-590938ae8930",
  "message": "Job deleted successfully"
}

Dependencies

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

Troubleshooting

  • Missing Job ID: If the Job ID parameter is empty or not provided, the node will throw an error stating "Job ID is required." Ensure the Job ID is correctly passed to the node.
  • Invalid Base URL: If the API base URL in credentials is malformed, an error "Invalid base URL" will occur. Verify the URL format in the credential settings.
  • API Request Failures: Network issues, invalid API keys, or permission problems can cause HTTP errors. Check API credentials and network connectivity.
  • Job Not Found: Deleting a non-existent job may result in an error from the API. Confirm the Job ID exists before attempting deletion.

To resolve these issues:

  • Double-check input parameters and ensure Job ID is correct.
  • Validate API credentials and base URL configuration.
  • Handle errors gracefully using the node's "Continue On Fail" option if needed.

Links and References

Discussion