SE Ranking n8n integration: the verified node, the plan you need and the setup steps

Does SE Ranking have an n8n integration? Yes, a verified node

Yes. SE Ranking has a dedicated n8n node, listed on n8n.io as a verified community node, and it works on both n8n Cloud and self-hosted n8n. It is not one of n8n's built-in core nodes. You install it once, add an SE Ranking API key, and call its actions from any workflow.

Here is exactly what the pages showed on 3 October 2026:

• n8n.io: an SE Ranking integration page that calls it a community node, credits an individual creator, and says it is verified by n8n.
• SE Ranking: its API documentation gives the package name, @seranking/n8n-nodes-seranking, hosted in SE Ranking's own GitHub organization. Its help center calls the node native, built and verified by SE Ranking.
• HTTP Request node: still an option for anything the node does not cover, using the same API key in an Authorization header.

This page is based on that documentation, not on a hands-on build.

What the SE Ranking node can do in n8n

The n8n listing describes 225 operations across 22 resources. They are actions you call, such as:

• Rank tracking: add keywords to a project, run a position check, get keyword statistics and competitor positions.
• Website Audit: launch a standard or JavaScript-rendered audit, check its status and pull the report.
• Backlinks and domains: backlink summaries, new and lost links, referring domains and domain overviews.
• Keyword research: metrics plus similar, related and question keywords.
• AI search: prompt rankings, brand mentions and source domains.

SE Ranking's walkthrough starts its example with a Manual Trigger and then swaps in n8n's Schedule Trigger. Neither page describes an SE Ranking event trigger, so plan on scheduled runs. For trigger-based lead routing, SE Ranking documents Zapier instead.

Which SE Ranking plan includes API access for n8n

Every current plan does. SE Ranking's API documentation says Core, Growth and Enterprise all include Data API access with a monthly credit allowance, and that the Project API is available on each of them with no add-on to buy. One API key covers both.

SE Ranking's own pages disagree on API credits: the pricing table lists 25,000 a month on Core and 100,000 on Growth, but its Rank Tracker page gives 100,000 for Core and 300,000 for Growth, so confirm the allowance before relying on it. The trial row is the API package's own trial, per the help center.

The Project API is limited to 5 requests per second and spends your plan limits rather than credits: a keyword added through n8n counts against your keyword quota. Accounts on older legacy plans may need the API add-on. If the allowance runs out, SE Ranking sells an annual API add-on and pay-as-you-go credit packs. No price is quoted here because the pricing page did not show US dollars. See the SE Ranking API guide and the pricing guide.

Setup steps for n8n Cloud and self-hosted n8n

1. Create an API key. In SE Ranking, open API in the left menu, go to the Dashboard and click Create API key. Copy it and store it somewhere private.
2. Install the node. On self-hosted n8n (version 1.0.0 or higher, Node.js 18 or higher), go to Settings, Community nodes, Install a community node, and enter @seranking/n8n-nodes-seranking. On n8n Cloud, click the plus button and search for SE Ranking. n8n's documentation says an instance owner or admin must install a verified node before other members can use it.
3. Add the credential. Open an SE Ranking node, choose Create new credential, paste the API token and save.
4. Import a template. SE Ranking publishes workflow files for audits, backlinks, keyword research, domain analysis and AI visibility in its GitHub repository. Download one, use Import from File, then set your domain and maximum pages.
5. Schedule it. Replace the Manual Trigger with a Schedule Trigger and use Execute step to test the output.

SE Ranking's own pages disagree on one detail. The setup guide tells you to select Data API as the API type in the credential, while the node's README says version 2.0.0 uses a single credential for both APIs. If you do not see an API type field, that is why.

Known limits, and what to check after the first run

• Credits. Only successful calls are charged. A domain overview costs 100 credits per request, so 25,000 credits cover 250 of them. Keyword metrics cost 10 credits per keyword, which is 2,500 keywords. Included plan credits renew and do not roll over.
• Rate limits. Going over returns an HTTP 429 error. SE Ranking's guide says to reduce how often the workflow runs.
• Delete actions. The node includes Delete Project, Delete Keywords and Delete Search Engine. Warning: SE Ranking's help center says deleting a search engine or region erases its ranking history with no recovery. Keep delete actions out of scheduled workflows until you have tested them on a spare project.
• Key security. API keys cannot be restricted by IP address or endpoint. If one leaks, delete or rotate it.

After the first run, open the API Dashboard and confirm the credits used match your estimate, compare one result with the same report inside SE Ranking, and check that the schedule is no more frequent than the data changes. The workflow automation guide covers alert thresholds.