IPQualityScore

Screen risk before it enters your funnel. Agents score IP addresses for proxy, VPN, Tor, and bot activity, validate email deliverability and reputation, verify phone numbers, and scan URLs for malware and phishing through IPQualityScore's fraud scoring API.

4 actions API key available

IPQualityScore website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A checkout completes and a payment intent sits awaiting confirmation in Stripe

Check IP Address scores the buyer's connection for proxy, VPN, Tor, and bot activity, with geolocation and abuse history attached

Validate Email confirms the address is deliverable and flags disposable, catch-all, and honeypot patterns

Validate Phone confirms the number is active and reports line type, carrier, and country

The agent merges the three verdicts: clean signals pass through untouched, fraud scores of 85 and above hold the order, and the suspicious band in between goes to review

The fraud reviewer reads the held orders with the full evidence, the score, the connection metadata, the mismatches, and approves or declines each one

Every lookup and every decision appends to the reputation log, so the thresholds can be tuned against outcomes instead of instinct

What This Integration Enables

A fraud score is a probability, not a verdict, and the teams that get value from IPQualityScore are the ones whose workflows respect the difference. The platform returns a 0 to 100 score for any IP address, email, phone number, or URL, with the metadata to explain it: proxy and VPN detection, mailbox deliverability, line type and carrier, phishing and malware flags. What it does not decide is what your business should do at 78. FlowRunner is where that policy lives. - Score the visitor behind every login, signup, and payment for proxy, VPN, Tor, and bot activity before granting anything - Reject disposable and undeliverable email addresses at signup instead of discovering them at send time - Detect VoIP and burner phone numbers before they become verified accounts - Scan user-submitted URLs for phishing and malware before anyone downstream clicks them - Tune per-lookup strictness deliberately, and route the ambiguous band to [human-in-the-loop](/concepts/human-in-the-loop) review instead of guessing

Without FlowRunner

Fraud discovered by chargeback The first signal that an order was fraudulent arrives from the card network, weeks late and with a fee attached

Binary blocking A rules engine either lets a signup through or rejects it, and the rejected legitimate customers never tell you

Screening only at checkout Signups, logins, and user-submitted links flow in unscored because each check would need its own build

With FlowRunner

Risk scored at the door IP, email, phone, and URL reputation arrive as structured scores inside the workflow, before money or access moves

An ambiguous band with a human in it High-risk holds automatically; the gray zone gets judged by a person with the evidence in front of them

One gate, every funnel The same scoring steps sit in front of checkout, signup, account recovery, and inbound links

Use Case Scenarios

The signup gate that keeps the list honest

New responses arrive from a [Typeform](/integrations/typeform) signup form. For each one, the agent runs Validate Email and Validate Phone. Deliverable addresses with real mobile numbers flow straight into the CRM and the mailing list. Disposable domains and honeypot addresses are dropped with a logged reason. The middle cases, a catch-all domain with a VoIP number, say, post to [Slack](/integrations/slack) where a person decides whether this is a privacy-conscious customer or a fake account, before the welcome sequence fires.

The payment screen that holds instead of guessing

Before an order is fulfilled, the agent calls Check IP Address on the buyer's connection. A clean residential score passes. A fraud score of 85 or higher, or an active Tor exit flag, holds the order and alerts the team with the geolocation, ISP, and abuse history attached; if the reviewer declines it, the refund is issued in [Stripe](/integrations/stripe) before shipping costs stack on top of the loss. Scores in the suspicious band hold for review rather than auto-declining, because a VPN is not a crime and regular customers use them.

The link scanner in front of the community

Users submit links: support tickets, community posts, partner form fields. The agent runs Scan URL on each before the link is rendered anywhere a colleague or customer might click it. Unsafe flags and high risk scores quarantine the submission and notify the moderator with the phishing, malware, and domain-age evidence. Every scan result also appends to [Google Sheets](/integrations/google-sheets), building a reputation history the security review can actually audit.

Human-in-Loop Highlight

The costly operation here is not the lookup, it is what the lookup authorizes. Acting on Check IP Address means declining a payment or blocking a signup, and a false positive is invisible revenue loss: the legitimate customer behind a VPN does not file a ticket, they just buy elsewhere. IPQualityScore's own scale marks 75 to 84 as suspicious rather than high risk, and FlowRunner treats that band as exactly what it is, a question. Agents auto-pass the clean, auto-hold the 85-plus, and hand the suspicious band to a reviewer with the whole evidence file: score, proxy flags, ISP, geolocation against billing address, email and phone corroboration. Raising strictness to catch more fraud widens that gray zone, which is precisely why the judgment call in it belongs to a person.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

4 actions

Network and Device Risk

Check IP Address Analyzes an IP address for fraud risk, proxy, VPN, Tor, and bot activity. Returns a fraud_score from 0 to 100, where 75 and above reads as suspicious and 85 and above as high risk, plus connection metadata, geolocation, ISP, and abuse history. The gate in front of risky logins, payments, and signups. Higher strictness increases detection at the cost of more false positives.

Contact Verification

Validate Email Validates an email address and scores its reputation. Confirms syntax and mailbox deliverability, and flags disposable, temporary, catch-all, honeypot, and abusive addresses, with a fraud_score, deliverability rating, and domain and SMTP details. The difference between a mailing list and a bounce generator.
Validate Phone Validates a phone number and scores its reputation. Confirms the number is valid and active, and returns line type across mobile, landline, VoIP, and toll-free, plus carrier, country, timezone, and a fraud_score. Provide the country for the most accurate parsing of local-format numbers.

Link Safety

Scan URL Scans a URL or domain for malware, phishing, and reputation risk. Returns an unsafe flag, a risk_score from 0 to 100, and boolean indicators for phishing, malware, spam, suspicious content, and parked or adult domains, plus domain age, category, server, and DNS details. The check that runs before anyone clicks.

Frequently Asked Questions

What can FlowRunner do with IPQualityScore?

FlowRunner agents can run Check IP Address, Validate Email, and Validate Phone in IPQualityScore, plus 1 more action.

Does connecting IPQualityScore to FlowRunner require OAuth?

No. IPQualityScore connects to FlowRunner with an API key, no OAuth flow required.

Can IPQualityScore trigger a FlowRunner workflow automatically?

IPQualityScore doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with IPQualityScore

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us