How to Add Conversation Thread Field in Gmail Lindy Setup

Thanh P. · 2025-07-27 15:32:17.886771+00

Hey team! I'm trying to build an email inbox manager and from the template of "email negotiator", I see that the Gmail send email action has a field where you can reference the "conversation thread". But when I build a Lindy from scratch, I don't see that field anywhere. The issue I'm running into is that my from-scratch Lindy starts to write brand new draft emails instead of replying to an existing thread. How do I make sure it has that "conversation thread" field appear?

How to Add Conversation Thread Field in Gmail Lindy Setup | Lindy Community

13 comments

· Sorted by Oldest

Thanh P.
·
·
It seems like the templates have this field but not when you make something from scratch.
Alon J.
·
·
Hey Thanh! Got your support email 🙂 That feature is actually specific for a 'send reply' action that can only be added as an action (not a trigger). I've attached a screenshot 🙂 Let me know if that helps!
Thanh P.
·
·
Oh I see. So it can only be used when that trigger of "email received" is used. Is there a way to build it so the Lindy wakes up once a day and then mass processes emails? I wouldn't use that trigger then (likely the timer one) and then reads in a loop every unread email, and replies to specific ones as needed. The issue is that because it cannot reference a thread, it just creates new drafts.
Alon J.
·
·
Hey Thanh! If you're using the timer trigger, you can use the 'search emails' action that can look for emails over the last x amount of time, and process them based on your conditions. Let me know if that's what you're referring to 🙂
Thanh P.
·
·
Yep! That's what I meant. Here's what I have. The issue is, when you use the action of "send email" (since there's no Send Reply), it creates a new draft or send a new email, instead of replying to the found emails.
Thanh P.
·
·
So it's not within the same thread. It drafts a new email as a separate email, or sends a new email but not as a reply. Because it cannot reference the thread. So it seems like to me, the "send reply" would be the solution but it only becomes available if you have the "email received" trigger.
Thanh P.
·
·
I also tried adding it as a skill to the agent, but it didn't seem available. So I tried to make it conditional what the next step would be (reply or archive) and it also doesn't show the "send reply" action.
Alon J.
·
·
Ah yeah, the reply would need to be connected to an email received step of some sort. What you can do though , is have an 'email received' action with a filter -> That goes into a timer waits until a specific time of day -> Get email -> Condition that passes based on if its read/unread I would duplicate this flow and try that (if that's the idea you're looking to do!)
Thanh P.
·
·
Ah ok that's an interesting idea Alon J.! I'm trying to think what's the best/efficient use of credits because with email it can easily get burned fast haha.
Alon J.
·
·
Yeah it's a good point -> You would have to add a filter to the 'Email received' trigger there to keep it cheaper. Are you looking to process every single email?
Thanh P.
·
·
Yes want to process every email. Keeping the filter tight is something I definitely want to do. I thought maybe the "search emails" -> loop might be faster/efficient but then I don't have the send reply action. So I think I'll try your suggestion with "unread/read" condition for once daily clean up of emails.
Alon J.
·
·
Ah, it may be tough to process every email without it being expensive. It's a tough scenario here without adding filters on the email received trigger
Thanh P.
·
·
Appreciate the support Alon J.

Thanh P.
·
·
It seems like the templates have this field but not when you make something from scratch.
Alon J.
·
·
Hey Thanh! Got your support email 🙂 That feature is actually specific for a 'send reply' action that can only be added as an action (not a trigger). I've attached a screenshot 🙂 Let me know if that helps!
Thanh P.
·
·
Oh I see. So it can only be used when that trigger of "email received" is used. Is there a way to build it so the Lindy wakes up once a day and then mass processes emails? I wouldn't use that trigger then (likely the timer one) and then reads in a loop every unread email, and replies to specific ones as needed. The issue is that because it cannot reference a thread, it just creates new drafts.
Alon J.
·
·
Hey Thanh! If you're using the timer trigger, you can use the 'search emails' action that can look for emails over the last x amount of time, and process them based on your conditions. Let me know if that's what you're referring to 🙂
Thanh P.
·
·
Yep! That's what I meant. Here's what I have. The issue is, when you use the action of "send email" (since there's no Send Reply), it creates a new draft or send a new email, instead of replying to the found emails.
Thanh P.
·
·
So it's not within the same thread. It drafts a new email as a separate email, or sends a new email but not as a reply. Because it cannot reference the thread. So it seems like to me, the "send reply" would be the solution but it only becomes available if you have the "email received" trigger.
Thanh P.
·
·
I also tried adding it as a skill to the agent, but it didn't seem available. So I tried to make it conditional what the next step would be (reply or archive) and it also doesn't show the "send reply" action.
Alon J.
·
·
Ah yeah, the reply would need to be connected to an email received step of some sort. What you can do though , is have an 'email received' action with a filter -> That goes into a timer waits until a specific time of day -> Get email -> Condition that passes based on if its read/unread I would duplicate this flow and try that (if that's the idea you're looking to do!)
Thanh P.
·
·
Ah ok that's an interesting idea Alon J.! I'm trying to think what's the best/efficient use of credits because with email it can easily get burned fast haha.
Alon J.
·
·
Yeah it's a good point -> You would have to add a filter to the 'Email received' trigger there to keep it cheaper. Are you looking to process every single email?
Thanh P.
·
·
Yes want to process every email. Keeping the filter tight is something I definitely want to do. I thought maybe the "search emails" -> loop might be faster/efficient but then I don't have the send reply action. So I think I'll try your suggestion with "unread/read" condition for once daily clean up of emails.
Alon J.
·
·
Ah, it may be tough to process every email without it being expensive. It's a tough scenario here without adding filters on the email received trigger
Thanh P.
·
·
Appreciate the support Alon J.