- Home
- Resources
- Integrations
- Micropay
Micropay Zapier integrationAutomate Micropay with Zapier.
The Micropay Zapier integration gives you 1 trigger, 1 action and 0 searches. One side listens to the SMS people send to your Micropay virtual number, the other sends SMS out, and Zapier ties both to the rest of your apps.
Beta app Zapier still marks this integration as beta.
Verified Trustpilot reviews · AI, automation & growth agency
What the Micropay Zapier integration does for you
Micropay handles business SMS, and through Zapier it plugs into a Zap: the automation that runs each time an event happens in one app and makes something happen in another. An incoming SMS can start that chain, and any other app can ask Micropay to send one. You stop copying numbers and messages by hand.
A log of every incoming SMS. Receive SMS fires when someone texts your virtual number with your code word, and the next step writes the message into a spreadsheet, so nothing stays inside the phone system.
A text sent from another app. Send SMS takes a message and a list of numbers, or a Micropay list ID, from whatever app starts the Zap. A new form entry or a new row can become an SMS without anyone typing it.
Separate flows for separate code words. Each Receive SMS trigger is tied to one code word, the word at the start of the incoming text. Two code words, two Zaps, two destinations.
What Zapier does not do here: it does not hand you a virtual number. That number comes from your sales manager at Micropay, and the trigger cannot work without it. There is no search step either, so a Zap cannot look up a past SMS or a contact in Micropay. And Zapier lists the app as beta, which is worth keeping in mind before you rest a key process on it.
New to the tool itself? See our Zapier review.
Zapier words in one minute
Eight terms come back on this page. One plain line each.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. For Micropay, it is an SMS arriving on your virtual number.
- Action
- What the Zap does once started, the step that writes, sends or moves something. For Micropay, sending an SMS.
- Task
- The unit Zapier bills: one action that completes successfully. The count on your plan is a count of those.
- Instant trigger
- A trigger the app reports itself: it calls Zapier when the event happens, so nothing waits for a scheduled check.
- Polling trigger
- A trigger Zapier checks on a timer, asking for new items at a fixed interval. Micropay has none of those.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes one, and it then needs a paid plan.
What a Micropay Zap really costs
Micropay is not a premium app on Zapier, so it is available from the free plan.
- Premium appNo
- Free plan100 tasks a month, two-step Zaps
- BilledEach successful Send SMS, and each other action
- Not billedReceive SMS, and failed actions
An incoming SMS that starts the Zap costs no task: triggers are free. Each Send SMS that completes counts as one task, and one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each one limited to two steps, so a filter on the code word or a second action means a paid plan. The interval grid below concerns polling triggers; it does not apply to Receive SMS, which is instant.
Connect Micropay to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. A connection is your Micropay account linked to Zapier once, then reused by every Micropay step in your Zaps.
- 02
Find Micropay and add it
Search for Micropay in the dialog, pick it from the results, then click Add connection. A new tab opens, and that tab is where you finish linking the account.
- 03
Sign in and grant access
Sign in to Micropay in that tab and grant Zapier access to the account. You need a Micropay account, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first Zap: every incoming SMS in a spreadsheet
GoalWhen an SMS with your code word reaches your virtual number, keep only the ones that match your condition, then add the message to a spreadsheet.
- 01
Create the Zap with Receive SMS
Start a new Zap, pick Micropay as the app and
Receive SMSas the event. Select your Micropay connection when Zapier asks for it. - 02
Fill the three required fields
Write a service description, enter the incoming virtual number from your sales manager, and set the code word, letters and numbers only.
- 03
Test with a real SMS
Run the test: Zapier brings back the three most recent items of the account. Pick a real one so the mapping uses true data.
- 04
Add the filter and the spreadsheet
Click the plus icon, add Filter and fill the field, the rule and the value. Then add the spreadsheet step and map the message fields into the columns.
- 05
Test, then publish
Test each step and read what came back. Click Publish to switch the Zap on. With a filter, it is a multi-step Zap and needs a paid plan.
The Micropay trigger
1 event starts a Zap when something happens in Micropay, and one of them is instant: the app calls Zapier straight away, whatever your plan.
Receive SMS
Instant triggerIn Zapier“Triggers when SMS sent from clients to your virtual phone number at Micropay.”
Starts your Zap when someone texts your Micropay virtual number with a message that begins with your code word. The SMS then becomes data the next steps can store, route or answer.
The Micropay action
Micropay gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Send SMS
ActionIn Zapier“Initiate a request to send SMS to a list of phone numbers and/or list ID”
Asks Micropay to send a text to a list of phone numbers, a Micropay list ID, or both.
When a Micropay Zap breaks
Zapier links no help article to Micropay, and no app-specific limit has been recorded beyond the field rules of its two operations.
The cases below cover general Zapier behavior and those field rules. If a run fails and the cause stays unclear, see our Zapier troubleshooting guide.
Texts sent before the Zap are lost to it
A Zap only reacts to what happens after you switch it on. SMS received earlier are not picked up; moving that backlog is a separate job.The code word does not match
Receive SMS is tied to a code word placed at the start of the incoming text. A message that does not begin with it does not belong to that service.A Zap that sets itself off
As a general precaution, a Zap that writes into the very place its own trigger watches can start itself again and again, and burn through tasks.A sudden burst is held back
When a trigger suddenly returns a huge batch, after a bulk import for example, Zapier's flood protection can hold those runs back.
Need help automating Micropay with Zapier?
A person reads every message.



