We (Streak, YCS11) have been using this API for a few days to build our email snoozing feature ( https://www.streak.com/email-snooze-in-gmail ). The API is really nice to use and makes interacting with Gmail way easier relative to IMAP. I'm surprised they don't recommend using this API to build full email clients. I fully expected that to be one of the core use cases. The reason its hard (currently) to build a mail c…
I use a small google script to "snooze" my emails. I change them to a custom label which the script looks for. The script just runs once a day and sends me a summary of ones with this label if I haven't already replied to them. If it's useful to anyone: http://pastebin.com/c4JvjNef
Gmail API
131–140 of 147 posts
Re: Gmail API
#132My killer app for this needs webhooks, or some sort of event notification when mail arrives. Bonus points for making that condition a stored procedure/filter. Until then I'll probably run out of "quota units" polling the thing..
I then have my Twilio number added as a favorite contact in iOS Phone app thus bypassing the scheduled Do Not Disturb feature. I will continue to get calls every 3 minutes until I answer the call and press 5. That's my "shit hit the fan" alarm.
Re: Gmail API
#133Earlier quoted context omitted.
If anyone wants to snooze email without auth'ing your Gmail account, here's one I built in 2008 that's still going strong. http://hitmelater.com/ It costs $30/yr for the high-end service but send me a note and I'll give you a link to signup for free.
One of the key differences between your solution (and fut.io, followup.cc) and our snooze is that we also do the conditional "but don't bring this back if there's a reply on this thread". Along with being able to "snooze" an email you're sending out with the conditional. This brings us much more in line with Boomerang's main functionality. Plus our snoozing functionality is 100% free, no matter how many you schedule,…
Re: Gmail API
#134My killer app for this needs webhooks, or some sort of event notification when mail arrives. Bonus points for making that condition a stored procedure/filter. Until then I'll probably run out of "quota units" polling the thing..
My solution. Gmail Filter -> Forward to Mandrill Email Address -> Mandrill Webhook -> POST to HTTP endpoint that will issue a Twilio voice call to my phone. I then have my Twilio number added as a favorite contact in iOS Phone app thus bypassing the scheduled Do Not Disturb feature. I will continue to get calls every 3 minutes until I answer the call and press 5. That's my "shit hit the fan" alarm.
Re: Gmail API
#135We (Streak, YCS11) have been using this API for a few days to build our email snoozing feature ( https://www.streak.com/email-snooze-in-gmail ). The API is really nice to use and makes interacting with Gmail way easier relative to IMAP. I'm surprised they don't recommend using this API to build full email clients. I fully expected that to be one of the core use cases. The reason its hard (currently) to build a mail c…
Seriously, I'm not trolling - why would you want to snooze an email (hide it from inbox and have it come back later - I had to go look it up)? Apart from that I like the API idea - I have been beta testing my own personal document scanner - I email myself photos of bills and receipts and file them under the subject line (ie file-as bills.electricity) - it beats the hell out of a document scanner I never used. Anyway…
Re: Gmail API
#136Earlier quoted context omitted.
> Seriously, I'm not trolling - why would you want to snooze an email (hide it from inbox and have it come back later - I had to go look it up)? Example that happened to me yesterday: a colleague asks me for a piece of information that I know I can find in a book at home, but I'm at work. I snooze the email so that it doesn't fall at the bottom of my inbox, and so that it gets redelivered when I'm home and can access…
Hypothetically, wouldn't really aggressive archiving accomplish the same task? Have a 0-email inbox, and if you get something that you can't address immediately (but you can take care of later in the day), then you leave it in the inbox. In the meantime, anything you can act on in some way gets acted upon and then archived. By the end of the day you would ideally have just that email in your inbox (and even in a real…
Re: Gmail API
#137I can't believe how many people are stoked about this. If you look at https://developers.google.com/gmail/api/auth/scopes , basically apps can do a combination of a) have full control, b) read everything, c) do everything but delete emails, or d) read/write/send drafts. Granting that level of access with no fine-grained control to 3rd party apps seems insane to me. I predict at least a couple major security incidents…
While I somewhat agree with you, it's not as though these problems didn't already exist with IMAP. I think a better way of looking at it is this is the first step in removing the password from 3rd party access. Maybe at some point in the future they'll add more fine-grained access, but for now removing the credentials from the process seems like a good first step. Not sure why they really need an API though. Seems to…
Re: Gmail API
#138We (Streak, YCS11) have been using this API for a few days to build our email snoozing feature ( https://www.streak.com/email-snooze-in-gmail ). The API is really nice to use and makes interacting with Gmail way easier relative to IMAP. I'm surprised they don't recommend using this API to build full email clients. I fully expected that to be one of the core use cases. The reason its hard (currently) to build a mail c…
If anyone wants to snooze email without auth'ing your Gmail account, here's one I built in 2008 that's still going strong. http://hitmelater.com/ It costs $30/yr for the high-end service but send me a note and I'll give you a link to signup for free.
Re: Gmail API
#139Earlier quoted context omitted.
Whether they drop support or not, clearly their idea here is to replace it. Replacing globally supported open standards with proprietary APIs is one of the things people hated about Microsoft in the past. Why does Google seem to get a pass from so many developers for this type of behavior? Or worse, get applauded for it? If the argument is IMAP is out of date and crappy, then OK, let's make a new standard. Unilateral…
Having spent one year of my life trying to replicate Gmail's interface in a desktop app through IMAP (www.betterinbox.com), I can say with confidence that IMAP is completely unsuited for the Gmail paradigm. If we had this API back when we were working on BetterInbox in 2011, our lives would have been much easier.
Re: Gmail API
#140Earlier quoted context omitted.
If anyone wants to snooze email without auth'ing your Gmail account, here's one I built in 2008 that's still going strong. http://hitmelater.com/ It costs $30/yr for the high-end service but send me a note and I'll give you a link to signup for free.
Sorry I'm super dumb :( what does 'snoozing' your email mean?