Zapier allows you to connect applications with each other. In Zapier there are two types of applications, the applications that trigger events and those that execute actions.
Applications that trigger events do communicate with those that execute actions.
An example of an event could be when a user enters a task in the Trello backlog.
An example of action could be to send an SMS through 360NRS.
In this way we could send an SMS when someone introduces a task in the Trello backlog indicating which task has been added, on what date, to whom it is assigned, etc.
360NRS is an application capable of sending SMS when any event of any application occurs with all the information that the application provides.
For this integration to work properly it is necessary to bear in mind the following previous considerations:
You must have a 360NRS account and sufficient credit.
Mobile phones must always contain the international prefix. Otherwise, the messages can not be delivered correctly.
The senders can be numeric or alphanumeric. For numeric senders, the maximum length is 15 characters and for alphanumerics 11 characters.
A standard SMS allows a maximum of 160 characters using the GSM7 codification. Characters not supported by the GSM7 codification will be automatically substituted for the most similar character in GSM7. For example: "á" is not supported by GSM7, so the system will change it for an "a", which is the character supported by GSM7. You can find all GSM7 characters allowed in the annex.
Some characters included in the GSM7 count as 2 characters. You can find the extended characters in the annex.
If the length of SMS is greater than the maximum, the system will concatenate the necessary SMS up to a maximum of 5 SMS. (the end user sees it as if it was a single SMS).
The certified SMS have an additional cost.
For the use and integration of the Zapier module with the different services provided on this platform it is necessary to have an account on it, which can be created at:
https://www.zapier.com/sign-up/
using some basic data such as email, name and password.
Illustration 1 - Account creation
When performing the account creation process or Login properly, we will enter the platform by displaying the login page where we are presented with different options for the creation of ZAPs (Integrations between different APIs created in Zapier).
Illustration 2 - Home page with Zaps creation options
As can be seen in illustration 2, to start the process of creating a ZAP we must press the button indicated above (Make a Zap!) and it will be necessary to follow a series of steps broken down below:
1. Direct function to the creation module, where we can select the trigger or initial APP of the ZAP, for the practical case we will use Google Calendar:
Illustration 3 - General view creation of ZAP mode 1
2. When selecting the desired APP, a series of possible integration events will be presented, these vary depending on each of them:
Illustration 4 - Google Calendar available events
Illustration 5 - Google Sheets available events
As can be seen in illustrations 4 and 5, the events available for Google Calendar are different from the events available for Google Sheets and their integration will depend on the needs of the end user.
3. Once the required event is selected (for the practical case, when a new event is created in Google Calendar), we will proceed to the next step in which authentication will be performed in the selected service, in this case Google.
Illustration 6 - Google Authentication
4. In the next step, it will depend directly on the type of service selected above, in the case of Google Calendar, it will be required to select the Calendar associated with the account used in the previous step; in the case of Google Sheets for example, it will be required to select the own Document which will be taken as a reference, as well as the required document sheet.
Illustration 7 - Example Google Calendar selection
Illustration 8 - Google Sheets selection example
5. In the next step of integration, Zapier will present (if possible) templates to manage proof of information and better exemplify what the data brought by these services will be:
Illustration 9 - Google Calendar Test Templates
6. At the end of the configuration of the trigger or initial service (In this case Google Calendar), we will proceed to the integration with the 360NRS APP (it can be found through the search engine provided), which will be found by pressing the button "Add a Step" (See previous illustration).
Illustration 10 - Search 360NRS App
7. When the 360NRS APP in Zapier is selected, the different options currently available for integration will be presented.
SMS sending
The text message sending system uses a request to the 360NRS server and, using each user's own credentials, sends information via SMS. For the proper Zapier integration of the text message sending module, the following steps must be taken into account:
7.1. Action selection
When selecting the action that the 360NRS APP should perform, the option "Send SMS" must be selected.
Illustration 11 - Event selection send SMS
7.2. 360NRS credentials
In the next step, you must press the button to add a new account, with this we can access the login module of the APP, allowing adequate access to the event.
Illustration 12 - Add new 360NRS account
7.3. SMS data
In order to send SMS, the following mandatory fields are required: From, To and Message, and the following optional Campaign name.
From: is the sender that will appear in the message.
To: is the recipient of the message. It is possible to add more than one recipient.
Message: is the message to be sent.
Campaign name: is the name of the campaign that will help us identify the campaign in the panel statistics at https://dashboard.360nrs.com
In any of these fields you can use custom fields that will depend on the application that launches the event. For example, if the application that launches the event is Trello we can use the name of the task in the SMS message, if it is Google Calendar we can use the time of the calendar event, etc.
To use the custom fields, press the button: 
Illustration 13 - Data insertion
As you can see in the previous illustration, you can enter fields from Google Calendar or any App used for this integration, as well as concatenate these with character strings as the following illustration.
Illustration 14 - Custom fields insertion
7.4. SMS test sending
When going to the next step of the integration, templates will be offered depending on the data entered that will allow the user to test their integration before publishing it.
Illustration 15 - Test Zap
The test result will be shown:
Illustration 16 - Test result
7.5. Zap name and activation
Finally, a name will be assigned to this new Zap and it will be activated, ending in this way the integration of 360NRS with any App integrated in Zapier and for this case study with Google Calendar.
Illustration 17 - Name and Zap activation
basic character set| 0x00 | 0x10 | 0x20 | 0x30 | 0x40 | 0x50 | 0x60 | 0x70 | |
| 0x00 | @ | Δ | SP | 0 | ¡ | P | ¿ | p |
| 0x01 | £ | _ | ! | 1 | A | Q | a | q |
| 0x02 | $ | Φ | " | 2 | B | R | b | r |
| 0x03 | ¥ | Γ | # | 3 | C | S | c | s |
| 0x04 | è | Λ | ¤ | 4 | D | T | d | t |
| 0x05 | é | Ω | % | 5 | E | U | e | u |
| 0x06 | ù | Π | & | 6 | F | V | f | v |
| 0x07 | ì | Ψ | ' | 7 | G | W | g | w |
| 0x08 | ò | Σ | ( | 8 | H | X | h | x |
| 0x09 | Ç | Θ | ) | 9 | I | Y | i | y |
| 0x0A | LF | Ξ | * | : | J | Z | j | z |
| 0x0B | Ø | ESC | + | ; | K | Ä | k | ä |
| 0x0C | ø | Æ | , | < | L | Ö | l | ö |
| 0x0D | CR | æ | - | = | M | Ñ | m | ñ |
| 0x0E | Å | ß | . | > | N | Ü | n | ü |
| 0x0F | å | É | / | ? | O | § | o | à |
* Special characters
extended character set| 0x00 | 0x10 | 0x20 | 0x30 | 0x40 | 0x50 | 0x60 | 0x70 | |
| 0x00 | | | |||||||
| 0x01 | ||||||||
| 0x02 | ||||||||
| 0x03 | ||||||||
| 0x04 | ^ | |||||||
| 0x05 | € | |||||||
| 0x06 | ||||||||
| 0x07 | ||||||||
| 0x08 | { | |||||||
| 0x09 | } | |||||||
| 0x0A | FF | |||||||
| 0x0B | SS2 | |||||||
| 0x0C | [ | |||||||
| 0x0D | CR2 | ~ | ||||||
| 0x0E | ] | |||||||
| 0x0F | \ |
* Special characters
basic character set| 0x00 | 0x10 | 0x20 | 0x30 | 0x40 | 0x50 | 0x60 | 0x70 | |
| 0x00 | @ | Δ | SP | 0 | Í | P | ~ | p |
| 0x01 | £ | _ | ! | 1 | A | Q | a | q |
| 0x02 | $ | ª | " | 2 | B | R | b | r |
| 0x03 | ¥ | Ç | # | 3 | C | S | c | s |
| 0x04 | ê | À | º | 4 | D | T | d | t |
| 0x05 | é | ∞ | % | 5 | E | U | e | u |
| 0x06 | ú | ^ | & | 6 | F | V | f | v |
| 0x07 | í | \ | ' | 7 | G | W | g | w |
| 0x08 | ó | € | ( | 8 | H | X | h | x |
| 0x09 | ç | Ó | ) | 9 | I | Y | i | y |
| 0x0A | LF | | | * | : | J | Z | j | z |
| 0x0B | Ô | ESC | + | ; | K | Ã | k | ã |
| 0x0C | ô | Â | , | < | L | Õ | l | õ |
| 0x0D | CR | â | - | = | M | Ú | m | ` |
| 0x0E | Á | Ê | . | > | N | Ü | n | ü |
| 0x0F | á | É | / | ? | O | § | o | à |
* Special characters
** Characters different from GSM
extended character set| 0x00 | 0x10 | 0x20 | 0x30 | 0x40 | 0x50 | 0x60 | 0x70 | |
| 0x00 | | | |||||||
| 0x01 | À | Â | ||||||
| 0x02 | Φ | |||||||
| 0x03 | Γ | |||||||
| 0x04 | ^ | |||||||
| 0x05 | ê | Ω | Ú | € | ú | |||
| 0x06 | Π | |||||||
| 0x07 | Ψ | |||||||
| 0x08 | Σ | { | ||||||
| 0x09 | ç | Θ | } | Í | í | |||
| 0x0A | FF | |||||||
| 0x0B | Ô | SS2 | Ã | ã | ||||
| 0x0C | ô | [ | Õ | õ | ||||
| 0x0D | CR2 | ~ | ||||||
| 0x0E | Á | ] | ||||||
| 0x0F | á | Ê | \ | Ó | ó | â |
* Special characters
** Characters different from GSM
Salesforce
Hubspot
Salesmanago
Klaviyo
360nrs APIs