GMAIL_SEND_EMAIL supports from_email for verified send-as aliases, but GMAIL_REPLY_TO_THREAD and GMAIL_CREATE_EMAIL_DRAFT don't.
This makes it impossible to reply in-thread from an alias — a very common setup (one mailbox, multiple verified send-as domains). The current workaround forces a choice between:
- a correctly-threaded reply from the wrong address (GMAIL_REPLY_TO_THREAD), or
- a correctly-addressed reply that breaks threading on the sender's side (GMAIL_SEND_EMAIL with
from_email, which can't take a thread_id).
Real-world impact: replying to an insurance claim thread (Zendesk-based) where the ticket is keyed to the alias address — neither tool can produce a reply that is both in-thread and from the right address, so the reply had to be sent manually.
Since the From-header logic already exists in GMAIL_SEND_EMAIL, this looks like porting one parameter to the other two tools (and ideally GMAIL_UPDATE_DRAFT as well).
GMAIL_SEND_EMAIL supports
from_emailfor verified send-as aliases, but GMAIL_REPLY_TO_THREAD and GMAIL_CREATE_EMAIL_DRAFT don't.This makes it impossible to reply in-thread from an alias — a very common setup (one mailbox, multiple verified send-as domains). The current workaround forces a choice between:
from_email, which can't take athread_id).Real-world impact: replying to an insurance claim thread (Zendesk-based) where the ticket is keyed to the alias address — neither tool can produce a reply that is both in-thread and from the right address, so the reply had to be sent manually.
Since the From-header logic already exists in GMAIL_SEND_EMAIL, this looks like porting one parameter to the other two tools (and ideally GMAIL_UPDATE_DRAFT as well).