Block 1 - Form signup for Wordpress in KlickTipp form
- Type / Role
- n8n-nodes-klicktipp.klicktippTrigger - klicktippTrigger
- Config choices
- Version 1
Community Node Disclaimer This workflow uses KlickTipp community nodes , available for self hosted n8n instances only . Who’s it for Marketing teams and cou...
n8n-nodes-klicktipp.klicktipptrigger, n8n-nodes-base.set, n8n-nodes-klicktipp.klicktipp, n8n-nodes-base.httprequest, n8n-nodes-base.switch, n8n-nodes-base.stickynote, n8n-nodes-base.filter, n8n-nodes-base.scheduletrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by KlickTipp.
Original n8n.io sourceThis workflow uses KlickTipp community nodes, available for self-hosted n8n instances only.
Marketing teams and course/community operators using WordPress and KlickTipp who want to automate the full bridge between lead capture and member engagement:
This workflow removes manual user creation, keeps your marketing database enriched with behavioral data, and enables highly targeted follow-up campaigns.
This workflow connects KlickTipp ↔ WordPress in two directions: (1) Signup → Account creation, and (2) Comments → Profile enrichment + tagging.
Triggered by the Form signup for Wordpress in KlickTipp form webhook (RAW form submission):
field229493 equals "I give consent".temporary_password.subscriber) using the generated username, password, and contact profile data.field229462 → WordPress User ID field228982 → WordPress Username field228983 → Temporary PasswordThis enables automated onboarding emails that include login credentials (if you choose to send them).
Triggered daily by Pull comments trigger (scheduled at 08:00):
after = now - 24h query parameter).field229468 → last comment textAfter the comment is stored, Check relevant segment evaluates the link (where the comment was posted) and applies tags accordingly:
1416290514176702This gives you interest-based tagging driven by real engagement, not just form submissions.
field229493 with the value "I give consent".field229462field228982field228983field229468https://cht.klicktipptest.de/...).subscriber to other roles where appropriate.after parameter in Get last comments from Wordpress (e.g., last 6 hours, last 7 days).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.
Showing the first 24 of 27 workflow blocks. Download the JSON for the full node graph.
| Workflow | Create WordPress users from KlickTipp and tag contacts based on comments |
|---|---|
| Complexity | advanced |
| Nodes | 27 |
| Categories | Lead Generation |
| Author | KlickTipp |
| Published | 26 Feb 2026 |
Use the JSON export at /data/workflows/13721/13721.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
Community Node Disclaimer This workflow uses KlickTipp community nodes , available for self hosted n8n instances only . Who’s it for Marketing teams and cou...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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 Lead Generation use case.