DataForSEO

SEO and SEM data from DataForSEO — API docs: https://docs.dataforseo.com/v3

Connection: your API login and API password from app.dataforseo.com/api-access. The API password is issued separately by DataForSEO and is not your dashboard password — using the wrong one is the obvious first mistake, so the connection screen says so.

Base URL: https://api.dataforseo.com/v3, HTTP Basic.

Actions

Get Google Search Results, Get Keyword Search Volume, Get Backlinks Summary, Analyse Page (On-Page), Get Account.

Most actions need a location — either Location as DataForSEO spells it (United States, London,England,United Kingdom) or a numeric Location Code. The actions fail fast with a clear message when neither is set, rather than letting DataForSEO reject it.

Every call is billed, so the result includes the cost DataForSEO reported, and Get Account lets a flow check the balance before running a large batch.

Two API behaviours worth knowing

HTTP 200 does not mean success. DataForSEO returns 200 and puts the real outcome in status_code, at both the envelope and per-task level (20000 = success). This piece throws on any non-20000 status, carrying DataForSEO's own message — otherwise a flow would receive a "successful" step whose result is an error and carry on with it.

Write endpoints take an array of task objects, even for a single task. A bare object returns POST Data Is Empty.

No triggers

The live endpoints used here are request/response. DataForSEO's task-based (queued) endpoints accept a pingback_url, but that's a per-request callback rather than a subscription an onEnable/onDisable pair can manage, so there's nothing to build a trigger on against this surface.