HTML styling email sent by Gmail "send and wait" node

Describe the problem/error/question

I would like to use HTML to style an email I’m automatically sending from the Gmail “send and wait for response” node. Unlike in the regular Gmail “send message” node, I do not see an option to select “HTML” as the email type in the “send and wait” node. Is there a good workaround for this, or any reason the option is not made available in this node?

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 2.12.3
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: MacOS 15.6.1
1 Like

the send and wait node is pretty bare-bones compared to the regular send node. workaround: use a function node before send and wait to inject the html as a string into the message body, or split it into two workflows — regular send for the html email, then a separate webhook trigger to wait for the response. not ideal but works

1 Like

Hi @adminasst i think for that you need to use a regular gmail send operation and there you can give a form link which user can fill for the information you are trying to take in HITL gmail.

As send and wait gmail node does not actually supports HTML directly in the message field, same with attachment operation as that is also not available in send and wait, consider using classic gmail send node and there attach a n8n form trigger link that would be a better case if HTML formatting and file attachments is very imp.

1 Like

@Anshul_Namdev yeah the form trigger approach is cleaner for proper HITL response capture, especially if you need formatted responses. the function node thing is more if you just want html in the email body and dont want to restructure the whole flow — depends what the actual requirement is

2 Likes

thanks all, I think the HTML injection approach will work best for this use case. will give it a try, if it doesn’t work i’ll take a look at regular gmail + form. cheers!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.