Overview
The EspoEcho node simply echoes back a message provided as input. It logs the message to the console and returns the same data it received without modification. This node is useful for debugging workflows by allowing users to output and verify messages or data at specific points in the workflow.
Practical examples:
- Testing if a previous node correctly outputs a message.
- Debugging complex workflows by echoing intermediate data.
- Logging custom messages during execution for monitoring purposes.
Properties
| Name | Meaning |
|---|---|
| Message | The message to echo |
Output
The node outputs the same input data it receives, unchanged. The json field of each item contains the original data including the message property. No binary data is produced.
Dependencies
- Requires an API key credential (generic API authentication token) configured in n8n, though this credential is not actively used in the current logic.
- No external services are called; the node operates entirely locally.
Troubleshooting
- If no message appears in the debug tab, ensure that the input data includes the
messageproperty. - The node logs messages to the console; make sure your environment allows viewing console output.
- Missing or misconfigured credentials will cause the node to fail before execution, even though the credential is not used in the code.