Menu

Mattering Automations Moz integration

Connect Moz to Mattering Automations: Domain Authority and Brand Authority, backlinks, linking domains, anchor texts, top pages, ranking keywords and keyword research as workflow steps, on one API token. The Moz API meters in rows, so this guide covers what each node spends before it covers anything else.

The Mattering Automations Moz integration puts Moz's current unified API on your automation canvas: Domain Authority, Page Authority, Spam Score and link counts, Brand Authority, backlinks and anchor texts, linking domains including the ones you recently gained and lost, top pages, link status checks, link intersects, ranking keywords, and the full keyword research set of volume, difficulty, organic CTR, priority, search intent and related keywords.

Read this part before you build anything. The Moz API is PAID and METERED IN ROWS, and the metering is the reason this integration is shaped the way it is. Moz's own definition is that one row typically corresponds to one object in the response for methods that return multiple objects, or one field in the response for methods that return a single flat object or report. On a list node that means the page size IS the price: Moz: List Links with a limit of 25 costs 25 rows, and Moz: List Ranking Keywords permits a page size of 500. Every node in the palette repeats its own cost in its description, four nodes are free, and the connection test is free by design.

The credential is a single Moz API token, created in the Moz API dashboard and sent as the x-moz-token header on every request to api.moz.com/jsonrpc. There is no OAuth flow to complete for this API, no signing, and no second field. Setup takes a few minutes, and this guide walks through each step, shows a verify path that spends nothing, and ends with the full node reference.

Before you start

  • A Moz API subscription. This is separate from Moz Pro and from Moz Local, which is the single most common surprise here: a Moz Pro seat does not carry API access. Moz sells the API on a tiered model measured in monthly rows, with pay-as-you-go overages on some tiers, and its own pricing page is the place to read the current tiers.
  • Optionally, the free tier, if all you want to do is prove the wiring. Moz documents a free tier offering 50 rows of data per month, requiring a valid non-expired credit card to sign up, with no charge unless you choose to upgrade, and Moz's help documentation adds a throttle of one request every ten seconds on it. Fifty rows will run the connection test and a few single-row calls. It will not run a report: one Moz: List Links call at the default page size spends half of the month.
  • Permission to create a token in the Moz API dashboard. An account can hold up to five active tokens at once, and deleting a token immediately breaks anything still using it, so create one specifically for automation rather than reusing a developer's.
  • A plan for spend before you schedule anything that loops. Row cost is per node and is stated on every node, and Moz: Fetch Link Intersects is the one to look at twice, because it charges rows equal to the number of targets for every result returned.
  • A Moz Local subscription, but only if you intend to reach Moz Local methods through Moz: Custom API Method. No typed node in this integration touches Moz Local, and none of the 31 nodes is one of Moz's beta methods, so the separate beta allowance and its Starter Medium plan requirement do not apply here.
  • A Mattering workspace with access to the Automations app.

Create a Moz API token

Mattering authenticates to Moz with a single API token, sent as the x-moz-token header. There are no scopes to compose, no secret key to pair it with, and no signature to compute: Moz's current API dropped the HMAC signing that its archived first-generation Links API used, and one token now covers the whole surface. Decide first which account the token should belong to, because the token is what selects the subscription and the row allowance the automation will spend.

Sign in to Moz and open the Moz API dashboard.
Click Add Token, name it for the automation that will use it, and copy the value.
An account can hold at most five active tokens, and deleting one takes effect immediately: anything still using that token starts failing at the next call. Give automation its own token so that rotating a developer's key never takes a scheduled workflow down with it.
You do not need an Access ID, a secret key, or a signature. Those belong to Moz's archived first-generation Links API. The current API reads one token from the x-moz-token header, and the same token also works against Moz's legacy hosts.

