Note: Please remember that currently, the information entered in the form is also be stored in the internal application database so that anyone can see the tokens that are being used. It would be pretty easy to add  a small routine to the script to delete the data after it has been sent to ESME.

The code to create the esme message is very simple and is linked to the submit button.

MyMap = map(); Response = postUrl(”http://api.esme.us/esme/api/login?token=” + input.Token, MyMap);

Response = postUrl(”http://api.esme.us/esme/api/send_msg?message=” + input.Message + “&tags=” + input.Tags + “&via=zoho”, MyMap);

Response = getUrl(”http://api.esme.us/esme/api/logout“);

What is cool is that there is also the possibility to use the “out-of-the-box” functionality of ZohoCreator applications to import information from Excel to fill internal database tables.  Thus, you can rapidly create a series of ESME messages. The first ESME spammer is born.

Why is the integration interesting:  Zoho has a series of business applications (CRM, Invoice, etc.) where it might be relatively easy to integrate ESME and micro-blogging into this environment.  I could imagine interesting scenarios where a company has some applications hosted by Zoho and some internally – ESME could act as a information bridge between both environments.