Key Takeaways
- make android sms gateway order or pipeline alerts is an HTTP module POSTing REST JSON — we do not ship a first-party Make app.
- Shipping/status SMS still leave your SIM. Make only schedules the HTTPS call.
- Use order id as Idempotency-Key so scenario retries do not double-text the customer.
- Keep OTP on a product path. Pipeline alerts on another deviceId.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Each successful radio send spends operator credit.
- Docs own live fields. Scenario mapping must match OpenAPI.
HTTP module, not a Make SMS app we sell
Search intent for make android sms gateway order or pipeline alerts is wiring a scenario to text a customer when an order moves — on your SIM. Service pricing is based on device count and total SMS sent through the gateway. Make documents HTTP modules (Make HTTP). We do not list a branded Make app. Contract: docs.sms-gateway.app.
If the scenario “succeeded” and the phone was in a drawer, you automated a queue, not a delivery.
curl -X POST "https://app.sms-gateway.app/api/v1/messages" \
-H "Authorization: Bearer $SMS_GATEWAY_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: 3f1b0c8a-9d2e-4c77-9f5a-2b6d1e0f4a83" \
-d '{"to":["+14155552671"],"text":"Your verification code is 481920","type":"sms"}'Map that JSON in the HTTP module. Consent still applies — bulk SMS with consent.
Order alerts are not OTP
Shipping texts can carry STOP. Login codes cannot share that radio. OTP verification. Laravel OTP stays a product path.
| Node | Does | Trap |
|---|---|---|
| Trigger | Order paid / pipeline stage | Firing on every draft save |
| HTTP | POST JSON + Bearer from a connection | Key hardcoded in a note module |
| Idempotency | Header = order id | Make auto-retry without a key |
| Radio | Paired Android; last-seen watched | Assuming Make hosts an SMSC |
POST /messages from the scenario
to[], text, optional deviceIds. Do not invent priority. Webhooks if you need DLR back into Make.
Idempotency on order id
Scenario auto-retry is a feature until it double-sends. Header = stable order/pipeline event id.
Connection secrets, not scenario JSON
Store the Bearer token in a Make connection. Never in a shared blueprint screenshot. Keys in env. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
Pipeline alert checklist
- Staff order canary before production SKUs.
- STOP on promotional/status copy where required.
- OTP device not this scenario.
- Idempotency-Key = order id.
- Last-seen watched; Make 200 ≠ inbox.
Next steps
One paid-test order, then production. Pricing. Setup.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS API documentationLive endpoint reference
- device and SMS volume pricingPlans and allowances
- transactional SMS for orders and alertsEvent-driven messages
- Android SMS gateway product guideDefinition, product, and how to buy
