The Markdown to HTML node in n8n is not functioning correctly when used in conjunction with other nodes in the workflow. The issue arises when the Markdown to HTML node is placed after other nodes, such as an HTTP request node or an IF node. In these cases, the output from the previous nodes is not being processed by the Markdown to HTML node, resulting in the original data being passed through without any HTML conversion.
To resolve this issue, the Markdown to HTML node should be placed before the HTTP request node or any other nodes that might interfere with its functionality. This ensures that the Markdown text is processed correctly and converted to HTML before being passed to subsequent nodes.
Here is an example of how the workflow should be structured:
1. **Webhook Node**: Receive data from Trello.
2. **HTTP Request Node**: Make a request to retrieve additional data (if necessary).
3. **IF Node**: Conditionally process the data based on certain criteria.
4. **Markdown to HTML Node**: Convert the Markdown text to HTML.
5. **Other Nodes**: Any additional processing or output nodes.
By placing the Markdown to HTML node before any other nodes that might alter its input, you can ensure consistent and correct HTML output from your Markdown text.
Additionally, it is important to check the version of n8n being used, as older versions might have different behaviors or bugs that could affect the functionality of the Markdown to HTML node.