Squarespace form emails → Make mailhook → JobNimbus (no Squarespace access workaround)
No Squarespace access? Forward form emails to a Make mailhook, parse fields, dedupe by email, then upsert contacts and log activities in JobNimbus.
Fix Gmail email threading + quote context in AI replies
Gmail email threading breaks when RFC headers are missing. Set Message-ID, In-Reply-To, References, and threadId — then add quoted context. See the checklist.
TABLE OF CONTENTS
Quick answer
Email threads break when your reply can’t be matched to the original message. To keep threading consistent (especially in Gmail), send replies with the original message’s RFC headers and Gmail thread metadata, and include readable quoted context as a fallback for clients that don’t reliably thread.
Why replies “split” into a new thread
Most email clients and providers build a conversation view by combining signals like:
- Gmail thread identifiers (internal to Gmail)
- RFC email headers that link messages together:
Message-ID(unique ID for each message)In-Reply-To(points to the parent message’sMessage-ID)References(the chain ofMessage-IDs in the conversation)- Subject normalization (e.g.,
Re:changes are usually fine, but totally different subjects can break or fork threads)
If you generate and send AI replies but don’t preserve the linkage headers, Gmail (and many other clients) will often display the reply as a brand-new conversation.
The threading headers you must set (RFC-compliant)
When composing a reply, build these values from the message you’re replying to:
1) Reuse the original
Subject- Keep the subject identical to the message you’re replying to (optionally with a conventional
Re:prefix). - Avoid adding tracking codes or dynamic tokens to the subject for replies (they can cause forks).
2) Set
In-Reply-To- Set it to the original message’s
Message-ID: In-Reply-To: <original-message-id@example.com>
3) Set
References- Include the full chain of message IDs if you have it.
- At minimum include the parent
Message-ID: References: <older-id@example.com> <original-message-id@example.com>
4) Ensure the reply has its own
Message-ID- Your SMTP provider usually generates it automatically.
- Do not try to reuse the original
Message-ID.
Gmail-specific: threadId matters when using the Gmail API
If you're sending via the Gmail API (drafts/messages), set:
threadIdto the existing thread you’re replying inIn-Reply-ToandReferencescorrectlySubjectto match the thread’s subject
Gmail uses a mix of its internal threading plus RFC headers. You typically need both for reliable in-thread placement.
Common implementation pitfalls (and how to avoid them)
1) Missing headers due to “send as new message”
Some libraries default to a fresh outbound email and won’t preserve reply headers unless you explicitly set them.
- Fix: Always treat AI “reply” as a reply, not a new message.
2) Incorrect header formatting
These must be valid RFC header values:
Message-IDvalues are wrapped in angle brackets, like<...>Referencesis space-separated IDs, not comma-separated
3) Provider changes or “helpful” rewriting
Some ESPs or relay layers may rewrite headers or strip fields.
- Fix: log the raw RFC message and confirm the final sent headers match what you set.
- Debug: in Gmail, use “Show original” and check whether
In-Reply-ToandReferencesare present.
4) Replying to the wrong message in a long thread
If the user has multiple messages, you might fetch the newest email but reply to an older one (or vice versa).
- Fix: store the exact
Message-IDof the user message you’re answering, and reply to that.
Add “quoted context” as a reliability + UX fallback
Even when threading works, quoted context helps recipients understand what’s being answered. And when threading fails, it becomes essential.
What to include
Append a minimal quote block at the bottom of the AI reply:
- the original sender
- the original timestamp (as shown to the user)
- the original message text (trimmed)
Example:
On Tue, Apr 28, 2026 at 9:12 AM Alex wrote:
Can you confirm you can support threading on replies?
Quoting rules that keep replies readable
- Keep the quote to a reasonable length (trim signatures, legal footers, and long history)
- Preserve line breaks (use
- Never put quoted context above your new reply text (top-post your AI response, quote below)
A practical checklist for AI reply threading (copy/paste)
Store the user email’s
Message-IDSend the AI response as a reply (not a new message)
Set
In-Reply-To = original Message-IDSet
References = existing references chain + original Message-IDKeep
Subject consistentIf using Gmail API: set
threadId and keep headers RFC-compliantAppend trimmed quoted context for clarity and non-threading clients
Get help building this
Getting AI replies to thread correctly across Gmail, Outlook, and custom inboxes means getting three things right at once: the RFC headers, the Gmail API parameters, and the quoted context format. If you've built part of this and threads are still splitting, book a ZoomFlow session — one of our consultants can debug the header chain with you live and get threading working in the same call.
Related Posts
How to Forward Gmail Attachments to Make for AI Processing (Privacy-First Setup)
How to forward Gmail attachments into Make for AI document processing. Covers mailhook setup, Gmail filters, confidential mode, and polling tradeoffs.
Automate Outlook email orders into your CRM with AI (step-by-step)
Automate Outlook email orders into your CRM with AI field extraction, Make.com, and human review. Cut manual order entry, reduce errors, and scale faster.
