Number To Word Converter API converts a number to words in English or many other languages. Zoho Books & Zoho Invoice provides a straight forward solution for converting an Invoice Total into Words missing on some key components of the description.

The main goal for this Hack is to have a more precise Number to Word converter for an Invoice. The solution provides number to Word conversion & includes the most needed cents details at the end along with the currency. ( 00 / 100 USD ) just like a check would show. 

Get the Script in our Deluge Scripts Library.

Zoho Creator does have an automatic weekly and monthly backups of all database details, but there is no way to create a daily backup. A solution is to leverage Dropbox API to send a copy of all records in a view to dropbox on a daily basis.

The Solution...

The solution is quite elegant. First, you need to send an email to a Form that will store the attachment you want to backup. You would then need a clever iteration setup to consider large number of records in a view. 

Below you can get the script for the file creation.

//FILE CREATION SCRIPT

void Dropbox.fileCreation()
{
getMaximumAuto = YOUR_FORM_NAME[ID != null].maximum(Auto_Number);
maxLoopN = getMaximumAuto / 3000;
i = 0;
for each  rec in YOUR_FORM_NAME
{
if(i >= maxLoopN)
{
break;
}
else
{
start = i * 3000;
end = (i + 1) * 3000;
sendmail
[
from :zoho.adminuserid
to :"formname@forms.zohocreator.com"
subject :"Records from zoho " + zoho.currenttime + " " + i
message :"Dropbox"
Attachments :view:YOUR_VIEW_NAME[Auto_Number >= start && Auto_Number <= end] as XLS
]
}
i = i + 1;
}
}

Second we need to send the file to Dropbox by executing the SendfiletoDropbox function on Add on Success of YOUR_VIEW_NAME 

getData = Dropbox[ID == input.recID];

Get the full script to integrate the Dropbox API to your Zoho Creator databases from our Deluge Scripts Library. If you need a Dropbox Account open one for free here. Dropbox Sign Up

The more you know about your customers, the better you can engage them with targeted, relevant content that gets higher response rates. TowerData Email Intelligence provides valuable demographic, interest and purchase data on 80% of email or postal addresses in batch or via a real-time API. Within minutes, you can learn who your customers are, what they're interested in and their preferred point of contact. Use Email Intelligence to:

• Make a Killer First Impression: Use our data to immediately appeal to a new lead based on his or her characteristics and interests.
• Personalize and Target Offers: Customize subject lines, offers, images, calls to action, landing pages and more using enhanced data.
• Create Context for Behavior: Understand the intent behind customer action by supplementing behavior-based data with demographic and lifestyle data.
• Better Segment Your List: Identify the segments of your customer database that will be most responsive to your message.

Available Customer Database Enhancements

Keeping your email list clean and accurate allows you to promptly connect with new leads. Enriching your list with consumer data helps you create a more personalized experience for leads. With TowerData’s API, you can do both...in real time.

//GETurl

resp = getUrl("https://api.towerdata.com/v5/ev?api_key=e506YOURAPIKEY0890f752f15&email=" + Email);

We’re quite excited today to unveil Zoho CRM 2018, our smartest release ever. We are bringing to the market multiple innovations, improvements and additions to Zoho CRM. If we were to describe all of them in a single word, it would certainly be ‘smart’. Why?

At just one year old, Zia learns to speak

Zia, the AI-powered sales assistant, was born a year ago. Today, Zia learns to speak: We’re introducing Zia Voice, the first conversational assistant for sales teams. Zia can now interact with you through both voice and chat messages to perform any action inside Zoho CRM. Want to know your schedule for the day? Just ask Zia. On the go and want to check if you have enough inventory of a particular product before your next customer visit? Just ask Zia. Want to quickly mark a deal as Closed-Won after hanging up with the customer? Just ask Zia to do it for you.

What else can you #AskZia? From questions like new leads created in the past week to monthly sales forecasts, Zia can help you do anything you can do in the CRM, all through voice or chat. Zia comes with a pre-defined set of intents for you to choose from, but you can also write your own intents to enable any sort of actions you might want Zia to help you with. You interact with Zia either through the voice interface in the Zoho CRM app in iPhone or Android, or through the chat bar in Zoho CRM in your desktop web browser.

