Transactional Email by Mandrill
Filemaker’s “Send Mail” script step allows you to send simple plain text emails. It works great if it’s for internal purposes like notifications and reminders, but if you want to send emails for marketing purposes, like campaign and coupon offers, then Mandrill is probably a better option. Mandrill allows your to send pretty html based emails and keeps track of how many you’ve sent within a period of time, who opened it, unsubscribed etc. If you ever decide to use Mandrill, below are some tips and guides on how to integrate Mandrill with Filemaker.
There’s no cost to sign up for Mandrill. The first 32,000 emails you send are free every month. Depending on your usage, you can always add credits to your account if it exceeds 32,000 sends. Once you create an account, go to SMTP & API Info tab in Settings and create an API key. You can create multiple API keys if you plan on using it for different purposes. Secondly, you need to create a template in Mandrill. You can create a template using html code or create a template in MailChimp using their template editor and simply send it to Mandrill since it’s owned by the MailChimp. MailChimp has a width restriction of 600px, if you’re not so concerned about it I would recommend using MailChimp Editor. It’s simply faster and allows non-coders to create simple templates too. In your templates, you can set up multiple merge tags (a placeholder for the information you want to pass through the api calls) to dynamically set the content. Here’s more info on merge tags.
Just like any other API calls, you’ll need the BaseElements Plugin.
Once you got the BaseElements Plugin installed, I would recommend to verify the api key first before continuing on with the templates calls. That way you can eliminate the possibility of having an invalid api key. Below are examples on how to verify your api key and making a template request in the format of JSON.
If you include merge tags in your template, simply add the global_merge_vars parameter in your request. Another thing to watch out for is the “&” in your requests. Any variables containing the “&” will cause the request to end prematurely. For example, if the variable $Company_Name is set to “Glass & Windows”, only “Glass “ will be passed in the call and all the global_merge_vars after that will be ignored. To solve this, simply substitute the “&” with “%26”.