Always Authenticate Your Server!
Configured with Aggregate, Execute Workflow Trigger, Filter, Google Sheets, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Routing
- Subworkflow
- Web / API
- Data store
- Transform
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| When Executed by Another Workflow | Trigger | Execute Workflow Trigger | See node parameters |
| Operation | Routing | Switch | See node parameters |
| Paycaptain MCP Server | Trigger | Mcp Trigger | See node parameters |
| Update Employee | Subworkflow | Tool Workflow | See node parameters |
| Get Employee | Subworkflow | Tool Workflow | See node parameters |
| Get Employees | Web / API | HTTP Request | See node parameters |
| Search Employees | Subworkflow | Tool Workflow | See node parameters |
| Log Call | Data store | Google Sheets | append |
| Filter Matches | Routing | Filter | See node parameters |
| Aggregate Search Results | Transform | Aggregate | See node parameters |
| Get Employees1 | Web / API | HTTP Request | See node parameters |
| Filter Matching ID | Routing | Filter | See node parameters |
| Strip Sensitive Fields1 | Transform | Edit Fields | See node parameters |
| Strip Sensitive Fields | Transform | Edit Fields | See node parameters |
| Update Employee1 | Web / API | HTTP Request | POST |
| Valid Fields Only | Transform | Edit Fields | See node parameters |
| Has Valid Request? | Routing | If | See node parameters |
| Get Error Response | Transform | Edit Fields | See node parameters |
| Get Success Response | Transform | Edit Fields | See node parameters |
| Aggregate Get Response | Transform | Aggregate | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleSheetsOAuth2ApihttpHeaderAuth
Workflow notes
1. Set up an MCP Server Trigger
1. Set up an MCP Server Trigger
2. Build Your MCP Server from Existing APIs
2. Build Your MCP Server from Existing APIs
Read more about the HTTP Request Node
N8N allows any organisation to quickly build and host their own MCP server by leveraging existing APIs. Here's a quick example for PayCaptain.com - a cloud-based payroll software for modern companies.
With this set of tools, Paycaptain customers can simplify employee management from within their favourite MCP client such as Claude Desktop. Better yet, n8n also handles distribution so this MCP server can serve entire departments as well.
Always Authenticate Your Server!
Always Authenticate Your Server!
Before going to production, it's always advised to enable authentication on your MCP server trigger.
Sticky Note2
Website: https://paycaptain.com DeveloperHub: https://developer.paycaptain.com
Good to know: PayCaptain also sponsors the n8n London Meetups - Definitely check them out!
Try It Out!
Try It Out!
This n8n demonstrates how any organisation can quickly and easily build and offer MCP servers to their customers or internal staff to improve productivity.
This MCP example uses PayCaptain.com as an example and shows how to create an MCP server which can search for and update employee data.
How it works
- A MCP server trigger is used and connected to 3 custom workflow tools: Search Employee, Get Employee by ID and Update Employee.
- Each tool makes calls to the PayCaptain API to perform their respective tasks. Extra care is performed to strip out sensitive data and ensure we're not sharing too much.
- The Update Employee too also guards against updating fields which would preferably remain readonly. When you control the MCP server, you can determine behaviour of the tool.
- Finally, a Google Sheet node is used to log all operations for later audit. This will add a tiny bit of latency but recommended if sensitive data is being accessed.
How to use
- This MCP server allows any compatible MCP client to manage their PayCaptain employee database. You will need to have a PayCaptain account and developer key to use it.
- Connect your MCP client by following the n8n guidelines here - https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/#integrating-with-claude-desktop
- Try the following queries in your MCP client:
- "When did Sarah start here employment at the company?"
- "Does Jack work Wednesdays or Fridays?"
- "Please update Tracy's NI number to ABCD123456"
Requirements
- PayCaptain Account and Developer Key.
- Google Sheets to log actions for later audit.
- MCP Client or Agent for usage such as Claude Desktop - https://claude.ai/download
Customising this workflow
- Add or remove employee attributes as required for your user case.
- If Google Sheets is too slow, consider an API call to a faster service to log calls to the MCP server.
- Remember to set the MCP server to require credentials before going to production and sharing this MCP server with others!
Always Authenticate Your Server!
Always Authenticate Your Server!
Purpose and structure
This folder contains the Always Authenticate Your Server! workflow. Its executable nodes use aggregate, executeWorkflowTrigger, filter, googleSheets, httpRequest, if, mcpTrigger, set, switch, toolWorkflow. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When Executed by Another Workflow, Paycaptain MCP Server
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Filter/0879_Filter_HTTP_Update_Webhook.json MIT; preserve source notices.