Connect Moz to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Moz from the list.
Click Create new credential, paste the API token, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs. Moz's own documentation notes that a successful response can echo the original request, so the connector also scrubs the live token and any api key id value out of node output before it reaches an execution record.
Click Test Connection. Mattering posts Moz's quota lookup method, which Moz documents as requiring no quota, so testing a credential costs you nothing. A pass proves the host, the POST verb, the header name, that the token is valid and that the account holds a Data API subscription, and the success message reports the remaining row allowance.
A passing test does not prove that a paid method will succeed. A token whose monthly rows are already exhausted still passes this probe, and then returns an authorization error on the first real call. Read the allowance in the success message rather than treating a green tick as headroom.
Click Connect. All 31 Moz nodes appear in your canvas palette.

Verify it works

Verify with the free nodes first, because on this API a verify path that spends rows is a bad habit to teach. Open any automation canvas, drop Moz: Fetch Quota onto it and run a test step. It takes one quota path and no target, it costs nothing, and it returns how many rows the account has, how many it has used, when the period resets, and whether overages are enabled. Those two numbers, used and allotted, are the ones every subsequent workflow should gate on.

Then run Moz: Fetch Current Index ID, also free. It returns an opaque id that changes only when Moz refreshes its link index, which makes it both a proof that the connection reaches real data and the cheapest possible trigger for an expensive link report. Store the value somewhere you can compare it later.

Only now spend a row. Drop Moz: Fetch Site Metrics onto the canvas, point it at a domain you own with the scope set to the whole domain, and run the step. One row buys Domain Authority, Page Authority, Spam Score, crawl status and the full link-count matrix, and it proves that the metered half of the connector works. Re-running Moz: Fetch Quota afterwards should show the used figure moved by exactly one, which is the clearest possible confirmation that you understand what these nodes charge.

Node reference

31 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 30

Moz: Count Ranking Keywords

moz_ranking_keyword_count

How many top-50 keywords a target ranks for, as a single total plus a breakdown by each rank from 1 to 50. The cheap way to size a competitor's organic footprint before deciding whether to spend rows listing it. SPENDS QUOTA: uses 1 row per call, whatever the totals turn out to be.

Moz: Fetch Brand Authority

moz_brand_authority_fetch

Brand Authority score for a domain: Moz's measure of how strong a brand's presence is in search, as distinct from how many links point at it. Useful for competitor benchmarking and for tracking PR impact. SPENDS QUOTA: uses one row per call.

Moz: Fetch Current Index ID

moz_index_metadata_fetch

An opaque id that changes whenever Moz's link index is refreshed. Store it and compare: when it moves, the link data underneath every other node in this connector has changed, which is the cue to re-run a link-building report rather than polling one on a fixed schedule. FREE: does not require any quota.

Moz: Fetch Keyword Difficulty

moz_keyword_difficulty_fetch

Keyword Difficulty for one keyword: how hard the top of that SERP is to break into. Use Fetch Keyword Metrics instead if you also want volume or CTR. SPENDS QUOTA: uses one row per call, so a loop over a keyword list costs one row per keyword.

Moz: Fetch Keyword Metrics

moz_keyword_metrics_fetch

All four keyword metrics at once for one keyword: monthly volume, difficulty, organic CTR and priority. Cheaper than four separate calls when you want more than one of them. SPENDS QUOTA PER VALUE: one row per returned value up to a maximum of four, with nulls not charged, so a keyword Moz has full data for costs 4 rows.

Moz: Fetch Keyword Organic CTR

moz_keyword_opportunity_fetch

Organic CTR (Moz calls this Opportunity) for one keyword: how much of that SERP's traffic the organic results actually get, once ads and SERP features have taken their share. SPENDS QUOTA: uses one row per call.

Moz: Fetch Keyword Priority

moz_keyword_priority_fetch

Priority for one keyword: Moz's blend of volume, difficulty and organic CTR into a single go-after-this score. SPENDS QUOTA: uses one row per call.

Moz: Fetch Keyword Search Intent

moz_keyword_search_intent_fetch

Why someone searches a keyword: the primary intent labels plus a scored breakdown across informational, navigational, commercial and transactional. Feeds content briefs and page type decisions. Accepts a narrower set of locales, devices and engines than the other keyword methods. SPENDS QUOTA: uses one row per successful call.

Moz: Fetch Keyword Volume

moz_keyword_volume_fetch

Monthly search volume for one keyword. SPENDS QUOTA: uses one row per call, so a loop over a keyword list costs one row per keyword.