As awesome as Zia Voice is, it is not the only thing we’re unveiling today. Zia has gotten smarter in many other ways as well.

Zia now predicts closure rates for leads and deals 

Zia intelligently analyzes your activities in a particular deal, takes into account your win history and other factors, and comes up with a prediction score for each lead or deal. This score, on a scale of 0 to 100, is also available as a dynamic filter so you can quickly focus on the deals that make the most sense for you to spend your time on.

Zia can read your email’s sentiment

Every email a customer sends to you carries some sentiment. Zia can automatically analyze the tone behind every new email you receive. Zia tells you if your customer is happy or upset based on the content of the email. You have happy customers? Acknowledge them. You find them disappointed with your product or service? Get your best sales rep on it. Got a lot of emails you need to sort through quickly? You can also use this sentiment analysis to focus on the emails that require the most immediate attention. Even better, you can also train Zia to identify particular phrases or sentiment to improve the accuracy of her predictions.

Best time to contact, workflow performance, and lead enrichment

Zia now proactively reminds you when the best time to contact a particular person approaches, so you no longer miss that window or have to check on every record. In addition, Zia helps you decide whether the changes you are making to particular workflows in your CRM are producing positive results, or if the percentage of records going through the workflow changes significantly. Finally, Zia also helps you fill in your prospects details faster by automatically retrieving contact details from public sources and letting you decide whether you want to use that contact information.

Introducing Catalyst – the hyper-customization platform for businesses

This is another piece of news that we’ve been anxiously waiting to tell you about. Enterprise businesses have their own unique needs, which typically surpass the customization (including custom fields and modules) option you have in packaged software.

We started Catalyst with the vision to allow enterprises to easily build custom applications on top of Zoho CRM. For example, some reps out on the field do not need to see all the CRM data the standard apps comes with – and the app might not match the flow in which they accomplish their daily jobs. A custom CRM app cuts through the clutter and puts the information they need to see in front of them, in the way they need to interact with it.

But, how easy is it to build that application? How do you ensure the app doesn’t break the business rules contained in your CRM? Once you build the app, how do you distribute and manage it in all the relevant devices (whether you own them or not)? And finally, if the app needs some back-end code to perform specific tasks, where do you deploy and manage that code – and how do you make sure it scales?

Those are the kinds of problems that Catalyst solves. Catalyst includes mobile and web SDKs, MDM (mobile device management)  and perhaps most importantly, serverless infrastructure that runs–and scales–your back-end code.

Catalyst is apt for the more technically-inclined. We’ll be discussing it in more detail at a future date.

Blueprint for Zoho CRM ads SLA and checklist enhancements

Blueprint already helps you build and execute your sales process in a way that both scales and is easy for reps to follow. With this new update, admins can now specify the maximum time a record should spend in a stage before it gets escalated. Now, you can also specify a checklist of items sales reps need to complete before moving a record to the next stage.

Paint your own view on Canvas

Each business has a unique way to visualize its deals or prospects. For example, for one business it might be a picture of a property, for another, the picture of an antique car, and for another it might be a picture of its most important customers. That’s why we have created Canvas, for businesses to visually build their lists with images, text, color, and much more. The Canvas designer makes it easy to drag-and-drop components onto the screen and build new custom visualizations.

A new way to visualize your business performance

With 6 pre-built dashboards and 5 intelligent components to choose from, you can redefine the way your team draws data. The pre-built dashboards help you know about your email analytics, lead insights, and overall organization overview. You can also customize your dashboard according to your business needs. Let’s introduce you to some of the dashboard components you can choose from.

Create charts without the need of reports. See KPIs that give you a complete picture of your sales essentials like current growth indices. There are funnels that help track your pipeline giving you visibility on where your prospects drop off, or that can tell you about your churn rates. You can compare the performance between any two variables like your sales metrics, or even compare peer-to-peer performance. The Target Meter helps you set targets for yourself and your team so you know where you’re headed. And finally, there are Anomalies, powered by Zia, that help you map your current trends as compared to expected results.

