Overview
The node "MPC Server Trigger" is designed to act as a webhook trigger that listens for incoming data from an MPC (likely a custom or third-party service) server. It waits for HTTP requests sent to a specified URL and path, authenticates them using bearer token authentication, and then triggers workflows in n8n with the received data.
This node is beneficial when you want to integrate real-time data or events pushed from an external MPC server into your n8n automation workflows. For example, it can be used to receive notifications, updates, or any event-driven data from the MPC system and process it immediately within n8n.
Practical examples:
- Receiving transaction or event data from an MPC platform to update internal databases.
- Triggering alerts or notifications based on specific events sent by the MPC server.
- Integrating MPC data streams into broader automation pipelines for processing or analytics.
Properties
| Name | Meaning |
|---|---|
| MPC URL | The base URL of the MPC server endpoint where the trigger will listen for incoming data. |
| Path | The specific path appended to the MPC URL that defines the webhook endpoint. |
| Authentication | The method of authentication used to secure the webhook; currently supports Bearer Auth. |
Output
The node outputs the data received from the MPC server in its json output field. This typically contains the payload sent by the MPC server in the HTTP request body. The structure of this JSON depends on the data sent by the MPC server but generally represents the event or data object that triggered the workflow.
There is no indication that the node outputs binary data.
Dependencies
- Requires an active HTTP endpoint accessible at the configured MPC URL and path.
- Requires a valid bearer token credential for authentication to secure incoming requests.
- No additional external libraries or services are indicated beyond standard HTTP and bearer token authentication.
Troubleshooting
Common issues:
- Incorrect MPC URL or path configuration may cause the trigger not to receive any data.
- Missing or invalid bearer token authentication will result in unauthorized access errors.
- Network connectivity issues between the MPC server and n8n instance can prevent triggering.
Error messages:
- Unauthorized or 401 errors indicate problems with the bearer token authentication setup.
- 404 errors suggest the webhook path is incorrect or not properly registered.
Resolutions:
- Verify the MPC URL and path match exactly what the MPC server uses to send data.
- Ensure the bearer token credential is correctly configured and valid.
- Confirm that the n8n instance is reachable from the MPC server network.
Links and References
- n8n Webhook Documentation
- General information about Bearer Token Authentication: https://tools.ietf.org/html/rfc6750