Feature request - "Read/Get Draft" action for Gmail

Hi team,

I'd like to request a new Gmail action in Pabbly Connect: the ability to read or fetch the content of an existing Gmail draft (subject and body).

My use case: I have an automated process that composes a daily briefing and saves it as a Gmail draft. I'd like Pabbly to pick up that draft's content and relay it onward (in my case, to a Telegram bot). Right now the Gmail connector can create a draft and find/send emails, but there's no way to read the body of a draft that hasn't been sent. The email parser doesn't help here, since a draft is never actually delivered to a parser address.

A "Get Draft" or "Read Draft" action - ideally letting you find a draft by subject or pick the latest draft, and returning its subject and body - would close this gap. It would make Gmail drafts usable as a content source in workflows, not just a destination.

Is this something you'd consider adding? 

Happy to share more detail on the workflow if useful. Thanks for the great product.

Hello Verel,

Thanks for contacting us.

I would like to inform you that the Existing Find Email action event under the Gmail application does fetch the Draft email. I made a search with the Subject line and received the response. The response also includes the content of the draft email. Kindly run some tests executing the action.

Thanks & Regards,

Adeel Akhtar
🌐 Pabbly.com

Found it sorry. I was looking for the find email when I added Gmail as a trigger, but it's within the action modules.

Thanks for your help Adeel.

Hello Verel,

You're welcome. Glad to hear that you are able to find the action event.

Thanks & Regards,

Adeel Akhtar
🌐 Pabbly.com

Hi Adeel,

Thanks for the help so far - the Gmail Find Email step is working perfectly and returns the draft content as you described.

I've now hit a problem on the next step: a Telegram Bot "Send a Text Message or Reply" action. The message body maps fine and the text/parse mode are correct, but the action fails on the button fields with this error:

Bad Request: inline keyboard button URL '{{pc_skip_field_with_parent}}' is invalid: Disallowed character in URL host

It seems the {{pc_skip_field_with_parent}} placeholder is being sent to Telegram literally as a button URL, instead of being stripped out when the field is empty.

What I've tried, none of which fixed it:

1. Leaving both Button Label(s) and Button URL(s) completely empty - the fields show empty but the error persists, so the skip token appears to be sent anyway.

2. Toggling the input mode on both button fields and leaving them blank.

3. Deleting the Telegram action entirely and recreating it from scratch, without touching the button fields at all.

4. Entering a valid Button Label and a valid https URL - this time it returns a generic "something went wrong" and the action doesn't complete.

So the action fails whether the button fields are empty or filled. It looks like a bug in how the Telegram action handles the optional button parameters.

Could you take a look? My workflow is "Daily Morning Brief (Gmail)" - Schedule → Gmail Find Email → Telegram Bot. Happy to share screenshots or grant access if useful.

Thanks,
Verel

Hello Verel,

Could you please share the Workflow URL so that we can look into it and provide information accordingly? Also, share a screen recording or screenshots of the error you are facing.

Please be aware that to assist you effectively, we may need to access your Pabbly Connect account. If you're comfortable with this, please grant us permission by stating in your next email: "You have my permission to log into my Pabbly Connect account, and edit workflow {If required}. Here is the registered email address associated with it."

Thanks & Regards,

Adeel Akhtar
🌐 Pabbly.com