Check my backlinks from a Zap: the five-step version
New row in, rating out, Slack message only when the site is worth a call. Every step uses built-in Zapier apps, so no code and no extra connector.
Deeplinkify research team ·
What this Zap does
A lead's website gets scored the moment the lead arrives
The trigger is a new row in Google Sheets, HubSpot or whatever collects your leads. One free call returns an overview of the site, a filter drops weak ones and Slack gets the rest.
Five steps: trigger, Webhooks GET, Filter, Formatter (optional), Slack.
Cost on our side: zero credits, the overview action is free.
Cost on Zapier's side: every action step counts as a task on your plan.
Build it
1
Trigger: New Spreadsheet Row
Pick Google Sheets and the tab where leads land. Make sure one column holds the bare domain, with no https:// in front.
2
Action: Webhooks by Zapier, GET
URL https://deeplinkify.com/api.php. Under Query String Params add action = overview and q = the domain column. Add a header Authorization = Bearer sk_live_....
3
Action: Filter
Continue only if the rating field from step 2 is greater than your threshold. Zapier shows the response keys after a test run, so pick the rating from that list.
4
Action: Formatter, Text (optional)
Trim and lower-case the domain if your lead form is messy. Do this before step 2, not after, or the lookup will miss.
5
Action: Slack, Send Channel Message
Post the domain, the rating and a link to the lead. Short is better; nobody reads a wall of JSON in a channel.
Choosing the threshold
Pick a number, then test it.
Sort, then eyeball. Run the Zap on twenty past leads, write the ratings in a column and sort them. Where your good customers cluster is your cut-off; a rating is a rough size signal on a log scale, so a jump from 20 to 30 is a bigger step than from 60 to 70. Our DR is our own metric and does not match Ahrefs DR or Moz DA, so do not reuse a threshold from another tool.
Revisit it each quarter. The Sheets script is a handy way to re-score the old leads in bulk.
What Webhooks by Zapier sends
The same request in curl, so you can reproduce a failed step outside Zapier.
bash
curl -H "Authorization: Bearer sk_live_..." \
"https://deeplinkify.com/api.php?action=overview&q=example.com"
# Expected: HTTP 200 and JSON with "ok": true
# Free actions return no _credits block; paid ones do.
Task counts, not credits, are the bill to watch
This Zap spends no credits at all. The meter that moves is Zapier's.
Zapier counts each successful action step as a task, and a filtered-out run still uses the steps before the filter. So five steps on 300 leads a month is a different number from five steps on 3,000, and the plan you are on decides whether that matters.
If volume is the issue, collect leads into a sheet and score them in one bulk_dr call from a single Zap run: one webhook step, up to 2,000 domains, and nothing more. The outreach list recipe shows the body to send.
Paid actions inside a Zap
If you swap overview for refdomains (2 credits) the Zap becomes a spender. Put a Filter before it so only qualified leads reach it, and keep an eye on _credits in the response, as described in what $100 buys.