ASPSMS Zapier integrationAutomate ASPSMS with Zapier.
ASPSMS Zapier integration: 0 triggers, 1 action, 0 searches. One step does the job, Send SMS. Another app starts the Zap, and ASPSMS texts the number you map. Here is how to wire it, what it costs on the free plan, and where messages go wrong.
Verified Trustpilot reviews · AI, automation & growth agency
What the ASPSMS Zapier integration is good for
The ASPSMS Zapier integration lets Zapier, a service that runs automations between your apps, send text messages through ASPSMS, an SMS gateway based in Switzerland. ASPSMS has no event of its own to start anything, so another app opens the Zap and ASPSMS sends the SMS at the end.
Reminders that leave on their own. A booking tool starts the Zap and Send SMS texts the client the time and the address. Order updates by text. A shop or an order form records a purchase, and the buyer gets a short confirmation on their phone. Alerts for whoever is on call. An urgent form or a new lead fires a text to a colleague who is not watching their inbox. All three rest on the same step: you choose the number, you write the text, and fields from the starting app slot into it, like a first name or a booking time.
What Zapier does not do here: it cannot read replies, confirm delivery or start a Zap when ASPSMS receives something. Send SMS is the only operation. A Zap also never catches up on the past, so bookings made before you publish it get no text. If you work with Make, the ASPSMS Make integration page covers the same gateway, and the n8n vs Zapier comparison helps if a third tool is on your list.
Seven Zapier words before you start
The rest of this page leans on these terms. Each one in plain words.
- Zap
- An automation built in Zapier: a starting event in one app, followed by one or more steps that run every time it happens.
- Trigger
- The event that opens a Zap. ASPSMS offers none, so the trigger always comes from another app: a booking, a form, an order.
- Action
- A step that does something for you once the Zap is running. Here it is Send SMS, which texts a phone number.
- Task
- What Zapier bills: one action that completes without error. Every SMS the Zap sends successfully is one task on your plan.
- Polling vs instant
- Polling means Zapier checks the starting app on a timer. Instant means that app warns Zapier itself, the second the event occurs.
- Filter
- A checkpoint between steps: the Zap goes on only when the data meets your rule, for example a phone number that is filled in.
- Connection
- Your ASPSMS account linked to Zapier one time. Every Zap that sends a text then picks it from a list instead of asking again.
What a text costs you in Zapier tasks
ASPSMS is not a premium app, so it runs on the free plan. The step that starts the Zap never costs a task; only a Send SMS that goes through is billed.
- Free plan100 tasks a month, as many Zaps as you want
- Free plan Zap sizeTwo steps: a trigger and Send SMS
- Premium appNo, ASPSMS works on the free plan
- BilledEach successful Send SMS, never the trigger
One SMS sent by the Zap is one task, and a Send SMS that fails is not counted. The free plan gives 100 tasks a month and Zaps of two steps, so a trigger plus Send SMS fits. Add a filter or a second action and the Zap turns multi-step, which needs a paid plan. With no ASPSMS trigger, how fast a text leaves depends on the app that starts the Zap: right away if it is instant, otherwise at the interval of your plan.
Link your ASPSMS account in three steps
- 01
Go to the Apps page
Log in to Zapier and go to Apps, the page that gathers every account you have linked. Have your ASPSMS login ready: the action itself asks you to create an ASPSMS account first.
- 02
Pick ASPSMS
Hit + Add connection, search for ASPSMS in the dialog that appears and select it. A second button, Add connection, then opens the ASPSMS sign-in in a new tab.
- 03
Sign in and allow access
Sign in to ASPSMS in that tab and let Zapier use the account. From then on, every Zap that sends a text offers this connection in a list, with nothing to retype.
Your first Zap: a text for every new Calendly booking
GoalEach new booking that carries a phone number gets a confirmation SMS from ASPSMS.
- 01
Start with the booking tool
Create a Zap and choose Calendly with the Invitee Created event. ASPSMS cannot open a Zap, so the booking tool plays that role. Connect your Calendly account.
- 02
Test with a real booking
Run the trigger test. Zapier shows the three latest bookings of the account; choose one that has a phone number, because the SMS step is mapped on it.
- 03
Skip bookings without a number
Use the plus icon to add a Filter. Pick the phone field and a text rule that passes only when it holds a value. No number, no SMS, no failed step.
- 04
Add Send SMS
Choose ASPSMS and Send SMS as the action. Map the phone into To and write the Message, mixing fixed words with the booking time. Under 160 characters, it leaves as one SMS.
- 05
Test, then publish
Send a test to your own phone first and read it. Then click Publish. From that moment, each new booking with a number gets its text.
The ASPSMS action
ASPSMS gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Send SMS
ActionIn Zapier“Sends an SMS using ASPSMS. Create an account at ASPSMS first.”
Texts one phone number through your ASPSMS account, with a message you write or build from earlier steps. Two fields are required: To, the recipient's number, and Message, the text itself.
Where an ASPSMS Zap goes wrong
Zapier ties no help article to ASPSMS, so these cases mix the two field notes of Send SMS with the limits every Zap shares.
Most of them only show up once real contacts flow through, never with the tidy test record. When a text goes missing, the Zapier troubleshooting page lists the checks to run in order.
Long messages turn into several SMS
One SMS holds up to 160 characters. A longer Message is split into several texts, so check how your ASPSMS account handles that before you go live.Numbers in the wrong format
To works best with the international E.164 format: plus sign, country code, then the number. A local number without its country code is the first thing to check.Bookings made before publishing
The Zap only reacts to events that happen after you switch it on. Clients who booked last week get no SMS, and catching them up is a separate job.A burst of events gets held
After a bulk import in the source app, a trigger that suddenly sends a huge batch can be held back by Zapier's flood protection, sparing you a wave of texts.
Need help automating ASPSMS with Zapier?
A person reads every message.