Moz: Fetch Link Intersects

moz_link_intersect_fetch

Link intersect: sources linking to some targets and not others, the Venn-diagram query behind competitor link-gap analysis. Each row names the source page or domain, its Domain Authority and Spam Score, and matching_target_indexes pointing back into the Is Linking To array. THE MOST EXPENSIVE NODE IN THIS CONNECTOR: it uses N rows of quota per result, where N is the total number of targets across Is Linking To and Not Linking To, so 25 results against 6 targets costs 150 rows.

Moz: Fetch Multiple Site Metrics

moz_site_metrics_fetch_multiple

The same metrics as Fetch Site Metrics for a batch of targets in one call. Results come back under results_by_site with per-target failures isolated in errors_by_site, so one bad URL does not fail the batch. SPENDS QUOTA PER ROW: uses one row per returned result, so the cost is the size of the array.

Moz: Fetch Quota

moz_quota_lookup

How much row quota the account has, has used, and when the period resets, plus whether overages are enabled. Put this in front of an expensive branch and gate on data.result.quota.used against data.result.quota.allotted. FREE: does not require any quota, which is what makes it the right auth probe as well.

Moz: Fetch Site Metric Histories

moz_site_metrics_histories_fetch

Historical series for chosen metrics on one target, as daily or monthly absolute values or as period-over-period deltas. Each requested metric comes back as a metric_name plus a metric_values array of {date, value} points. At least one of the four metric-list fields must be filled. There is no date range to ask for: Moz returns the history it holds, so this node cannot be windowed (see the incremental note at the foot of moz_endpoints.py). SPENDS QUOTA PER METRIC: one row for every metric named across the four lists.

Moz: Fetch Site Metrics

moz_site_metrics_fetch

Domain Authority, Page Authority, Brand-safe Spam Score, crawl status and the full link-count matrix (pages and root domains linking to the page, subdomain and root domain, split by followed, nofollow, redirect and deleted) for ONE target. The workhorse node. SPENDS QUOTA: uses one row per call.

Moz: Fetch Site Metrics Distributions

moz_site_metrics_distributions_fetch

Link-profile histograms for a target: how the links pointing at it are spread across the source's linking root domain count, Domain Authority and Spam Score. Every distribution is a ten-element array of counts, ordered lowest bucket first, named METRIC_BY_MEASURE. Sources with no Spam Score are excluded from the spam buckets. SPENDS QUOTA: uses one row per successful call.

Moz: Filter Links by Anchor Text

moz_link_filter_anchor_text

Backlinks to a target whose anchor text matches one exact string, or whose anchor text is empty when the field is left blank. Use it to audit over-optimized anchors or to find the links behind a brand mention. SPENDS QUOTA PER ROW: uses one row per returned result.

Moz: Filter Links by Domain

moz_link_filter_domain

Every link from ONE source root domain to a target, sorted by descending source page authority (this method allows no other sort). The node for answering does site A still link to us, and from which pages. SPENDS QUOTA PER ROW: uses one row per returned result.

Moz: Get Final Redirect Target

moz_redirect_fetch

Where a URL finally lands after Moz follows the redirects it knows about. The audit node for a domain migration or a bulk page move: it answers whether the redirect Moz's index believes in is the one you built. NOT a live fetch: it reports the index's view, which lags the web. SPENDS QUOTA: uses one row per call.

Moz: Get Link Status

moz_link_status_fetch

Does a link from this source to this target exist in Moz's index? Returns a single boolean alongside both parsed queries. The node for verifying that a placed link is still live. SPENDS QUOTA: uses one row per call.

Moz: Get Multiple Link Status

moz_link_status_fetch_multiple

Batch link-existence check: many source-to-target pairs in one call, answered under results_by_query with failures isolated in errors_by_query. The node a link-building campaign monitor loops over. SPENDS QUOTA PER ROW: uses one row per returned result, so the cost is the size of the array.

Moz: Get Top Ranking Domains

moz_global_top_domain_list

The highest-authority root domains on the web, globally, each with the full site-metrics object. Reference data for calibrating what a Domain Authority number means. FREE: does not require any quota.

