Resources · Make integration

SMSzasilam Make integrationAutomate SMSzasilam with Make.

Need a text message to leave the moment something happens in another tool? The SMSzasilam Make integration gives you 5 action modules to send SMS and read your message history. This guide connects your account and builds a first scenario with you, no code involved.

Try the SMSzasilam integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SMSzasilam Make integration let you automate?

The SMSzasilam Make integration links your SMSzasilam account to Make, so a scenario (the automation you build, a chain of steps) can send a text or pull your message lists without you opening the SMS dashboard. Each step is a module, one brick of the scenario, and all 5 modules of this app are actions.

Confirmation texts that write themselves. An order lands in your shop or a booking appears in your calendar app, and Pošli SMS sends the customer a short confirmation. The phone number and the wording come from the step before.

A log of what went out. Vypiš odeslané zprávy, going by its name, reads the messages already sent, so a scenario can copy them into a spreadsheet or a CRM where the sales team actually looks. Vypiš přijaté zprávy does the same for replies, which helps when customers answer a reminder by text.

One wording, many sends. Vypiš šablony zpráv brings back the message templates saved in your account, so the text you approved once is the text every scenario uses.

What the app does not do in Make: it has no trigger, so nothing in SMSzasilam starts a scenario by itself. The scenario starts on a schedule or on another app's trigger. The official doc also warns that it was generated with AI help and may contain mistakes, so check anything critical with SMSzasilam. Before you go further, the Make pricing page explains how operations are counted, and the n8n vs Make comparison helps if you are still choosing a tool. If a scenario stalls, Make troubleshooting covers the usual fixes.

Connect

How do you connect SMSzasilam to Make?

  1. 01

    Copy your API key from SMSzasilam

    Log in to SMSzasilam and open the account dashboard. In the account settings, find the section called API or OAuth Tokens and copy the key shown there. The doc also asks for an active SMSAPI account, so have it ready.

  2. 02

    Add a SMSzasilam module in Make

    In your Make scenario, add any SMSzasilam module and click Create a connection. A connection is your SMSzasilam account linked to Make once, then reused by every module of the app. You can type a label in Connection name if you run several accounts.

  3. 03

    Paste the key and save

    Paste the credentials copied in the first step, or follow the instructions Make shows on screen, then save. From now on the module can talk to your account, and the next SMSzasilam module you add will offer this connection straight away.

First scenario

Your first scenario with SMSzasilam

GoalWhen a new order reaches your shop app, Make sends the buyer a confirmation text through SMSzasilam.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big +. This first slot holds the module that starts everything, here the trigger of the app where your orders arrive.

  2. 02

    Pick the starting app

    Search for your shop or form app, choose its module for new orders and connect it. Every new order becomes a bundle, one item passed to the next module with its details, including the phone number.

  3. 03

    Add Pošli SMS

    Click the + on the right of the first module, search SMSzasilam and pick Pošli SMS. Connect your account as shown above. Make then lists what it can read from SMSzasilam once the connection exists.

  4. 04

    Map the number and the text

    Fill the module fields by clicking into them and choosing values from the order module: the buyer's phone, a line with the order reference. Keep the text short and test it on your own number first.

  5. 05

    Test with Run once

    Click Run once, place a test order and read the bundles each module received. If the text reaches your phone, the mapping is right. Each module run on a bundle is one operation, the unit Make counts on your plan.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. On the Free plan, 15 minutes is also the shortest interval between two scheduled runs.

Modules

What each SMSzasilam module does

SMSzasilam gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SMSzasilam1

Pošli SMS

ActionIn the docs only

Your customer gets a text the moment your scenario reaches this step. The Czech name reads "Send SMS": it is the one module here that sends something out, fed by a trigger from your shop, CRM or form tool.

When to use it
a booking is confirmed or a parcel ships and the buyer should hear about it by phone rather than by email.
Watch out
every text sent is a real message on your SMSzasilam account, so point it at your own number while you test with Run once.
SMSzasilam2