But wait… there’s more!

This release is incredibly big and we can’t do justice to every single thing that we’re including in it. So here are a few more items that we thought you should be aware of:

• Portals. Make your customers, vendors, and partners part of your sales process. Create separate portals for your customers, partners, or vendors and choose what data you want them to have access to. It’s not just minimizing back-and-forth over email or self-service. When you give your external stakeholders access to portals, you make them an integral part of your business processes, including triggering workflows and having access to the updated information.
• Encryption At Rest (EAR). You are now able to designate up to 10 fields that will be encrypted at rest (i.e. in the database in Zoho’s servers). And just to clarify – as usual, all traffic, including fields that at not encrypted at rest, continues to be securely transmitted and encrypted between Zoho’s servers and your browser (or app).
• Translations. Zoho CRM now supports 24 different languages. With this release, we also enable you to translate any custom fields or picklist values that you’ve created in your default language.

We hope you find something for your business in Zoho CRM 2018. We also want to ask a favor; please let us know what you think about all the features you read about on Twitter or Facebook using the hashtag #ZohoCRM2018. You can also talk to us in the comments below.

Perhaps you have wondered how predictable machines like computers can generate randomness. In reality, most random numbers used in computer programs arepseudo-random, which means they are generated in a predictable fashion using a mathematical formula. This is fine for many purposes, but it may not be random in the way you expect if you're used to dice rolls and lottery drawings.

RANDOM.ORG offerstrue random numbers to anyone on the Internet. The randomness comes from atmospheric noise, which for many purposes is better than the pseudo-random number algorithms typically used in computer programs. People use RANDOM.ORG for holding drawings, lotteries and sweepstakes, to drive online games, for scientific applications and for art and music. The service has existed since 1998 and was built by Dr Mads Haahr of the School of Computer Science and Statistics at Trinity College, Dublin in Ireland. Today, RANDOM.ORG is operated by Randomness and Integrity Services Ltd.

As of today, RANDOM.ORG has generated 1.51 trillion random bits for the Internet community. You can easily integrate this API to your zoho creator database from our Deluge Script Library and use it in a diverse universe of random options or you can follow the HTTP interface instructions below to set it up yourself.

HTTP Interface Description

RANDOM.ORG is a true random number service that generates randomness via atmospheric noise. This page explains how to interface to the service via the Hyper-Text Transfer Protocol (HTTP). There is also the HTTP Client Archive, which contains clients that other people have written.

This page contains documentation for the Integer Generator, the Sequence Generator, the String Generator and the Quota Checker, which allows you to examine your current bit allowance.

All the interfaces on this page return HTTP status code 503 (Service Unavailable) in the case of errors and code 200 (OK) when successful. Not all languages allow you to access the HTTP status codes in a straightforward manner. A reasonable workaround is to look for the string "Error:" (don't forget the colon) as the first line of the response. This will work for all the generators on this page, including the String Generator (which could by chance produce the string "Error" in a successful response, but which cannot produce the colon character).

Please note that the old CGI scripts (randbyte, randnum, etc.) are no longer supported and you should use the ones described below instead. In particular, the old scripts do not return the 503 status code in case of errrors (they return the 200 response code in all cases), so please use the new ones instead.

The Integer Generator will generate truly random integers in configurable intervals. It is pretty easy to write a client to access the integer generator. The integer generator accepts only HTTP GET requests, so parameters are passed via encoding in the URL.

Parameters

Success

If no error occurred, a HTTP status code of 200 (OK) will be returned. The MIME type will be set in accordance with the format parameter that was specified in the request. The body of the response will contain a list of numbers. If XHTML was requested (via the formatparameter), the numbers will be formatted inside a <pre></pre> element. If plain text was requested, the numbers will be separated by line feeds. Multiple columns will be separated by tab characters.

Errors

If an error occurred, a HTTP status code 503 (Service Unavailable) will be returned. The MIME type will be set in accordance with the format parameter that was specified in the request. The body of the the returned page will contain the string "Error:" followed by a string with further details. If XHTML was requested, this message will appear somewhere in the document inside a <p><p> element. If plain text was requested, it will appear on the first line in the document.

The types of errors can vary. Errors will occur if you specify invalid parameters but can also occur because the server is temporarily overloaded. Reasonable behaviour for a client is to look for the "Error:" string in the page returned by the server and print out the whole line if the string was present. When I get around to it, I will provide a full list of possible errors on this page. In the meantime, feel free to experiment ;-)

