Back to Catalog

AI-powered contact management in KlickTipp with MCP server

KlickTippKlickTipp
325 views
2/3/2026
Official Page

Screenshot 20250711 at 14.28.47.png

Community Node Disclaimer: This workflow uses KlickTipp community nodes.

How It Works

This workflow connects an MCP Server with the KlickTipp contact management platform and integrates it with an LLM (e.g. Claude etc.) to enable intelligent querying and segmentation of contact data. It covers all major KlickTipp API endpoints, providing a comprehensive toolkit for automated contact handling and campaign targeting.

Key Features

MCP Server Trigger:

  • Initiates the workflow via the MCP server, listening for incoming requests related to contact queries or segmentation actions.

LLM Interaction Setup:

  • Interacts with an OpenAI or Claude model to handle natural language queries such as contact lookups, tagging, and segmentation tasks.

KlickTipp Integration: Complete set of KlickTipp API endpoints included:

  • Contact Management: Add, update, get, list, delete, and unsubscribe contacts.
  • Contact Tagging: Tag, untag, list tagged contacts.
  • Tag Operations: Create, get, update, delete, list tags.
  • Opt-In Processes: List and retrieve opt-in process details.
  • Data Fields: List and get custom data fields.
  • Redirects: Retrieve redirect URLs.

Use Cases Supported:

  • Query contact information via email or name.
  • Identify and segment contacts by city, region, or behavior.
  • Create or update contacts from the provided data.
  • Dynamically apply or remove tags to initiate campaigns.
  • Automate targeted outreach based on contact attributes.

Setup Instructions

Install and Configure Nodes:

  • Set up MCP Server.
  • Configure the LLM connection (e.g., Claude Desktop configuration).
  • Add and authenticate all KlickTipp nodes using valid API credentials.

Define Tagging and Field Mapping:

  • Identify which fields and tags are relevant to your use cases.
  • Ensure necessary tags and custom fields are already created in KlickTipp.

Workflow Logic:

  1. Trigger via MCP Server: A prompt or webhook call activates the server listener.
  2. Query Handling via LLM Agent: AI interprets the natural language input and determines the action.
  3. Contact Search & Segmentation: Searches contacts using identifiers (email, address) or criteria.
  4. Data Operations: Retrieves, updates, or manages contact and tag data based on interpreted command.
  5. Campaign Preparation: Applies tags or sends campaign triggers depending on query results.

Benefits:

  • AI-Powered Automation: Reduces manual contact search and tagging efforts through intelligent processing.
  • Scalable Integration: Built-in support for full range of KlickTipp operations allows diverse use-case handling.
  • Data Consistency: Ensures structured data flows between MCP, AI, and KlickTipp, minimizing errors.

Testing and Deployment: Use defined prompts such as:

  • “Tell me something about the contact with email address X”
  • “Tag all contacts from region Y”
  • “Send campaign Z to customers in area A” Validate expected actions in KlickTipp after prompt execution.

Notes:

  • Customization: Adjust tag logic, AI prompts, and contact field mappings based on project needs.
  • Extensibility: The template can be expanded with further logic for Google Sheets input or campaign feedback loops

Resources:

AI-Powered Contact Management in KlickTipp with MCP Server

This n8n workflow demonstrates a foundational setup for AI-powered interactions using the Model Context Protocol (MCP) server, specifically highlighting the integration of a custom "Code Tool" within an AI agent's capabilities. While the provided JSON is a minimal example, it lays the groundwork for advanced contact management in platforms like KlickTipp by enabling an AI to execute custom logic.

What it does

This workflow serves as a template for building AI agents that can perform custom actions. Specifically, it:

  1. Listens for AI Agent Requests: The MCP Server Trigger node acts as an entry point, waiting for requests from an AI agent that supports the Model Context Protocol. This trigger initiates the workflow when the AI agent decides to use one of its registered tools.
  2. Provides a Custom Code Tool: The Code Tool node defines a custom function or action that the AI agent can invoke. In a real-world scenario, this tool would contain JavaScript code to interact with external services (e.g., KlickTipp API to add a contact, update a tag, or send an email), perform data manipulation, or execute complex business logic.
  3. Illustrates AI Tooling: The presence of both the MCP Server Trigger and Code Tool signifies an architecture where an AI agent can dynamically decide to execute custom code based on its understanding of a user's request.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n (self-hosted or cloud).
  • Model Context Protocol (MCP) Server: An AI agent or service configured to communicate via the Model Context Protocol, capable of invoking tools registered with an MCP server.
  • Understanding of JavaScript: To customize the Code Tool node for specific actions.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "..." menu in the top right and select "Import from JSON".
    • Paste the JSON and click "Import".
  2. Configure the MCP Server Trigger:
    • The MCP Server Trigger node will automatically configure itself. Its primary purpose is to act as a listener for an AI agent.
  3. Customize the Code Tool:
    • Open the Code Tool node.
    • Replace the placeholder code with your desired JavaScript logic. For example, you could write code to:
      • Call the KlickTipp API to create a new contact.
      • Update an existing contact's tags or custom fields.
      • Send a specific email campaign.
      • Retrieve contact information based on AI agent queries.
    • Ensure the Code Tool returns a meaningful response that the AI agent can interpret.
  4. Connect to an AI Agent:
    • Configure your AI agent (e.g., a custom GPT, a LangChain application, or another AI service) to use an MCP server and register this n8n workflow's Code Tool as an available action. The AI agent will then be able to call this tool when appropriate.
  5. Activate the Workflow:
    • Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the n8n editor.

This workflow provides a powerful foundation for integrating custom business logic and third-party API interactions into your AI agents, enabling them to perform specific, tailored actions in response to user prompts.

Related Templates

AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp

This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The “virtual executive team,” is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier 🎯 Core Features 🧑‍💼 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. 📊 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. 🕵️‍♀️ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. ⏰ 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline — key traits for early-stage success. 🗓️ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. 💬 WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. ⚙️ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. 🧩 Integrations Required Gemini API – for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API – for business and competitor analysis SerpAPI – for market research and opportunity scouting Google OAuth – to connect Sheets, Calendar, and Gmail WhatsApp Business API – for message triggers and responses 🚀 Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. 🧰 Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startup’s needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you 💡 Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business

ShadrackBy Shadrack
331

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API

Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. It’s designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
110