by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by ZeroBounce
ZeroBounce Bulk Email Validation and Scoring This template uses the ZeroBounce node to validate and score email addresses. It is designed to first check if an email is deliverable and then uses A.I. Scoring to assess the sender's deliverability confidence. This is an example template to demonstrate ways to use the ZeroBounce node and how to manipulate the data with core n8n nodes. A ZeroBounce API key is needed to use this template. Generate one here. 1. Email Validation The Validate email node sends the email address to the ZeroBounce API to determine its status (e.g., 'valid', 'invalid', 'spam trap'). Function:** Checks the email address against ZeroBounce's Email Validation API 2. A.I. Scoring For emails confirmed as valid, the workflow proceeds to the Score email node. Function:* Applies ZeroBounce's proprietary A.I. model to assess the quality of the email, returning a numerical score (0 to 10*). 3. Output The workflow concludes with the Filter by score Switch Node, which uses the ZeroBounce score to categorize the email into three confidence tiers: High Score:** Indicates high confidence in deliverability and is ready for immediate campaigns. Medium Score:** Suggests moderate risk; these might be suitable for re-engagement or specialized campaigns. Low Score:** Indicates high risk, even if the status was technically valid. These should be suppressed to protect sender reputation.
by ZeroBounce
ZeroBounce Email Validation and Scoring This template uses the ZeroBounce node to validate and score email addresses. It is designed to first check if an email is deliverable and then uses A.I. Scoring to assess the sender's deliverability confidence. This is an example template to demonstrate ways to use the ZeroBounce node and how to manipulate the data with core n8n nodes. A ZeroBounce API key is needed to use this template. Generate one here. 1. Email Validation The Validate email node sends the email address to the ZeroBounce API to determine its status (e.g., 'valid', 'invalid', 'spam trap'). Function:** Checks the email address against ZeroBounce's Email Validation API 2. A.I. Scoring For emails confirmed as valid, the workflow proceeds to the Score email node. Function:* Applies ZeroBounce's proprietary A.I. model to assess the quality of the email, returning a numerical score (0 to 10*). 3. Output The workflow concludes with the Filter by score Switch Node, which uses the ZeroBounce score to categorize the email into three confidence tiers: High Score:** Indicates high confidence in deliverability and is ready for immediate campaigns. Medium Score:** Suggests moderate risk; these might be suitable for re-engagement or specialized campaigns. Low Score:** Indicates high risk, even if the status was technically valid. These should be suppressed to protect sender reputation.
by System Admin
Tagged with: , , , ,
by Kai S. Huxmann
How to secure GET Webhooks? What are webhooks? Webhooks are special URLs that instantly trigger workflows when they receive an incoming HTTP request (like GET or POST). They're perfect for connecting external tools to n8n in real time. 🔐 Why webhooks should be protected Unprotected webhooks are publicly accessible on the internet — anyone with the link can trigger your workflow. This can lead to spam, unwanted requests, or even data loss. ✅ Best Practice: Use built-in Authentication n8n provides native authentication options for webhook nodes: Basic Auth Header Auth JWT Auth These methods are highly recommended if supported by your external app or service. You can find them in the “Authentication” dropdown of the webhook node. 🛠️ When to use THIS SETUP Sometimes, external tools don’t support custom headers or advanced auth methods — for example: A button click in Google Sheets A link shared via email or chat with a trusted partner IoT devices or basic web apps In those cases, you can protect a webhook by adding a secret query parameter (e.g. ?secret=abc123xyz456...) and validating it with an IF node at the start of your workflow. This way, only those requests with the secret can trigger the core elements of your workflow. It's a simple yet powerful way to secure GET-based workflows. Only use if better methods aren't available.