https://linen.dev logo
Powered by
a
When responding to a thread using the gmail toolkit, threading works (the email is threaded correctly), but the the email's content is not copied on each message (in Gmail each message has a copy of the thread upto that point. This can be accessed with the 3 dots "..." in the gmail GUI). This works fine when sending emails using the gmail GUI, but when we use the composio toolkit the 3 dots are not present in the email. This is key because when people are added to a running thread, they won't be able to have context on what happened before. Are we missing a parameter, header or something? I've attached an image
u
Hey @AlvaroVargas11, We tried it on our end, and thread replying seems to be working fine. Could you share reproducible steps and the above-mentioned image? It'll make it easier for us to reproduce the issue with better context. https://cdn.discordapp.com/attachments/1459210104690839673/1459213567566942469/Screenshot_2026-01-09_at_21.19.53.png?ex=697a3109&is=6978df89&hm=1eeb5e0800467f4d2766ba83ca1986f8b4c825180cab913a5b8a275be11cbc64&
a
Hey @Uday yep, but you are not getting the 3 dots, see the image i posted
u
Hey @AlvaroVargas11, I see, you meant thread reference or quoted text. Gmail API does not automatically do this, let me check with the team if we can add this.
a
@Uday any update on this
Issue: When using GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID or GMAIL_FETCH_MESSAGE_BY_THREAD_ID to fetch incoming emails (emails received from external senders), the response returns: { "payload": { "mimeType": "multipart/alternative", "body": { "size": 0 }, "parts": [] }} The parts array is empty and body.data is not present, even when passing format: "full". Expected behavior: The response should include the nested MIME parts with text/html and text/plain bodies, similar to what the native Gmail API returns: { "payload": { "mimeType": "multipart/alternative", "parts": [ { "mimeType": "text/plain", "body": { "data": "base64..." } }, { "mimeType": "text/html", "body": { "data": "base64..." } } ] }} Interestingly: Emails that we send through the Gmail API do return the HTML body correctly (mimeType: "text/html" with body.data present). The issue only affects incoming emails from external senders. Impact: Without the HTML body, we can only use the messageText plain text field, which contains Gmail's > quote markers for nested replies. This breaks our email reply formatting.
---
this is causing a lot of issues with our customers we need help @Uday
u
Hey @AlvaroVargas11, looks like we do return payload inside 
parts
when 
full
is used. Could re-check and lmk? Also, regarding the quoted replies("...") we've fixed the issue and it's currently in QA, I'll update you when it's live! https://cdn.discordapp.com/attachments/1459210104690839673/1462074520104861823/Screenshot_2026-01-17_at_18.48.47.png?ex=697a0d81&is=6978bc01&hm=af549eb28eb7ddc5259da992fa84102b7a94e1bf7fcc5e2131bc33309bf2caef&
a
thanks lmk when it's live
do you think you'll push this to prod today?
u
@AlvaroVargas11, let me check with the team and update the status.
a
@Uday any iupdate? sorry to push this hard, but we ar elosing customers due to this
a
Hey Alvaro, apologies for the delay here. We have some major changes that need to be taken live, and this fix is included in that deployment. It took a bit longer than expected. I believe it should go live within ~24 hours, but I'll try to push this & confirm with the team and get back to you ASAP.
a
@Abhishek @Uday has this gone live? We are waiting on this to deploy to prod too
@Abhishek @Uday any update?
u
a
nice! should we do anything on our end? update the version of the toolkit? set a parameter in a different value ?
@Uday i changed the version to 20260122_00 but still, it ain't working
I think i found the issue testing in playground. Can you confirm the fix is implemented for the reply_to_thread tool, but not create_draft (We would need it here too)?
@Uday
u
Could you make sure you are passing the threadId? lmk if the issue persists.
a
@Uday good morning, yes we are passing the thread id
u
@AlvaroVargas11, could you share a screen-recording? It'll help us reproduce it.
a
let me know if this works. When I use the reply to thread tool, the quoted text will appear in the email automatically. With the draft tool it doesn't. This happens on your playground too
@Uday
u
I see, sorry for the misunderstanding here: "*I think i found the issue testing in playground. Can you confirm the fix is implemented for the reply_to_thread tool, but not create_draft (We would need it here too)?*" — Yes, we've fixed the 
GMAIL_REPLY_TO_THREAD
as it was the only requested feature. We'll update the 
GMAIL_CREATE_EMAIL_DRAFT
as well.
a
ok thanks!
@Uday do you have an ETA on this?
u
The fix should be live in 1-2 weeks or sooner.
a
@Uday this is killing us ...
u
Hey @AlvaroVargas11, the timeline I mentioned is the upper bound, and ideally this should be done within a week. We pushed some changes live a few minutes ago, and this process needs thorough QA before going fully live. I know this is frustrating, and I’ve actively escalated this with the team and am closely following up to get this live as soon as possible. Thanks so much for your patience and understanding.
a
Thanks @Uday ! please keep me posted
u
hi @AlvaroVargas11 i carefully reviewed your chat history. i'm contacting you because it seems like you're building some kind of project. as an AI expert specializing in 
Composio
usage, would you be open to the opportunity to work with me?
u
Hey @AlvaroVargas11, the fix for 
GMAIL_CREATE_EMAIL_DRAFT
is live!
a
Thanks!!! @Uday
2 Views
PreviousNext
Powered by