Vypiš odeslané zprávy

ActionIn the docs only

A copy of your outgoing history lands wherever you need it. Going by its Czech name, "List sent messages", this action reads the texts your account has already sent, which lets a scenario archive them in a sheet or attach them to a client record.

When to use it
support wants to see which reminders a customer received before calling them back.
Watch out
the Make doc does not say what this module returns, so click Run once and look at the output before you map anything.
SMSzasilam3

Vypiš přijaté zprávy

ActionIn the docs only

Replies from customers stop sitting unread in the SMS dashboard. The name translates to "List received messages", so this is the module to reach for when the texts coming in matter as much as the ones going out.

When to use it
customers answer an appointment reminder with a short "yes" or "cancel" and your team tracks those answers in a shared tool.
Watch out
the app has no trigger, so replies are only read when the scenario runs on its schedule.
SMSzasilam4

Vypiš šablony zpráv

ActionIn the docs only

The wording your team already approved stays the wording every scenario sends. Its name means "List message templates": it fetches the templates stored in your SMSzasilam account so a later step can reuse one instead of typing the text again.

When to use it
marketing edits the promotion text in SMSzasilam and nobody wants to open Make to change it too.
Watch out
the Make doc gives no detail on template fields, so check with Run once which values the module actually returns.
SMSzasilam5

Zavolej API

ActionIn the docs only

This is your way into SMSzasilam features that the four other modules do not cover. The Czech name reads "Call API": going by that name, it sends your own request to the SMSzasilam API with the connection you already set up.

When to use it
you need an action from the SMSzasilam API documentation that none of the ready-made modules offers.
Watch out
the Make doc says nothing about how to fill it, so read the vendor's API documentation first and test with Run once on harmless data.
Need help

Need help automating SMSzasilam with Make?

A person reads every message.

FAQ

Questions about the SMSzasilam Make integration

01Is the SMSzasilam Make integration free?
Yes on the Make side: SMSzasilam is a standard app, available from the Free plan like the 3,000+ other standard apps. The Free plan allows 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute. SMSzasilam itself needs its own subscription, described on the SMSzasilam pricing page, which this guide does not cover.
02What do you need to connect SMSzasilam to Make?
You need an active SMSAPI account and an OAuth token from SMSzasilam. Log in, open the account dashboard, find the section named API or OAuth Tokens in the settings and copy the key. In Make, add any SMSzasilam module, click Create a connection, optionally name it, then paste the key. The same connection is then reused by all 5 modules, so you only do this once per account, and every new SMSzasilam module picks it up.
03Can a SMSzasilam module start a Make scenario on its own?
No. All 5 SMSzasilam modules are actions, and the app has no trigger, scheduled or instant. A scenario that uses them starts in one of two ways: on the schedule you set on its first module, every 15 minutes by default, or on a trigger from another app, such as a new order or a new form entry. If that other app offers an instant trigger, it calls Make through a webhook as soon as the event happens, and the SMS step runs right after.
04What if a SMSzasilam module is missing in Make?
It depends on what you need. SMSzasilam has no universal Make an API Call module, but it ships its own Zavolej API module, whose Czech name means Call API, for requests the four other modules do not cover. Check the vendor's API documentation before using it. Keep in mind that the Make doc for this app was generated with AI help and may contain mistakes, so confirm key details with SMSzasilam. If you are stuck, the team at Hack'celeration can look at the scenario with you.
05Should you use Make or n8n for SMSzasilam?
It depends on where the rest of your automations live. On Make, this page confirms 5 SMSzasilam modules, all actions, usable from the Free plan. The same app often has an n8n node too, but nothing here confirms one for SMSzasilam, so check the n8n node list before deciding. No ranking between the two tools follows from that. The n8n vs Make comparison linked earlier on this page lays out the general criteria, and the team can help you weigh them for your SMS workflows.
Same platform

Other docs you might need on this stack.

Browse all integrations