n8n Endpoints
This document provides a comprehensive reference for the n8n service endpoints and webhooks available in the MOOD MNKY ecosystem. These endpoints allow you to interact with workflows, trigger automations, and manage integrations.Base URLs
- Production:
https://mnky-mind-n8n.moodmnky.com - Development:
http://localhost:5678
Authentication
All n8n API requests require authentication. There are two authentication methods available:API Key Authentication
Include your API key in the request headers:- Navigate to the n8n dashboard
- Go to Settings > API Keys
- Create a new API key with appropriate permissions
Session Authentication
For browser-based access, use session authentication by logging in through the n8n interface.Core API Endpoints
Workflows API
List All Workflows
Get Workflow Details
id(path parameter): The ID of the workflow
Activate Workflow
id(path parameter): The ID of the workflow
Deactivate Workflow
id(path parameter): The ID of the workflow
Executions API
List Workflow Executions
workflowId(optional): Filter by workflow IDstatus(optional): Filter by execution status (success,error,waiting)limit(optional): Maximum number of results to return (default: 20)
Get Execution Details
id(path parameter): The ID of the execution
Webhook Endpoints
n8n can create webhook endpoints that serve as triggers for workflows. These webhooks are automatically generated when creating a webhook node in a workflow.Workflow Webhook
path(path parameter): The unique webhook path for the workflow
- Data produced by the workflow
- A simple acknowledgment
- An empty response with a status code
Webhook Authentication
For secure webhooks, you can add authentication:- Basic Auth
- Header-based authentication
- Query parameter-based authentication
MOOD MNKY Specific Endpoints
Content Synchronization Webhook
Order Processing Webhook
User Onboarding Webhook
Integration with Other Services
Ollama Integration
Flowise Integration
Langchain Integration
Health Check Endpoint
Best Practices
Rate Limiting
The n8n API implements rate limiting to protect the service from abuse. Limits apply based on:- API key
- IP address
- Endpoint
429 Too Many Requests response.
Webhook Security
When creating webhooks:- Use authentication mechanisms (API keys, HMAC validation)
- Validate request payload schemas
- Implement retry mechanisms for failed webhook deliveries
- Use HTTPS for all production webhooks
Error Handling
API errors follow a consistent format:UNAUTHORIZED: Authentication failedFORBIDDEN: Insufficient permissionsWORKFLOW_NOT_FOUND: Requested workflow doesn’t existEXECUTION_NOT_FOUND: Requested execution doesn’t existRATE_LIMIT_EXCEEDED: Too many requests