mirror of
https://github.com/khoaliber/n8nworkflows.xyz.git
synced 2026-04-28 00:29:22 +00:00
creation
This commit is contained in:
nusquama
@@ -0,0 +1,187 @@
|
||||
🛠️ Dropcontact Tool MCP Server
|
||||
|
||||
https://n8nworkflows.xyz/workflows/----dropcontact-tool-mcp-server-5275
|
||||
|
||||
|
||||
# 🛠️ Dropcontact Tool MCP Server
|
||||
|
||||
### 1. Workflow Overview
|
||||
|
||||
This workflow, titled **🛠️ Dropcontact Tool MCP Server**, serves as a Microservice Control Protocol (MCP) server designed to expose two primary operations related to contact data enrichment and retrieval using the Dropcontact Tool integration. It is intended for integration with AI agents or other automation solutions that require contact enrichment or data fetching functionalities via a consistent webhook interface.
|
||||
|
||||
**Target Use Cases:**
|
||||
- Enriching contact information by finding B2B emails.
|
||||
- Fetching the status or result of previous enrichment requests.
|
||||
- Providing a zero-configuration, ready-to-use MCP service for Dropcontact operations, facilitating seamless AI or automation system integration.
|
||||
|
||||
**Logical Blocks:**
|
||||
- **1.1 Input Reception:** Handles incoming MCP requests via a webhook trigger node.
|
||||
- **1.2 Contact Operations:** Performs Dropcontact Tool operations — either “Find B2B emails” or “Fetch Request Contact” — based on the MCP request parameters.
|
||||
- **1.3 Documentation & Guidance:** Sticky notes providing user instructions, setup guidance, and workflow overview.
|
||||
|
||||
---
|
||||
|
||||
### 2. Block-by-Block Analysis
|
||||
|
||||
#### 1.1 Input Reception
|
||||
|
||||
- **Overview:**
|
||||
This block receives incoming requests from AI agents or other clients via an MCP trigger. It acts as the entry point of the workflow, exposing a webhook URL that clients invoke to trigger contact operations.
|
||||
|
||||
- **Nodes Involved:**
|
||||
- `Dropcontact Tool MCP Server`
|
||||
|
||||
- **Node Details:**
|
||||
|
||||
- **Node Name:** Dropcontact Tool MCP Server
|
||||
- **Type:** `@n8n/n8n-nodes-langchain.mcpTrigger`
|
||||
- **Technical Role:** MCP trigger node that listens for incoming MCP requests on a specified webhook path.
|
||||
- **Configuration:**
|
||||
- Webhook path set to `"dropcontact-tool-mcp"`, exposing an endpoint at `/webhook/dropcontact-tool-mcp`.
|
||||
- **Expressions/Variables:** None in this node; it simply receives request data.
|
||||
- **Input Connections:** None (trigger node).
|
||||
- **Output Connections:** Outputs to the two Dropcontact Tool nodes (`Find B2B emails` and `Fetch Request Contact`).
|
||||
- **Version Requirements:** Requires n8n version supporting MCP nodes (v1.95.0 or later recommended).
|
||||
- **Edge Cases / Potential Failures:**
|
||||
- Webhook misconfiguration leading to unreachable endpoint.
|
||||
- Authentication or authorization if externally exposed (handled by MCP node).
|
||||
- High request volumes affecting throughput or rate limits.
|
||||
- **Sub-workflow:** None.
|
||||
|
||||
#### 1.2 Contact Operations
|
||||
|
||||
- **Overview:**
|
||||
This block performs the core Dropcontact Tool operations based on parameters provided by the MCP request. It either enriches contacts by finding B2B emails or fetches status/results of previous requests.
|
||||
|
||||
- **Nodes Involved:**
|
||||
- `Find B2B emails`
|
||||
- `Fetch Request Contact`
|
||||
|
||||
- **Node Details:**
|
||||
|
||||
- **Node Name:** Find B2B emails
|
||||
- **Type:** `n8n-nodes-base.dropcontactTool`
|
||||
- **Technical Role:** Calls Dropcontact API to enrich a contact by finding B2B emails.
|
||||
- **Configuration:**
|
||||
- `email`: Bound dynamically via `$fromAI('Email', '', 'string')`, meaning the AI agent must supply this parameter.
|
||||
- `simplify`: Bound via `$fromAI('Simplify', '', 'boolean')`, optional flag to simplify the response.
|
||||
- No additional fields configured by default.
|
||||
- **Credentials:** Uses Dropcontact API credentials (must be configured by the user).
|
||||
- **Input:** Receives data from MCP trigger node.
|
||||
- **Output:** Returns enriched contact data to MCP response.
|
||||
- **Version Requirements:** Compatible with n8n Dropcontact Tool node version 1 or higher.
|
||||
- **Edge Cases / Potential Failures:**
|
||||
- Missing or invalid email input causing API errors.
|
||||
- API authentication failure due to missing or expired credentials.
|
||||
- API rate limiting or service downtime.
|
||||
- Expression evaluation failure if AI agent does not supply expected parameters.
|
||||
|
||||
- **Node Name:** Fetch Request Contact
|
||||
- **Type:** `n8n-nodes-base.dropcontactTool`
|
||||
- **Technical Role:** Fetches the status or result of a previously made Dropcontact request by request ID.
|
||||
- **Configuration:**
|
||||
- Operation set to `"fetchRequest"`.
|
||||
- `requestId` parameter dynamically set via `$fromAI('Request_Id', '', 'string')`.
|
||||
- **Credentials:** Uses the same Dropcontact API credentials as above.
|
||||
- **Input:** Receives data from MCP trigger node.
|
||||
- **Output:** Returns request status or data to MCP response.
|
||||
- **Version Requirements:** Same as above.
|
||||
- **Edge Cases / Potential Failures:**
|
||||
- Invalid or missing request ID parameter.
|
||||
- API errors or timeouts.
|
||||
- Credential issues.
|
||||
- Expression evaluation failures if the AI agent does not provide `Request_Id`.
|
||||
|
||||
#### 1.3 Documentation & Guidance
|
||||
|
||||
- **Overview:**
|
||||
Provides users with workflow instructions, overview, and operation descriptions via sticky note nodes visible in the editor.
|
||||
|
||||
- **Nodes Involved:**
|
||||
- `Workflow Overview 0`
|
||||
- `Sticky Note 1`
|
||||
|
||||
- **Node Details:**
|
||||
|
||||
- **Node Name:** Workflow Overview 0
|
||||
- **Type:** `n8n-nodes-base.stickyNote`
|
||||
- **Technical Role:** Documentation & instructions for users importing or configuring the workflow.
|
||||
- **Content Highlights:**
|
||||
- Lists available operations (Contact enrich, fetch request).
|
||||
- Setup instructions including credential configuration and webhook URL usage.
|
||||
- Links to n8n documentation and Discord support.
|
||||
- **Input/Output:** None (informational).
|
||||
- **Edge Cases:** None.
|
||||
|
||||
- **Node Name:** Sticky Note 1
|
||||
- **Type:** `n8n-nodes-base.stickyNote`
|
||||
- **Content:** Simply the title "Contact" indicating the logical block for contact operations.
|
||||
- **Input/Output:** None.
|
||||
- **Edge Cases:** None.
|
||||
|
||||
---
|
||||
|
||||
### 3. Summary Table
|
||||
|
||||
| Node Name | Node Type | Functional Role | Input Node(s) | Output Node(s) | Sticky Note |
|
||||
|-------------------------|--------------------------------|---------------------------------------|-----------------------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Workflow Overview 0 | Sticky Note | Documentation and setup instructions | None | None | ## 🛠️ Dropcontact Tool MCP Server<br>### 📋 Available Operations (2 total)<br>**Contact**: enrich, fetch request<br>Setup instructions & support links |
|
||||
| Dropcontact Tool MCP Server | MCP Trigger | Entry point; receives MCP webhook calls | None | Find B2B emails, Fetch Request Contact | |
|
||||
| Find B2B emails | Dropcontact Tool | Enrich contact by finding B2B emails | Dropcontact Tool MCP Server | MCP response (via MCP node) | |
|
||||
| Fetch Request Contact | Dropcontact Tool | Fetch status/result of previous request | Dropcontact Tool MCP Server | MCP response (via MCP node) | |
|
||||
| Sticky Note 1 | Sticky Note | Label for Contact operations block | None | None | ## Contact |
|
||||
|
||||
---
|
||||
|
||||
### 4. Reproducing the Workflow from Scratch
|
||||
|
||||
1. **Create the MCP Trigger Node**
|
||||
- Add node: Type `@n8n/n8n-nodes-langchain.mcpTrigger` (MCP Trigger).
|
||||
- Set **Webhook Path** to `dropcontact-tool-mcp`.
|
||||
- This node will expose a webhook endpoint `/webhook/dropcontact-tool-mcp` for receiving MCP requests.
|
||||
|
||||
2. **Create Dropcontact Tool Node for “Find B2B emails” Operation**
|
||||
- Add node: Type `Dropcontact Tool`.
|
||||
- Configure parameters:
|
||||
- Set `email` field to expression: `$fromAI('Email', '', 'string')`. This means the workflow expects an `Email` parameter from the AI agent input.
|
||||
- Set `simplify` field to expression: `$fromAI('Simplify', '', 'boolean')`. Optional boolean flag from AI agent.
|
||||
- Leave additional fields empty unless customization is required.
|
||||
- Connect MCP Trigger node output to this node.
|
||||
- Assign Dropcontact API credentials (configure in n8n Credentials manager prior, then select here).
|
||||
|
||||
3. **Create Dropcontact Tool Node for “Fetch Request Contact” Operation**
|
||||
- Add node: Type `Dropcontact Tool`.
|
||||
- In the node parameters:
|
||||
- Set operation to `fetchRequest`.
|
||||
- Set `requestId` field to expression: `$fromAI('Request_Id', '', 'string')`.
|
||||
- Connect MCP Trigger node output to this node.
|
||||
- Assign the same Dropcontact API credentials as above.
|
||||
|
||||
4. **Add Sticky Notes for Documentation (Optional but Recommended)**
|
||||
- Add sticky note titled **Workflow Overview 0** with content:
|
||||
- Description of the workflow, usage instructions, available operations, and helpful links (e.g., n8n docs, Discord).
|
||||
- Add sticky note titled **Sticky Note 1** with content:
|
||||
- Simply “## Contact” to label the contact operations block visually.
|
||||
|
||||
5. **Finalize and Activate**
|
||||
- Confirm credential setup for Dropcontact API is valid.
|
||||
- Save the workflow.
|
||||
- Activate the workflow to enable the webhook endpoint.
|
||||
- Copy the webhook URL from MCP Trigger node UI (e.g., `https://your-n8n-instance/webhook/dropcontact-tool-mcp`).
|
||||
- Configure your AI agents or clients to send MCP requests to this URL with appropriate parameters (`Email`, `Simplify`, or `Request_Id`) depending on the operation desired.
|
||||
|
||||
---
|
||||
|
||||
### 5. General Notes & Resources
|
||||
|
||||
| Note Content | Context or Link |
|
||||
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Full setup instructions and operational overview are included in the workflow’s main sticky note for quick reference. | See “Workflow Overview 0” sticky note inside the workflow editor. |
|
||||
| MCP integration allows AI agents to automatically populate parameters using `$fromAI()` expressions, enabling zero-configuration usage out-of-the-box. | n8n MCP & LangChain documentation: https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolmcp/ |
|
||||
| For technical support or customization questions, the workflow author provides a Discord contact: [discord.me/cfomodz](https://discord.me/cfomodz). | Support channel for MCP integration and Dropcontact Tool usage. |
|
||||
| Dropcontact API credentials must be set up once and linked to all Dropcontact Tool nodes. The workflow expects a valid API key with sufficient quota and permissions. | Configure credentials in n8n Credential Manager under "Dropcontact API". |
|
||||
| The workflow assumes n8n version 1.95.0 or later for full MCP node compatibility. | Upgrade n8n if MCP nodes or LangChain nodes are not available. |
|
||||
|
||||
---
|
||||
|
||||
**Disclaimer:** The provided text is exclusively derived from an automated n8n workflow created using n8n, a tool for integration and automation. This processing strictly complies with current content policies and contains no illegal, offensive, or protected elements. All data handled is legal and public.
|
||||
Reference in New Issue
Block a user