Pabbly SMS App.
SMS Everyone's simple Pabbly app will have you
sending messages in under 5 minutes.
Pabbly Connect is a simple middleware platform for connecting apps together without having to write any code.
With our Pabbly SMS sender app, you can easily connect SMS messaging to thousands of applications.
For example, you could send a welcome SMS whenever you get a new customer on Shopify.
You can even receive messages back from the end user and push that data into your application one-by-one.
Connecting the SMS Everyone App to your application in Pabbly
Below is a quick video showing all the steps to get our Send SMS Action running. Or if you prefer to read, all steps are outlined below.
Before you start
Do you have an SMS Everyone account?
If not, sign up and we'll get you running in a few minutes.
Be sure to mention that you want to connect to Pabbly when you sign up
Create a Workflow in Pabbly
Log in to Pabbly Connect
On the dashboard top right, click the 'Create Workflow' button
Give the workflow a name and click 'create'
Choose a Trigger
Under step 1. type in the search box the name of the application that you want to connect to SMS Everyone. This will be your trigger.
In this case we are going to use Google Calendar
Now that you've selected your trigger app, select your Trigger Event.
For this example, we are going to select 'New Event'...
Imagine that you are on a sales team and you want to receive an SMS every time your appointment booker creates a new appointment for you.
Select 'New Event' and press the 'connect' button
You have the option to pick which Google calendar you want to connect to.
(We think that this only applies if you have more than one)
Create a Trigger Event for Pabbly to use.
To test the workflow and set up the SMS Action , you'll need to provide Pabbly with some valid data.
Log in to your Google Calendar and create a new Calendar event a few hours in to the future. Be sure to give it a name.
Now go back to Pabbly and on the Google Calendar trigger app, press 'Save and Send Test Request'
You'll see that it generates a very simple response with all the fields from your calendar appointment all neatly lined up one above the other.
Connect the SMS Everyone Action
Now we scroll down to step 2 where we add the SMS Everyone app as an action.
Click in the box that says '2. Choose Your Next Application : Action'
In the 'Choose App' search box, type 'SMS Everyone'
Select the 'SMS Everyone' app.
Select 'Send SMS' as the action event.
Then press the 'connect' button.
Click the 'Add New Connection' tickbox
Enter your SMS Everyone username and password exactly as we gave it to you when you signed up
Configure Your Message Text
Message Text
In the 'Message Text' box, type whatever you would like to receive as the message text. You can click on any of the fields from the Google calendar appointment and it will add that information into the body of the message wherever you want it. Like this:
So this message above will send an SMS for this appointment that reads:
Hi Dave, Sally has booked you another appointment. Details: Meeting with Kelly at Melbourne City, Melbourne, VIC, Australia
Origin
Next enter the origin exactly as we gave it to you when you signed up. In New Zealand, this will be a 4 digit number ONLY.
If you add an origin that is different to what we gave you, it will not work.
Destinations
Enter the mobile number/s that you want to receive the message.
Enter the numbers in international format without the + sign.
eg 022123456 would be entered as 6422123456
For multiple numbers, separate with a comma.
If you want the message to go to a contact in your trigger app (eg the person you are having the meeting with) and the app has that field available to use, click that field to add it to the Destinations field.
In this case below, I have stored the recipient's mobile number in the 'description' field in Google Calendar. So I can click on 'Description' and it will now send an SMS to the mobile number that is in the Google Calendar appointment's description field.
But to stick with our original design of sending the message to a staff member or myself, lets enter the mobile number manually and save. Note - the example below is an Australian number.
Click the 'Save and Send Test Request' button.
If it all worked as it should, you'll get a response like this:
-
Code = The success or failure code. 0 means success. any other number is an error.
-
CampaignID = Our reference ID for that message
-
Messages = How many mobile numbers you sent the message to.
-
Segments = The number of SMS segments used. eg 160 characters is the limit of 1 segment, 306 is the limit of 2 segments, 459 = 3 segments.
-
Credits = the number of credits used to send this campaign.
As long as you get a response similar to the above, then it is all working as it should. If you get an error - you'll see a description of the error in the response. Fix the issue and try again or contact us if you need help.
If the intended recipient didn't get the SMS message, check you have their number in the right format or contact us and we can investigate further.
Additional Actions
Receive SMS
Use the Receive SMS Action to periodically check our servers for any new SMS replies since it last checked.
Please note: This will pass back an array of SMS replies.
Because it is possible to receive multiple replies at once, you will need to use an iterator action directly after this step to process each reply one by one.
Then, AFTER the iterator action, add the app that you want to pass your replies to.
Be sure to turn OFF the "Simple Response" switch in the 'SMS Everyone : Check for replies' action.
To test this step you will need to send yourself an SMS from either Pabbly or from your SMS Everyone account, then reply to that message a few times so that there is plenty of data for Pabbly to use.
Wait for about 10 seconds after youve sent your last reply back, then click 'Save and Send Test Request' in the SMS Everyone : Check for replies Action.
Make sure you can see some data in the response.
For example, this below shows 3 messages that have been retrieved. (Count = 3)
and you can see all the message data in the 'Messages' field.
Adding the Iterator step
Click the + sign after the 'SMS Everyone : Check for replies' step.
search 'iterator'
Select 'Iterator (Pabbly)'
Under Action Event, select 'Process Arrays'
Under Choose Array, select '4 Messages []'
Click Save and Send Test Request
The iterator will give you just the FIRST result from the array.
But when it runs live, it will iterate through each response.
Then add whatever app you want after this to collect the data.
Check Delivery Status
Use this action after the 'Delay' action in Pabbly.
After the Send SMS action, click the + sign to add another step. Search for 'delay' and follow the simple prompts. Below I have added a delay of 1 minute.
Then after the delay step, add another app and again search for SMS Everyone and this time add the 'Check Delivery Status' action
Once you have connected your account, in the CampaignId field, select the 'Campaign ID : .......' field from the 'SMS Everyone : Send SMS' action results.
Click 'Save & send test request'
You'll see a response from our servers like this:
In the example above, this is what the fields mean:
-
CampaignId = the unique reference number of the message you sent
-
Count = the number of mobile phones you sent to in this campaign. There can be more than one.
-
Destinations X Destination = the phone number of the first destination you sent to in this campaign
-
Destinations X Timestamp = the date and time you sent the message in your time zone
-
Destinations X Status DeliveryReceiptStatusId = whether the message was delivered or not.
-
1 = DELIVERED
-
2 = FAILED
-
3 = REJECTED BY THE CARRIERS
-
4 = EXPIRED - The Carriers stopped trying after 48 hours
-
-
Destinations X Status Code = the error code if there was one. If it was delivered, this will be 0. If it failed, this will be one of about 50 codes. They can be found at https://www.smseveryone.com.au/restapi under the heading 'Delivery Error Codes' (Click on the left and it will take you there)
-
Permanent errors - the phone cant be reached again
-
Temporary errors - the phone can be reached again.
-
If the SMS has neither been confirmed delivered or failed yet because the carriers are still trying or the carriers cant supply a delivery receipt (happens occasionally) then the response will be more like this:
Count = 0 because there are zero delivery receipts for this campaign.
If you need any help with this, get in touch.
If you would like to give any of the above a try, sign up for a free trial below.