Transactional email for developers

Features


NO ACCOUNT NEEDED

No register forms, not another password to forget, not another account to manage.

NO CUSTOM TEMPLATE TAGS

You don't need to learn/develop another substitution/merge tag's set. Use {{handlebars expressions}} for your templates.

JUST POST IT

Just a POST request with a JSON payload and you're done!

USE IT FROM WHEREVER YOU LIKE

Use postman, curl or your own project to make a POST request to your ´s webhook with the JSON payload for your template. That´s all!

TEST IT ON DIFFERENT ENVIRONMENTS

You can now test your transactional emails using a NON-production environment.

IT'S FREE

Last but not least, you don't have to pay a cent!

Price Options

Choose your flavor!


FREE
  • BASIC
  • Manage your s from our graphic interface
  • Unlimited emails
  • Handlebars templating supported
  • Development and production environtments
  • Support for the principal transactional email providers
TRY IT
ENTERPRISE
  • $99 / one time fee
  • BASIC FEATURES PLUS:
  • 1 year updates included
  • AWS On premise setup
  • White label
  • Email support
GET IT

Too good to be true?

Take a look a at this Demos integrated with some programming languages and tools.


Still not sure?

Maybe this could help


Is this a real problem?

We know, we thought the same, but.. just think about it:

  • How many projects you've worked on, need to send transactional email?
  • How did you solve that problem? Services with custom object serialization? custom made template manager? hardcoded subjects?
  • How do you test transactional email? Two words, boring and slow. We have better things to do.
  • Do you have a development environment? Do you need to build different services, configuration, subject, body than production environment?
  • How do you deploy changes? Do you have to re-deploy your project or do changes in databases?
  • Do you remember your boss asking for subject changes, content changes, space changes and your excitement for doing them? another deploy for “stupid” changes!

Don't you think there is a better way? Did we get used to this problem?

How do we solve the problem?

First, accepting that we had underestimated the problem for 16 years, then:

  • We built a common wrapper for the transactional email integration. Just post a json to an endpoint.
  • Send the json as you want. No more specific wrapper or "merge variables".
  • You can use handlebars notation in all of the email template fields (from, to, subject, body)
  • Using our Test Provider, you can code the functionality, test it and then think about which transactional email service to use.
  • There is a development environment available within every hook, so, you can even change the transactional email provider without crashing production.
  • Yes, you can switch between different transaction email service providers whenever you like. No need to re-deploy your app!
  • You can test every hook with postman, curl or any service that allows you to make a json post request.
  • Your boss or the marketing guy are able to update that template!

I'm the boss, why do I care?

Just make the math, how much wasted time on all the email stuff? Time is gold. Maybe you are paying an expensive developer to spend time solving the same problem in every project.

Why Haboob?

Let's see what Wikipedia says about it.

Contact Us

Reach Us Here

We're just developers who love to make the things easier.


Email: contact@haboob.com

Let us know what you're wondering.

P.D. We eat our own dog food.