🛠️ Freshdesk tool MCP server 💪 all 10 operations
Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator?
Complete MCP server exposing all Freshdesk Tool operations to AI agents. Zero configuration needed - all 10 operations pre-built.
⚡ Quick Setup
- Import this workflow into your n8n instance
- Activate the workflow to start your MCP server
- Copy the webhook URL from the MCP trigger node
- Connect AI agents using the MCP URL
🔧 How it Works
• MCP Trigger: Serves as your server endpoint for AI agent requests
• Tool Nodes: Pre-configured for every Freshdesk Tool operation
• AI Expressions: Automatically populate parameters via $fromAI() placeholders
• Native Integration: Uses official n8n Freshdesk Tool tool with full error handling
📋 Available Operations (10 total)
Every possible Freshdesk Tool operation is included:
📇 Contact (5 operations)
• Create a contact • Delete a contact • Get a contact • Get many contacts • Update a contact
🔧 Ticket (5 operations)
• Create a ticket • Delete a ticket • Get a ticket • Get many tickets • Update a ticket
🤖 AI Integration
Parameter Handling: AI agents automatically provide values for: • Resource IDs and identifiers • Search queries and filters • Content and data payloads • Configuration options
Response Format: Native Freshdesk Tool API responses with full data structure
Error Handling: Built-in n8n error management and retry logic
💡 Usage Examples
Connect this MCP server to any AI agent or workflow:
• Claude Desktop: Add MCP server URL to configuration • Custom AI Apps: Use MCP URL as tool endpoint • Other n8n Workflows: Call MCP tools from any workflow • API Integration: Direct HTTP calls to MCP endpoints
✨ Benefits
• Complete Coverage: Every Freshdesk Tool operation available
• Zero Setup: No parameter mapping or configuration needed
• AI-Ready: Built-in $fromAI() expressions for all parameters
• Production Ready: Native n8n error handling and logging
• Extensible: Easily modify or add custom logic
> 🆓 Free for community use! Ready to deploy in under 2 minutes.
n8n MCP Server Workflow for AI Model Context Protocol
This n8n workflow provides a robust foundation for interacting with the Model Context Protocol (MCP) server. It simplifies the process of receiving and processing requests from AI models or other systems that adhere to the MCP standard.
What it does
This workflow is designed to act as an MCP server endpoint within n8n.
- Listens for MCP Requests: It uses the
MCP Server Triggernode to listen for incoming requests that conform to the Model Context Protocol. This node acts as the entry point for your AI models or other systems to send context-related information or commands. - Provides a Starting Point: The workflow, as defined, provides a barebones MCP server trigger, ready for further expansion. It includes a
Sticky Notefor documentation or initial thoughts.
Prerequisites/Requirements
- n8n Instance: An active n8n instance where this workflow can be imported and run.
- Model Context Protocol (MCP) Compliant Client: An AI model or system that is configured to send requests to this n8n workflow's MCP server endpoint.
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import" button (up arrow icon) and paste the JSON code.
- Click "Import".
- Activate the Workflow: Ensure the workflow is activated by toggling the "Active" switch in the top right corner of the workflow editor.
- Configure MCP Client: Configure your AI model or MCP-compliant client to send requests to the URL provided by the
MCP Server Triggernode. You can find this URL by clicking on theMCP Server Triggernode and looking at its configuration. - Extend the Workflow: This workflow provides the trigger. You will need to add subsequent nodes to process the incoming MCP requests. For example, you might add:
- Conditional Logic: To handle different types of MCP operations (e.g.,
tool_code,tool_description). - Data Processing: To extract relevant information from the incoming request.
- External API Calls: To interact with other services based on the MCP request (e.g., calling a Freshdesk API, interacting with a database).
- Response Handling: To send a response back to the MCP client.
- Conditional Logic: To handle different types of MCP operations (e.g.,
Related Templates
AI-powered code review with linting, red-marked corrections in Google Sheets & Slack
Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.
Daily cash flow reports with Google Sheets, Slack & Email for finance teams
Simplify financial oversight with this automated n8n workflow. Triggered daily, it fetches cash flow and expense data from a Google Sheet, analyzes inflows and outflows, validates records, and generates a comprehensive daily report. The workflow sends multi-channel notifications via email and Slack, ensuring finance professionals stay updated with real-time financial insights. 💸📧 Key Features Daily automation keeps cash flow tracking current. Analyzes inflows and outflows for actionable insights. Multi-channel alerts enhance team visibility. Logs maintain a detailed record in Google Sheets. Workflow Process The Every Day node triggers a daily check at a set time. Get Cash Flow Data retrieves financial data from a Google Sheet. Analyze Inflows & Outflows processes the data to identify trends and totals. Validate Records ensures all entries are complete and accurate. If records are valid, it branches to: Sends Email Daily Report to finance team members. Send Slack Alert to notify the team instantly. Logs to Sheet appends the summary data to a Google Sheet for tracking. Setup Instructions Import the workflow into n8n and configure Google Sheets OAuth2 for data access. Set the daily trigger time (e.g., 9:00 AM IST) in the "Every Day" node. Test the workflow by adding sample cash flow data and verifying reports. Adjust analysis parameters as needed for specific financial metrics. Prerequisites Google Sheets OAuth2 credentials Gmail API Key for email reports Slack Bot Token (with chat:write permissions) Structured financial data in a Google Sheet Google Sheet Structure: Create a sheet with columns: Date Cash Inflow Cash Outflow Category Notes Updated At Modification Options Customize the "Analyze Inflows & Outflows" node to include custom financial ratios. Adjust the "Validate Records" filter to flag anomalies or missing data. Modify email and Slack templates with branded formatting. Integrate with accounting tools (e.g., Xero) for live data feeds. Set different trigger times to align with your financial review schedule. Discover more workflows – Get in touch with us
Generate Weather-Based Date Itineraries with Google Places, OpenRouter AI, and Slack
🧩 What this template does This workflow builds a 120-minute local date course around your starting point by querying Google Places for nearby spots, selecting the top candidates, fetching real-time weather data, letting an AI generate a matching emoji, and drafting a friendly itinerary summary with an LLM in both English and Japanese. It then posts the full bilingual plan with a walking route link and weather emoji to Slack. 👥 Who it’s for Makers and teams who want a plug-and-play bilingual local itinerary generator with weather awareness — no custom code required. ⚙️ How it works Trigger – Manual (or schedule/webhook). Discovery – Google Places nearby search within a configurable radius. Selection – Rank by rating and pick the top 3. Weather – Fetch current weather (via OpenWeatherMap). Emoji – Use an AI model to match the weather with an emoji 🌤️. Planning – An LLM writes the itinerary in Markdown (JP + EN). Route – Compose a Google Maps walking route URL. Share – Post the bilingual itinerary, route link, and weather emoji to Slack. 🧰 Requirements n8n (Cloud or self-hosted) Google Maps Platform (Places API) OpenWeatherMap API key Slack Bot (chat:write) LLM provider (e.g., OpenRouter or DeepL for translation) 🚀 Setup (quick) Open Set → Fields: Config and fill in coords/radius/time limit. Connect Credentials for Google, OpenWeatherMap, Slack, and your LLM. Test the workflow and confirm the bilingual plan + weather emoji appear in Slack. 🛠 Customize Adjust ranking filters (type, min rating). Modify translation settings (target language or tone). Change output layout (side-by-side vs separated). Tune emoji logic or travel mode. Add error handling, retries, or logging for production use.