Package Information
Available Nodes
Documentation generating…
Documentation
n8n-nodes-oopspam
This is an n8n community node. It lets you use oopspam in your n8n workflows.
oopspam is a privacy-first spam and fraud protection API. It scores messages, comments and form submissions and returns a spam score together with a detailed report, so you can decide how strict your filtering should be.
n8n is a fair-code licensed workflow automation platform.
Installation
Follow the installation guide in the n8n community nodes documentation.
Operations
- Check for Spam: send a message, an email address, an IP address or any combination of them to oopspam and receive a spam
Score(0-6) with a detailed report. - Check Domain Reputation: check whether a domain is listed by reputation blocklists.
- Report Misdetection: report a false positive or false negative back to oopspam so detection improves for your use case.
Scoring
The Score returned by oopspam ranges from 0 to 6. A score of 3 or higher is considered spam.
Credentials
You need an oopspam API key.
- Sign up or log in to the oopspam Dashboard.
- Open your dashboard and copy the API key.
- In n8n, create a new Oopspam API credential and paste the key into the API Key field.
The credential sends the key in the X-Api-Key header, as described in the oopspam authentication documentation.
If you subscribed to oopspam through RapidAPI, note that the RapidAPI endpoint uses a different base URL and a different authentication header. This node talks to the oopspam Dashboard endpoint (https://api.oopspam.com/v1).
Compatibility
Requires n8n 1.0.0 or later.
Usage
Check a form submission for spam
- Add the oopspam node and select the Check for Spam operation.
- Fill in the sender details you have. You can send any combination of them:
- Content: the message, comment or form submission, for example
{{ $json.message }}. - Email: the sender's email address, for example
{{ $json.email }}. - Sender IP: the sender's IP address, for example
{{ $json.ip }}.
- Content: the message, comment or form submission, for example
- Optionally open Additional Fields and add:
- Block Temporary Emails, Block VPN, Proxy and Tor or Block Data Center IPs to tighten the filtering.
- Allowed Countries, Blocked Countries or Allowed Languages to restrict submissions to specific countries or languages.
- Content Context to describe your website and what you consider spam. Setting it switches the request to contextual detection only.
- Log to Dashboard together with Source to keep a log of the requests in the oopspam Dashboard.
- Add an If node after it and continue the workflow only when
{{ $json.Score }}is lower than3.
Example response:
{
"Score": 6,
"Details": {
"isIPBlocked": true,
"isEmailBlocked": true,
"isContentSpam": "spam",
"langMatch": true,
"countryMatch": false,
"numberOfSpamWords": 1,
"spamWords": ["dear"],
"isContentTooShort": false,
"isItVPN": true,
"isItDataCenter": false
}
}
The node returns the API response unchanged, so Details may contain the following keys:
| Key | Meaning |
|---|---|
isIPBlocked |
The sender IP is on an IP denylist |
isEmailBlocked |
The email address is on an email denylist |
isContentSpam |
Machine learning verdict on the content (spam or nospam) |
langMatch |
The detected language matches allowedLanguages |
countryMatch |
The country of the sender IP matches allowedCountries/blockedCountries |
numberOfSpamWords / spamWords |
Number and list of spam words found in the content |
isContentTooShort |
The content is shorter than 20 characters |
isItVPN |
The sender IP belongs to a VPN/proxy network |
isItDataCenter |
The sender IP belongs to a hosting/data center network |
All keys are optional: oopspam returns a result as soon as one check detects spam, so only the fields relevant to that request are present. isItVPN and isItDataCenter are informational — they explain why an IP was flagged, and are only returned when the IP was flagged. They don't cause the block themselves.
Country codes and language codes are passed as a comma-separated list, for example us, it or en, de.