3 ms·
My 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.
by mik3y 12y ago
My 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..
- eli 12y agoYou could probably have your mail pass through a non-gmail server like http://www.mailgun.com/ http://www.mailgun.com/ first
- toomuchtodo 12y agoYou could use Zapier: https://zapier.com https://zapier.com
- alooPotato 12y agoThe quotas are per user. So you can poll the /history endpoint per user. But yes, this isn't very efficient.
- brousky 12y agohttp://context.io/docs/lite/users/webhooks http://context.io/docs/lite/users/webhooks
- knotty66 12y agoWe currently use Gmail IMAP with IDLE to support this use case. It works great, so I hope they don't drop IMAP without a suitable replacement like webhooks.
- jpb0104 12y agoMy 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.
- hughstephens 12y agoyou've just successfully invented PagerDuty (albeit cheaper and DIYed) ;)