You probably want to make sure your client can deal with the full range of HTTP response codes, or at least 200, 301 and 503.

Example

Issuing a HTTP GET request for the following will generate a series of ten integers in the [1,6] interval, suitable as dice rolls, for example in a backgammon game. We are requesting a plain text document to be produced, such that our client can easily parse the numbers. Finally, we are requesting a new randomization.

https://www.random.org/integers/?num=10&min=1&max=6&col=1&base=10&format=plain&rnd=new

The Sequence Generator will randomize a given interval of integers, i.e., arrange them in random order. It is pretty easy to write a client to access the sequence generator. The sequence generator accepts only HTTP GET requests, so parameters are passed via encoding in the URL.

Parameters

The sequence requested must 10,000 numbers or shorter in length, i.e., max-min+1≤1e4.

Success

If no error occurred, the returned page will contain all the integers in the interval in random order. If XHTML was requested, the numbers will be formatted inside a <pre></pre> element. If plain text was requested, the numbers will be separated by line feeds. Multiple columns will be separated by tab characters.

Errors

If an error occurred, a HTTP status code 503 (Service Unavailable) will be returned. The MIME type will be set in accordance with the format parameter that was specified in the request. The body of the the returned page will contain the string "Error:" followed by a string with further details. If XHTML was requested, this message will appear somewhere in the document inside a <p><p> element. If plain text was requested, it will appear on the first line in the document.

The types of errors can vary. Errors will occur if you specify invalid parameters but can also occur because the server is temporarily overloaded. Reasonable behaviour for a client is to look for the "Error:" string in the page returned by the server and print out the whole line if the string was present. When I get around to it, I will provide a full list of possible errors on this page. In the meantime, feel free to experiment ;-)

You probably want to make sure your client can deal with the full range of HTTP response codes, or at least 200, 301 and 503.

Example

Issuing a HTTP GET request for the following will return the numbers from the interval [1,52] in random order, for example to shuffle a deck of cards. We are requesting plain text and a new randomization, as in the previous example.

https://www.random.org/sequences/?min=1&max=52&col=1&format=plain&rnd=new

The String Generator will generate truly random strings of various length and character compositions. It is pretty easy to write a client to access the string generator. The string generator accepts only HTTP GET requests, so parameters are passed via encoding in the URL.

Parameters

Success

If no error occurred, the returned page will contain a list of strings. If XHTML was requested, the strings will be formatted on separate lines inside a <pre></pre> element. If plain text was requested, the strings will be separated by line feeds.

Errors

If an error occurred, a HTTP status code 503 (Service Unavailable) will be returned. The MIME type will be set in accordance with the format parameter that was specified in the request. The body of the the returned page will contain the string "Error:" followed by a string with further details. The presence of the colon allows you to distinguish this from a randomly generated string. If XHTML was requested, this message will appear somewhere in the document inside a <p><p> element. If plain text was requested, it will appear on the first line in the document.

The types of errors can vary. Errors will occur if you specify invalid parameters but can also occur because the server is temporarily overloaded. Reasonable behaviour for a client is to look for the "Error:" string in the page returned by the server and print out the whole line if the string was present. When I get around to it, I will provide a full list of possible errors on this page. In the meantime, feel free to experiment ;-)

You probably want to make sure your client can deal with the full range of HTTP response codes, or at least 200, 301 and 503.

Example

