Hey guys,
I was having issues formatting HTML content to texts. I’ve tried many different approaches and managed to make Scenario #3 work but since I’m not a programmer and I’m learning n8n, I thought I should reach out to the awesome community here. Here are a few questions:
- Scenario #3 works, but it shouldn’t be this hard? Is this the only way to make it work?
- Scenario #2 seems to work better out-of-the-box than #1, am I missing something?
- Is there a way to make Scenario #4 work?
JSON file URL: Google Docs: HTML-to-Text scenarios
Workflow URL: n8n.io: HTML-to-Text scenarios
Note: Can’t seem to share the workflow’s code. It’s returning a 422 error.
Scenario #1: Directly using the n8n’s HTML node/module. (Note that the content I’m parsing doesn’t actually have full HTML structure)
- Seems to mess up spacing from the presence of HTML tags and \n
- Seems to only format these HTML character entities (HTML Character Entities), but not others like " or &.
- Didn’t remove 2 or more whitespaces.
Scenario #2: Using MAKE’s HTML node/module via webhooks
- Didn’t mess up spacing from the presence of HTML tags and \n
- Seems to also format these HTML character entities (HTML Character Entities), but not others like " or &.
- It removed 2 or more whitespaces.
Scenario #3: Using expressions to modify all the strings
It works but it shouldn’t be this hard?
Scenario #4: Trying to retrieve the full HTML structure for processing
I suspect maybe the HTML module is better if it actually processes content with full HTML structure, but I can’t get it to work. Seems like the string/text that I managed to retrieve (with “never error”) is not actually HTML (by intention).
Thanks a bunch!
Neo