Moz: Get Top Ranking Pages

moz_global_top_page_list

The highest-authority individual pages on the web, globally, each with the full site-metrics object. Reference data for calibrating Page Authority. FREE: does not require any quota.

Moz: List Anchor Texts

moz_anchor_text_list

The anchor texts people use when linking to a target, each with the number of external root domains and external pages using it. Good for brand-mention clustering and for spotting anchor-text over-optimization. SPENDS QUOTA PER ROW: uses one row per returned result.

Moz: List Linking Domains

moz_linking_domain_list

Root domains linking to a target, one row per source domain rather than per link, each with the source's full site metrics plus how many of its pages target you and how many of those are nofollow, redirect or deleted. The node for referring-domain counts and outreach prospecting. SPENDS QUOTA PER ROW: uses one row per returned result.

Moz: List Links

moz_link_list

Backlinks pointing at a target, one row per linking page, each carrying the full site-metrics object for BOTH the source and the target plus the anchor text, first and last seen dates, and the nofollow / redirect / rel-canonical flags. The core link-research node. SPENDS QUOTA PER ROW: uses one row per returned result, so Limit is the price of the call.

Moz: List Ranking Keywords

moz_ranking_keyword_list

Keywords a domain, subdomain, subfolder or page ranks for in Google's top 50, with the ranking URL, the position, the keyword difficulty and the monthly volume. The competitor research node. SPENDS QUOTA PER ROW: uses one row per returned result, and this method allows a page size of up to 500.

Moz: List Recently Gained Linking Domains

moz_linking_domain_recently_gained

Root domains that started linking to a target in the last 60 days, each with the day it happened (date_gained) and the source's full site metrics. Optionally narrow to a date range inside that window. The node behind a link-acquisition report. SPENDS QUOTA PER ROW: uses one row per returned result.

Moz: List Recently Lost Linking Domains

moz_linking_domain_recently_lost

Root domains that stopped linking to a target in the last 60 days, each with the day the link disappeared (date_lost) and the source's full site metrics. The node behind a link-decay alert. SPENDS QUOTA PER ROW: uses one row per returned result.

Moz: List Related Keywords

moz_keyword_suggestions_list

Related keyword suggestions for a seed keyword, each with a relevance score. The ideation node for content briefs and cluster building. SPENDS QUOTA PER ROW: uses one row per returned result, so asking for 50 suggestions costs 50 rows.

Moz: List Top Pages

moz_top_page_list

The strongest pages on a domain or subdomain, ranked by Page Authority, linking root domains or external linking pages, each row carrying the full site-metrics object. Filter to a 4xx status to find dead pages that still hold authority. SPENDS QUOTA PER ROW: uses one row per returned result.

Action nodes 1

Moz: Custom API Method

moz_request

Call ANY Moz JSON-RPC method by name, for the methods this connector does not ship a typed node for: the whole Moz Local surface (locations, listings, networks, Google Business Profile insights, local grid rankings, accounts and groups) and any method Moz adds after this catalog was built. Moz Local methods need a Moz Local subscription as well as a Data API one. SPENDS QUOTA UNPREDICTABLY: the cost is whatever the named method costs, and some Local methods WRITE. local.location.cancel and local.location.close end a paid listing. Read the method's own documentation before running it.

Using the integration

On the automation canvas

Moz nodes chain with every other node in the palette. A schedule can drive Moz: Fetch Multiple Site Metrics over a client list into a Mattering database, a condition can compare this week's Domain Authority against last week's and open a task only when it moves, and Moz: List Recently Lost Linking Domains can route a lost high-authority link straight to an owner. The paging pattern is worth knowing: the list nodes return a cursor at the offset token in their own response, and the next page is that same node run again with the cursor pasted into its page token field. Because every page costs rows, paging is a decision rather than a default.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter, the assistant built into the platform, can drive the same surface. A useful habit to give an agent is the same one you would give a workflow: read Moz: Fetch Quota first, because it is free, then decide. Moz also publishes MCP servers of its own, and they are worth knowing about before you choose. Moz documents two endpoints, one for Moz Data and one for Moz Local, each requiring a valid subscription to the corresponding product, authenticated with OAuth in the client or with the same API token, and both published in Claude's built-in connector directory. Moz states that the server is in beta and that access is limited to account owners today, with expansion to seated users in progress. For asking questions of Moz data in a chat window, use it. This integration is the operations side: 31 typed nodes that run unattended, chain with the rest of the fleet, hold one token in a shared workspace store rather than in each person's client config, and state their row cost where a reviewer can see it.

