SkizmoInc Blog

Every application sends email these days – we send email to our customers and to ourselves.  Again, we wanted to manage something that wasn’t up to our expectations.  We have many applications that send emails and a lot of times the emails are just variations of emails in our other applications.  We don’t like duplication, we love reuse and we love simplicity.  For us, MailerIt was the answer.  To provide us with one place for all of our email templates and smtp settings.  We simply use the MailerIt API now to pick our template and specify any keyword values we setup in the template.

Sample usage of MailerIt from a rails application -

# call from anywhere in your application - models, controllers, views, libs ...
Mailerit.create(:email_template_name => "MailerItTest",
                :smtp_setting_name   => "DefaultSettings",
                :params => {:email       => "myemail@blarg.com",
                            :username    => "someonesusername",
                            :another_var => "somevalue"})
                

Sample usage of MailerIt from any other application, tool, anything -

curl -i -X POST \  
  -H "Content-Type: application/xml" \
  -H "X-MailerItKey: YOUR_KEY_GOES_HERE" \
  -d "<mailerit>
        <email_template_name>notice_to_dev</email_template_name>
        <params>
          <email>myemail@blarg.com</email>
          <username>someonesusername</username>
          <another_var_used_in_template>somevalue</another_var_used_in_template>
        </params>
      </mailerit>" \
http://mailerit.com/mailerits.xml