Migrating an App to SendGrid’s Template Engine

Screen Shot 2014-09-10 at 10.45.19 AM

I’ve built a lot of applications to demonstrate what SendGrid can do over the past few years. Recently, I’ve started either updating them, getting rid of really old ones, or replacing them with newer ideas and more modernised examples. With the apps I’ve been updating, the biggest change has been removing all of the inline template code for the emails being generated by the app and moving it to SendGrid’s Template Engine, leaving behind a much cleaner looking codebase and a much more manageable set of templates. Migrating a simple app to Template Engine is really easy, here’s how I did one of mine: Migrating “Oh, Cardless” to Template Engine I built Oh, Cardless to fix the problem of either

Oh, Cardless: My Business Card Email App

Events, Product, Technical
Screengrab of Martyn's use of Oh, Cardless

Due to a recent printing fail, I’ve found myself without any business cards and I’m about to head out to How To Web in Bucharest for 3 days where I’m certain I’ll meet a few folks who ask for my details. Luckily, I work for a company that makes sending and receiving emails from an application easy, so I whipped up this quick app using SendGrid and Heroku to give me a quick autoresponder on my vanity email address that will send a digital version of my business card out to whomever emails that address. It’s quick to turn around and gets my details direct to their inbox. Install Start by cloning the repository: git clone Then follow these

Process SendGrid Events in Real-time with TempoDB

Product, Technical

If you’re a SendGrid customer you will no doubt have taken a look around your statistics dashboard a few times. It’s great isn’t it? Being able to get such a granular view of what’s happening with the email you send through us. I’m fascinated by statistics and analytics so when I stumbled upon Techstars Cloud graduate company TempoDB recently I had to check them out. What is TempoDB? TempoDB is a database designed specifically for storing time series data. This data could be anything really but it’s better used for little pieces of information like thermostat temperatures, network latency or heart rates. Perfect for storing data over extended periods of time, or where the storage requirement is very, very frequent.