Issuing a HTTP GET request for the following will generate a series of ten strings of length eight, suitable for example as randomly generated passwords. We are specifying unique We are requesting a html text document that will look nice in a web browser. Finally, we are requesting a new randomization.

https://www.random.org/strings/?num=10&len=8&digits=on&upperalpha=on&loweralpha=on&unique=on&format=html&rnd=new

The Quota Checker allows you to examine your quota at any point in time. The quota system works on the basis of IP addresses. Each IP address has a base quota of 1,000,000 bits. When your client makes a request for random numbers (or strings, etc.), the server deducts the number of bits it took to satisfy your request from the quota associated with your client's IP address.

If your client issues a request for random numbers while its quota is negative, the RANDOM.ORG server will return a 503 error response as described below. If your client's quota is greater than or equal to zero, the server will fully complete the client's next request for random numbers, even if the request will result in the client's quota becoming negative. Hence, no partial responses will be sent as a result of your client exhausting its quota; the server will either return a full response or an error response.

Every day, shortly after midnight UTC, all quotas with less than 1,000,000 bits receive a free top-up of 200,000 bits. If the server has spare capacity, you may get an additional free top-up earlier, but you should not count on it. If you need extra bits urgently (or require many bits) you can purchase once-off top-ups from the Quota Page.

The Guidelines for Automated Clients specify that you should use the Quota Checker periodically to verify that your client is not issuing requests for random numbers to the RANDOM.ORG server when its quota is exhausted. For most clients, the easiest solution is to interleave the quota checks with the requests for random numbers. If a quota check returns a negative value, your client should back off for at least ten minutes before issuing another quota check. Only when the quota check returns a zero or positive value, should your client resume its requests for random numbers. If you want to build a really well-behaved client, you can implement an exponential backoffalgorithm with a maximum delay of 24 hours.

The number of random number requests your client can issue before doing a quota check depends on how many bits each random number requests requires to satisfy. See the FAQ for details about how to estimate this. As a rule of thumb, your client should probably issue a quota check every time it thinks it has used its daily free top-up. This will mean the client can continue issue requests in case things are better than expected (perhaps it has received a free top-up) but that it will back off in case its quota is exhausted.

The Quota Checker only accepts HTTP GET requests, so parameters are passed via encoding in the URL.

Parameters

Success

If no error occurred, a HTTP status code of 200 (OK) will be returned. The MIME type will be set in accordance with the format parameter that was specified in the request. The body of the response will contain information about the remaining allowance for the IP address in question. If XHTML was requested (via the format parameter), the information will be nested inside several XHTML elements. If plain text was requested, the current quota level will be returned as a single number followed by a single newline.

Errors

If an error occurred, a HTTP status code 503 (Service Unavailable) will be returned. The MIME type will be set in accordance with the format parameter that was specified in the request. The body of the the returned page will contain the string "Error:" followed by a string with further details. If XHTML was requested, this message will appear somewhere in the document inside a <p><p> element. If plain text was requested, it will appear on the first line in the document.

The types of errors can vary. Errors will occur if you specify invalid parameters but can also occur because the server is temporarily overloaded. Reasonable behaviour for a client is to look for the "Error:" string in the page returned by the server and print out the whole line if the string was present. When I get around to it, I will provide a full list of possible errors on this page. In the meantime, feel free to experiment ;-)

You probably want to make sure your client can deal with the full range of HTTP response codes, or at least 200, 301 and 503.

Examples

Issuing a HTTP GET request for the following will return the quota level for the machine issuing the request. We are requesting a plain text document, such that our client can easily parse the number. If you are writing an automated client that downloads numbers or strings from RANDOM.ORG, you can use this type of request to make the client check its quota level. If the value returned is negative, your client should back off as described in the Client Guidelines.

https://www.random.org/quota/?format=plain

The following example examines the quota for the machine whose IP address is 134.226.36.80, which happens to be address of the RANDOM.ORG server. Again, we are requesting a plain text document, so the client can easily parse the value.

https://www.random.org/quota/?ip=134.226.36.80&format=plain