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 straight 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:
npm install n8n-nodes-cloro

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.

Operations

OperationEndpoint
MonitorPOST /v1/monitor/<provider>
Get CountriesGET /v1/countries
Get Task StatusGET /v1/tasks/{taskId}

Monitor

Pick a provider and the node calls the matching sync monitor endpoint:
  • Google Search — query, country, city, device (desktop/mobile), number of pages, include AI Overview, include HTML, include markdown
  • 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
Grok is still selectable, but the provider is temporarily unavailable — requests to it will fail until Grok access is restored.

Get Countries

Returns the supported countries, optionally filtered by provider — useful for validating country codes upstream in a workflow.

Get Task Status

Checks the status of an async task by its task ID, if you create tasks elsewhere and poll from n8n.

Example: monitoring Google Search results

Node: cloro
Provider: Google Search
Operation: Monitor
Query: "best coffee shops in New York"
Country: United States
Device: Desktop
Pages: 2
Include AI Overview: true
Include Markdown: true
The node returns the same JSON as the Google Search endpoint — organic results, People Also Ask, related searches, and the AI Overview when requested — ready to wire into filters, spreadsheets, or notifications.
Monitor calls run synchronously and count against your concurrency limits. Each call consumes credits at the standard per-provider rates — see Providers and Credits & limits.