n8n and the REST API

The n8n community node

The node is n8n-nodes-gsc-wizard, an n8n community node that talks to the GSC Wizard REST API.

1. In n8n, open Settings → Community Nodes, select Install, enter n8n-nodes-gsc-wizard and confirm.
2. On the MCP API keys page in GSC Wizard, create a key. Give it Read & write access if the workflow creates annotations, submits sitemaps or sends IndexNow URLs; a read-only key runs every read operation.
3. In n8n, create a GSC Wizard API credential and paste the key. n8n checks it against your account when you save.
4. Add the GSC Wizard node to a workflow, pick an operation and a property. Pick the property from the list, or enter it as sc-domain:example.com or https://www.example.com/.

The operations cover the account and its properties, performance summaries, top queries, pages, countries and devices, custom Search Console reports with filters, page and query trends, ranking changes, anomalies, cannibalization, decaying content, opportunity scoring, GA4 overviews and reports, URL inspection, sitemaps, IndexNow and annotations. List-shaped reports return one n8n item per row, which is what a Google Sheets, Airtable or Slack node expects, and the n8n AI Agent can use every operation as a tool.

Three example workflows, a weekly list of decaying pages, inspecting and submitting a page when your CMS publishes it, and annotating every deploy on the performance chart, are in the node’s repository.

The reverse direction, GSC Wizard calling n8n when an alert fires, is done with outbound webhooks.

The REST API

The REST API lives at https://mcp.gscwizard.com/v1 and runs every request through the same code as the MCP server, so the answers are identical. Send the key as Authorization: Bearer gscw_live_...; a read-only key cannot call a tool that changes something.

{site} is the URL-encoded property, such as sc-domain%3Aexample.com. Other inputs go on the query string (?startDate=2026-10-01&limit=50); anything that does not fit a query string, such as GA4 filters, goes through the generic POST /v1/tools/{name} route.

# a curated GET
curl -H "Authorization: Bearer gscw_live_..." \
  "https://mcp.gscwizard.com/v1/sites/sc-domain%3Aexample.com/top-queries?limit=25"

# any tool by name
curl -X POST -H "Authorization: Bearer gscw_live_..." \
  -H "Content-Type: application/json" \
  -d '{"siteUrl":"sc-domain:example.com","limit":25}' \
  "https://mcp.gscwizard.com/v1/tools/query_top_queries"

• The spec. GET /v1/openapi.json is an OpenAPI 3.1 document generated from the same schemas the server validates against, and it needs no key, so you can read it before you sign up. GET /v1/tools lists every tool with its scope and route.
• Errors come back as { "error": { "code", "message" } } with a matching status: 400 for a bad request, 401 for a missing or revoked key, 402 when there is no active subscription or trial, 403 for a scope or sharing limit, 404, 429 with a Retry-After header, and 502 when Google or another upstream failed.
• Rate limits are 180 calls a minute and 2,000 an hour per account, counted separately from the MCP server.
• Server to server only. The API sends no CORS headers, so a key cannot be used from a web page, where anyone could read it. For a client portal, fetch on a schedule from your backend and render from your own store.

Troubleshooting