Row metering, in four shapes

Every node in this integration falls into exactly one of four cost shapes, and each node's description names its own. One row per call covers the single-answer nodes: Moz: Fetch Site Metrics, Moz: Fetch Brand Authority, Moz: Fetch Site Metrics Distributions, Moz: Get Link Status, Moz: Get Final Redirect Target, Moz: Count Ranking Keywords and four of the five single-keyword fetches. One row per returned result covers every list node, which is the shape to internalise, because it means the limit field is a price field: Moz: List Links, Moz: List Linking Domains, Moz: List Anchor Texts, Moz: List Top Pages, Moz: List Ranking Keywords, Moz: List Related Keywords, Moz: Filter Links by Anchor Text, Moz: Filter Links by Domain, Moz: List Recently Gained Linking Domains, Moz: List Recently Lost Linking Domains, Moz: Fetch Multiple Site Metrics and Moz: Get Multiple Link Status. One row per returned value, capped at four with nulls not charged, applies to Moz: Fetch Keyword Metrics only. And the multiplier shape belongs to Moz: Fetch Link Intersects, which charges rows equal to the number of targets for every result returned.

The four free nodes, and what they are for

Moz states that four of these methods are free of charge, and they are the ones that make the rest safe to schedule. Moz: Fetch Quota reports rows used, rows allotted, the reset date and whether overages are enabled, which is the input to any spending guard worth having. Moz: Fetch Current Index ID returns an id that moves only when Moz refreshes the link index, so polling it costs nothing and tells you whether a link report would return anything new. Moz: Get Top Ranking Domains and Moz: Get Top Ranking Pages return the highest-authority domains and pages on the web, which is reference data for calibrating what a Domain Authority number actually means. Build the free nodes into the front of every metered workflow rather than treating them as curiosities.

Reaching Moz Local and anything else this catalog skipped

Moz: Custom API Method calls any Moz method by name, which covers the whole Moz Local surface (locations, listings, networks, Google Business Profile insights, local grid rankings, accounts and groups) and anything Moz ships after this catalog was built. Two conditions come with it, and both are on the node. Moz Local is a separate product with a separate subscription, so a Data API token alone will not reach it. And this is the only node whose cost cannot be printed in advance, because the cost is whatever the named method costs, and some Local methods write rather than read: cancelling or closing a location ends a paid listing. Read the method's own Moz documentation before you run it, and gate it behind an approval if an agent can reach it.

What the connector cannot window, and why it matters

Two nodes carry a real date window and declare it, so a scheduled refresh can partition them correctly: Moz: List Recently Gained Linking Domains and Moz: List Recently Lost Linking Domains both take a begin and end date inside Moz's own 60 day horizon, and each row carries the day the link appeared or disappeared. Asking for a wider window than 60 days is not a bigger request, it is an impossible one. Moz: Fetch Site Metric Histories is the exception worth flagging before you plan a time series around it: it has no start or end field at all, Moz returns the history it holds, and the bucket width is chosen by which of the four metric list fields you fill rather than by a grain parameter. Treat it as a chart source rather than as something to roll up. On the same note, Domain Authority, Page Authority, Brand Authority, Spam Score and link propensity are SCORES rather than flows: two days of Domain Authority do not add up, and averaging them across a window is only meaningful if you know the sampling was even.

Troubleshooting

