action_email_validate_mx · action · Email · Available · v1.0.0
Verify email deliverability via DNS MX lookup (RFC 5321 A record fallback included). Detect disposable domains (mailinator, tempmail, etc. — 250+ blacklist). Detect role-based vs person email (info@ vs name.surname@). Output: confidence 0-100. 5min × 5000 domain LRU cache → negligible in batch.
Fields shown in the editor when configuring the node. Generated directly from the NodeDefconfigFields.
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
emailEmail da validare | expression | yes | — {{$node.harvest.json.primary_email}} | Indirizzo email completo (local@domain). Tipicamente output di un nodo action_email_harvest (campo primary_email) o di un'estrazione manuale. |
minConfidenceConfidence minima per ok (0-100) | number | no | 70 | Threshold per il campo output `ok`. Default 70: • 100: MX valido, non-disposable, person-style • 85: MX valido, role-based • 60: MX valido, role-based (acceptable B2B) • 30: solo A fallback (deliverable ma debole) • 5: disposable (DA EVITARE) • 0: undeliverable Il flusso può usare `ok=true/false` in un logic_if subito dopo. |
timeoutMsTimeout DNS lookup (ms) | number | no | 4000 | Timeout per ciascuna query DNS (MX/A/AAAA). 4000ms = safe per il 99.9% degli upstream DNS. Aumentare a 8000 se i lookup avvengono via VPN/proxy lento. |
Fields available to downstream nodes via $node.<alias>.json.<field>:
mx_validmx_recordsdisposablerole_basedconfidencereasonokJSON snippet of the node as it appears in the workflow. Values are derived fromdefaultValue and from required parameters.
{
"id": "node-action_email_validate_mx-1",
"defId": "action_email_validate_mx",
"label": "Email: MX + disposable verify",
"config": {
"email": "{{$node.harvest.json.primary_email}}",
"minConfidence": 70,
"timeoutMs": 4000
}
}Available now on all FlowForge plans. Try it free without a credit card.
Start freeBrowse all nodes