Skip to main content
The cloro community node (n8n-nodes-cloro) adds a cloro node to n8n that calls the sync monitor endpoints and returns parsed, structured results into your workflow. It’s listed in the n8n integrations directory.

​
Prerequisites

​
Install the node

In the n8n UI, go to Settings → Community nodes → Install and search for n8n-nodes-cloro. On a self-hosted instance you can also install it from the n8n installation directory:

​
Configure credentials

Create a new cloro API credential and paste your API key. The node sends it on every request as a Bearer token in the Authorization header.

​
Resources and operations

Since node version 0.2.0, each AI engine is its own resource, mapping 1:1 to the matching sync monitor endpoint:
Workflows built with earlier node versions keep the original single Monitor operation with a provider dropdown and continue to run unchanged.
Monitor fields by resource:
  • Google Search — query, country, city, device (desktop/mobile), number of pages, include AI Overview, include HTML, include markdown
  • Google News — query, country (required), device (desktop/mobile), number of pages (1-10), include HTML
  • ChatGPT — prompt, country, include HTML, include markdown, include raw response, include search queries (query fan-out)
  • Google AI Mode, Google Gemini, Grok, Microsoft Copilot, Perplexity — prompt, country, include HTML, include markdown
Country: Get Many returns the supported countries, optionally filtered by engine — useful for validating country codes upstream in a workflow. Task: Get Status checks an async task by its task ID, if you create tasks elsewhere and poll from n8n.

​
Example: monitoring Google Search results

The node returns the same JSON as the Google Search endpoint: organic results, People Also Ask, related searches, and the AI Overview when requested.
Monitor calls run synchronously and count against your concurrency limits. Each call consumes credits at the standard per-provider rates — see Providers and Billing & credits.