Update n8n-nodes-base.sendemail.md #3684
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
✅ Deploy Preview for n8n-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the Send Email (SMTP) node documentation to include a limitation about email threading.
Currently, emails sent with this node do not appear in the same thread because the node does not support setting headers like In-Reply-To and References. This can cause each email to be treated as a new conversation in most email clients (e.g., Gmail, Outlook).
Changes
Added a Limitations section under the Send Email (SMTP) node docs.
Explained why threading does not work by default.
Added recommended workarounds: using the Gmail node’s Reply operation or community nodes that allow custom headers.