Skip to main content

Filter spam from webhook form submissions using honeypot and timing checks

Workflow preview

Workflow preview
100%
Filter spam from webhook form submissions using honeypot and timing checks preview
Open on n8n.io

1. Workflow Overview

Who is this for? Website owners, agencies, or developers who receive contact form submissions via webhook and want to block bots and spam without CAPTCHAs, keeping the user experience clean and fri...

Best for

  • Ticket Management automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.webhook, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.respondtowebhook

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Florian Eiche.

Original n8n.io source

1.1 Workflow description

Title
Filter spam from webhook form submissions using honeypot and timing checks
Workflow name
Filter spam from webhook form submissions using honeypot and timing checks

Who is this for?

Website owners, agencies, or developers who receive contact form submissions via webhook and want to block bots and spam without CAPTCHAs, keeping the user experience clean and friction-free.

How it works

Your frontend sends a POST request with form data, a hidden honeypot field, and a client-side timestamp The workflow runs three automated spam checks: Honeypot detection: A hidden form field that real users never see, if it contains data, it's a bot Timing analysis: If the form was submitted in under 2 seconds after page load, it's a bot Disposable email detection: Checks the email domain against a configurable blocklist of known throwaway providers (mailinator, yopmail, guerrillamail, etc.) Spam: Returns a silent 200 OK with a generic thank-you message, the bot thinks it worked, but nothing is forwarded Legitimate: Returns 200 OK with the cleaned form data, ready for downstream processing (email, Slack, CRM)

Setup

Activate the workflow Add the honeypot field and timestamp to your frontend form (see the Step 1 sticky note for a copy-paste HTML snippet) Optionally adjust spam rules in the Configure Spam Rules node (field names, timing threshold, blocked domains)

How to customize

Add your own disposable email domains to the blocklist in the Set node Adjust the minimum submission time threshold (default: 2 seconds) Connect your own nodes after the IF node on the legit branch to forward real submissions to email, Slack, a CRM, or a database

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Receive Form Submission

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 2.1

Block 7 - Configure Spam Rules

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 8 - Detect Spam

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 9 - Is Spam?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 10 - Silent OK (Spam Blocked)

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1.5

Block 11 - Forward & Respond (Legit)

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1.5

Block 12 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Filter spam from webhook form submissions using honeypot and timing checks
Complexity intermediate
Nodes 12
Categories Ticket Management
Author Florian Eiche
Published 13 Mar 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/14028/14028.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Filter spam from webhook form submissions using honeypot and timing checks do?

Who is this for? Website owners, agencies, or developers who receive contact form submissions via webhook and want to block bots and spam without CAPTCHAs, keeping the user experience clean and fri...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management use case.