Test Connection passes but the first real node returns an authorization error
Read the message rather than the status. The connection test probes Moz's quota lookup method, which Moz documents as costing nothing, and that method answers happily on a token whose monthly rows are exhausted. The first metered call then fails with a message about the monthly row limit being reached. Run Moz: Fetch Quota on its own, which is free, and compare used against allotted. If the allowance really is spent, the fix is Moz's, not ours: wait for the reset date the same response reports, or enable overages if your tier offers them.
A report cost far more rows than expected
Almost always the limit field. Every list node in this integration bills one row per returned result, so the page size is the price: Moz: List Ranking Keywords permits a page size of 500, and a workflow that pages through a large profile pays for every page. Two other shapes catch people out. Moz: Fetch Link Intersects charges rows equal to the number of targets for every result returned, so 25 results across 6 targets is 150 rows rather than 25. And Moz: Custom API Method costs whatever the method it names costs, which cannot be printed on the node in advance. Put Moz: Fetch Quota in front of anything that loops and gate the branch on the numbers it returns.
A node returns a 400 with an error object instead of data
Moz answers a bad request with an HTTP 4xx and a structured error, and the structure is more useful than the status. The error object carries a message, an internal code, and a data section whose key field names the exact request component at fault, for example a missing query. Read that key first: it usually points at a required field left blank or at a value that is not in the accepted set for that method. Both the message and the key are available downstream, so an error branch can route on them rather than just logging the failure.
Requests start failing in bursts after a run of errors
That is Moz's throttle, and it is driven by failures rather than by volume. Moz's error handling guide documents that more than 50 requests in a five minute period that return a 4xx caps the account at 50 requests per five minutes, until 30 seconds pass without a 4xx. A workflow looping over a bad input list therefore slows itself down. Fix the input rather than the pacing: validate targets before the loop, and let an error branch stop the run instead of letting it retry into the cap. Separately, on Moz's free tier the documented rate is one request every ten seconds, which will look like the same symptom on a much smaller workflow.
The sort value I set on List Linking Domains is rejected
Moz's prose documentation and its machine-readable schema disagree on this one field, and the schema is what the API enforces. The schema's accepted sort values for Moz: List Linking Domains are the source domain authority, the source link propensity and the source spam score. The date gained and date lost values that appear in the prose are not accepted there. If what you want is a list ordered by when a link appeared or disappeared, use Moz: List Recently Gained Linking Domains or Moz: List Recently Lost Linking Domains instead, which carry that date on every row by design.
Paging returns the same rows, or a page token is not accepted
Moz pages with an opaque cursor rather than a page number, and the cursor is per node and per query. Take the token from the offset section of the SAME node's previous response and paste it into that node's page token field, leaving every other field unchanged. Changing the query, the sort or the limit between pages invalidates the sequence. Two nodes need one extra detail: Moz: List Recently Gained Linking Domains and Moz: List Recently Lost Linking Domains require both paging fields to be present, so the connector sends an explicit empty token with the limit on the first page. And remember that each page is billed, so paging deep is a spending decision.
Filter Links by Anchor Text returns links with no anchor text at all
That is the documented behaviour rather than a fault, and it is the one place in this integration where a blank field is a question rather than a missing answer. Leaving the anchor text field empty on Moz: Filter Links by Anchor Text asks Moz for links that carry no anchor text, which is a real and useful query for auditing image links. If you meant to search for a phrase, type it. The node's own help text says the same thing, because the failure mode is silent: you get results, they are simply the answer to a different question.
A Moz Local method through Custom API Method fails on entitlement
Moz Local is a separate subscription from the Data API, and one token does not imply both. If Moz: Custom API Method reaches a Moz Local method and comes back refused, check the account's Moz Local subscription before checking anything about the connector. The same node is also the only one whose blast radius is not fixed in advance: some Moz Local methods write, and cancelling or closing a location ends a paid listing. Gate it behind a condition or an approval step, especially if an AI agent can reach the palette.
Fetch Site Metric Histories will not accept a date range
It has no date range to accept, which is a property of the Moz method rather than a gap in the node. Moz returns the history it holds, with no start or end parameter anywhere on the method, and the bucket width is chosen by which of the four metric list fields you fill: daily values, monthly values, or the two delta variants. Filling more than one returns more than one series in the same response. Because there is no window, this node declares no incremental behaviour, so a scheduled consumer will correctly refuse to aggregate it. Read it as a series to chart rather than as a table to roll up.

Moz is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products