Overview
This node acts as a simple HTTP response handler designed to send back a JSON response containing the current execution ID. It optionally supports caching the input request parameters for a specified duration. This can be useful in scenarios where you want to confirm receipt of data or trigger downstream workflows with an acknowledgment, while optionally caching inputs to optimize repeated requests or debugging.
Practical examples:
- Sending a confirmation response from a webhook endpoint.
- Caching incoming request data temporarily to avoid redundant processing.
- Returning execution metadata for logging or tracking purposes.
Properties
| Name | Meaning |
|---|---|
| 缓存请求参数 | Boolean flag to enable or disable caching of the input request parameters. |
| 缓存过期时间 | Number specifying the cache expiration time in seconds; only applicable if caching is enabled. |
Output
The node outputs the original input data unchanged in its json field. If caching is enabled, it stores the first input item's JSON data keyed by the execution ID for the specified TTL but does not modify the output.
Additionally, the node sends an HTTP response with:
- Status code: 200 (OK)
- Headers: Content-Type set to application/json
- Body: JSON string containing the current execution ID under the key
executeId
No binary data output is produced.
Dependencies
- Uses an internal utility module for caching (
dataCache), which must be available in the environment. - Requires no external API keys or services.
- The node relies on n8n's built-in methods for retrieving input data, parameters, and sending HTTP responses.
Troubleshooting
- Caching issues: If caching is enabled but data is not stored or retrieved correctly, verify that the internal cache utility is properly configured and accessible.
- Invalid cache TTL: Providing a negative number for cache expiration will default to zero, effectively disabling caching duration.
- Response sending errors: If the node fails to send the HTTP response, ensure that the workflow is triggered in a context supporting HTTP response handling (e.g., webhook).
- Error handling: On failure, if "Continue On Fail" is enabled, the node appends error details to the output; otherwise, it throws the error with context about the item index.
Links and References
- n8n Documentation - Creating Custom Nodes
- n8n Docs - Webhook Node (for understanding response handling)