The GridIron Mashup (SendGrid + Iron.io = love, flowers, ice-cream, and profits) Kunal Batra May 17, 2013 Partnerships, Product // SUMMARIES ?> Mashups tend to showcase interesting use cases of APIs in which the sum is greater than the parts. They offer increased productivity at reduced costs. Work flows that once required additional resources now become superfluous. By leveraging multiple SaaS solutions in a single application, we get all this plus the technology benefits of two focused providers. What better company to showcase such a mashup than Iron.io? Their message queue and worker APIs allow 3rd parties to create asynchronous and scalable architectures. Also, just like SendGrid they have webhooks that allow for an event driven workflow. Introducing GridIron SendGrid and Iron.io have been friends for a while, but recently we met up with them at a hackathon and got into an interesting discussion. We were talking about all the beneficial ways in which we could use our services together and decided it would be best to share these awesome examples with our customers. So today, we are publishing the examples we worked on to showcase some potential use cases of combining SendGrid with Iron.io. GridIron consists of five main examples right now: Hello, SendGrid: a simple demonstration of using IronWorker to send emails using SendGrid Queue-Based Emailing: an evolution of Hello, SendGrid that uses a pull queue to give you a more scalable, robust email sending solution that gives you full control over how quickly emails are sent out. Fanout: an example that shows how to use IronMQ’s push queues to fan out data to multiple processors. In this case, two IronWorker workers receive the data, and they send a text message through Twilio and send an email through SendGrid. Github Notifications: an example that shows how to use Github’s webhooks to trigger IronWorker workers. The workers send emails to the repo owner whenever specified branches are committed to, and ignores the other notifications. Markov Bot: the most powerful demonstration we could think of, the Markov Bot will accept an email from the Inbound Parse API, use it to queue up a worker, and process that email. The bot will read your first line, and try to guess the next word you’d use, just like your phone does. It then emails back your line, with its guess appended to the end. It’s an email bot that was written in about 200 lines of Python. Benefits Normally when you think of services that provide both message queues and transactional email, Amazon comes to mind. However, these services struggle when it comes to webhooks. Amazon SES currently does not have the capability to receive emails. Also to implement webhooks you would have to setup endpoints in EC2 and that requires a lot of overhead. With GridIron you can take advantage of this event-based workflow immediately. We’re really excited to share GridIron with you and we hope our examples are helpful. A big “thank you” to Iron.io for the great collaboration and if you have any ideas for future mashups, leave us a comment below.