https://linen.dev logo
Creating Drafts on Gmail threads
# 🖥│support-forum
a
When I create a draft using GMAIL's create email draft tool, the email is threaded correctly for the sender, but not for the recipients. The recipients will get individual emails... We need help asap! Either a thread id parameter or something on the tool, or have the reply to thread tool accept draft mode parameter. @abhishekpatil4
Adding drafts and messages to threads If you are sending or migrating messages that are a response to another email or part of a conversation, your application should add that message to the related thread. This makes it easier for Gmail users who are participating in the conversation to keep the message in context. A draft can be added to a thread as part of creating, updating, or sending a draft message. You can also add a message to a thread as part of inserting or sending a message. In order to be part of a thread, a message or draft must meet the following criteria: **The requested threadId must be specified on the Message or Draft.Message you supply with your request. The References and In-Reply-To headers must be set in compliance with the RFC 2822 standard. The Subject headers must match. Take a look at the creating a draft or sending a message examples. In both cases, you would simply add a threadId key paired with a thread ID to a message's metadata, the message object.**
@Uday
c
Hey Alvaro, you can use the draft id in
GMAIL_SEND_DRAFT
Tool to send the created Draft. Also, could you specify "threaded correctly for the sender, but not for the recipients"
a
that's not what i need. I need to create a drat, but when i send from GMAIL, whenever i create the draft with the composio create draft tool, it will thread it for me correctly, but for the recipient it won't ... they'll receive it as an independent email, and not thread it in his gmail inbox. We need to do this per GMAIL docs - In-Reply-To headers The requested threadId must be specified on the Message or Draft.Message you supply with your request. The References and In-Reply-To headers must be set in compliance with the RFC 2822 standard. The Subject headers must match. Take a look at the creating a draft or sending a message examples. In both cases, you would simply add a threadId key paired with a thread ID to a message's metadata, the message object.
@Uday
just to clarify i'm creating the draft with composio, then clicking send on my gmail console
@Uday - need help here, we are moving into producition next week and I need to figure this out .. thanks!
a
Hi @alvarovargas11_07237, Just want to confirm I understand what you're asking for => When you create a draft using our tool with a thread_id, then manually send it through Gmail web interface, it should appear as part of the existing conversation thread for recipients (not as a separate email). correct?
a
Yes. The sender sees it threaded correctly, but the recipients don't - both on gmail clients
@abhishekpatil4 we can hop on a call if you want to review this ... it's critical for us to get right
a
We understood the feat request and have escalated it to our integrations team.
a
@abhishekpatil4 any news? sorry to be pushing hard, but we are gearing up things for a launch and this is critical
c
Hey, let me check and get back with an ETA.
Hey Alvaro, we’ve added support for this.. QA team is testing it, I’ll update here once we take it live
a
this feat is live @alvarovargas11_07237
l
Do you need developer?
a
thanks i'll test this and get back
no thanks
@Uday good morning, got a critical issue here again. This is breaking our flow. This STOPPED working on both desktop and mobile. E.g.: Sender A sends an email. Sender B opens the thread on mobile, has a draft auto-created. Clicks on the draft and hits send. Sender A will recieve an email response, but not threaded. Sender B will have the thread correctly displayed. This is critical LogId: log_FdBYXrCL_Axo UserId: fwaqHBnMqGXiFd0rXiKZTBd9e5v2
a
checking
a
@abhishekpatil4 good morning, any news on this ?
We have customers at risk of churn because of this
a
Hey, really sorry about this. We understand how important this is and team is already investigating this on priority.
Hey Alvaro, We found that you're on an older version (
00000000_00
) based on logId shared - the threading fix is available in version
20250925_00
& higher. [Versioning doc](https://docs.composio.dev/docs/toolkit-versioning) Could you please update to the specified or latest version? You can get the versions from your dashboard (see attached image)? Also, just a heads up: changing the email subject can break threading for the original sender. Let us know if you still see issues after updating. Happy to help. https://cdn.discordapp.com/attachments/1419282245931241503/1437361106132930642/Screenshot_2025-11-10_at_2.03.58_PM.png?ex=6912f658&is=6911a4d8&hm=db08f37333a8a9bccf8033a11d17a82b348aba6a725d2a6d2e0513036b6cc25c&
a
Hey @abhishekpatil4 we are not specifying a version, shouldn't we be on latest right now?
@abhishekpatil4 any news?
a
Hey, When no version is specified, our system defaults to
00000000_00
(not latest) for backward compatibility. Here's why we went with this approach: We introduced versioning because tools can change over time (e.g., response/request keys might be modified). For users who are directly executing tools manually (not through agents), automatically updating to the latest version could break their implementations without warning. By pinning to a specific version by default, we ensure existing integrations remain stable. Also, if you're a recent version of SDK then it should default to
latest
(if executing via agent), let me quickly check the SDK version and get back to you
In version
"@composio/core": "0.1.52"
& later if you're using agent for tool execution then version is defaulted to latest. And in version
"@composio/core": "0.2.0"
& later if you're directly executing the tools (your case) we made passing version mandatory ([ref](https://docs.composio.dev/changelog/2025/10/22)), I'm assuming you might be using a version older than
0.2.0
, could you please update to latest/recent version, retry and let me know it worked fine for you?
a
thanks!