Hi! I can't seem to get this function to work at all. Here's a snippet to try in gmail with the command pack activated obviously. It never renders a result. It just returns
Unknown name "gmail"
{gmail-datereceived: format=X}
{=gmail-datereceived}
Hi @Joe_P,
The command itself is enough to paste received date. You don't need {=gmail-datereceived} part as this is accessing variable that does not exist.
{gmail-datereceived: format=MMM Do, YYY; default=July 1st, 2024}
This should be enough. However there seem to be an issue with this command as it does not work properly right now. We are working on fixing this one and I'll let you know once the issue is fixed.
1 Like
Thanks! Looking forward to using it when it's up and running again.
Can you think some other clever way using the "site:" function to pull the date received from a gmail message while I'm waiting for the "gmail-datereceived:" function to be resurrected?
The issue with the {gmail-datereceived} command itself should now be fixed.
Please give it a spin and let us know if you have any issues.
1 Like
It works! Thanks guys. I just want to take this moment to let you know that Text Blaze changed my life, psychologically, for the better. I have such a healthier relationship with my work ever since I started really implementing your product into all of my customer service centered workflows. I have more time with my family. I know that sounds hyperbolic but it's my truth.
If anyone stumbles across this and needs to make a Gmail snippet that auto inserts something if your reply is over a certain amount of time old (I choose 8 hours in the example) see the snippet below:
{received_time_diff={time: X}-{gmail-datereceived: format=X}}{if: received_time_diff >28800}This response is late{else}Not late{endif}
Don't forget to activate the Gmail command pack to make it work. Keep in mind this only works in Gmail.
5 Likes
From my limited testing at this moment it is broken again. I have developed an alternative that even though it seems brittle and hardcoded has functioned for months without fail:
{=extractregex({site: html; selector=div.gK span:nth-child(2); multiple=no},".*title..(.*). alt")}
Hi Peter,
When you say that gmail-datereceived is broken do you mean that it's not working at all for you or are you referring to the fact that it's returning only the sent date of the first email in a threaded conversation? Because I would like to register that as a bug with the developers. That being said it's still working in the sense that it does pull that date first emails sent date which works for a lot of use cases I suppose. Brilliant job with the workaround, it's is pulling the sent date of the most recent email.
With 'broken', in this context I mean that it does not return any value. If I set a default, it will return that default and if left blank, I get blank. Note: I have threaded view turned on as well. Not sure if that would or should make a difference.
Bummer. It's working fine here though. Chrome 127, TB extension 3.1.5 on both mac and windows, latest released os. This snippet pulls the same value except yours has a comma after the year
{gmail-datereceived: format=lll}
{=extractregex({site: html; selector=div.gK span:nth-child(2); multiple=no},".title..(.). alt")}
