Resources · Make integration

SerwerSMS Make integrationAutomate SerwerSMS with Make.

Can Make read and send your SerwerSMS messages for you? Yes. The SerwerSMS Make integration gives you 5 modules: 1 trigger that spots new SMS and 4 actions for texts, voice messages and contacts. This page walks you from the connection to a first working scenario.

Try the SerwerSMS integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SerwerSMS Make integration do for you?

The SerwerSMS Make integration links your SerwerSMS account to Make, a no-code tool where you build a scenario (the automation itself, a chain of steps). Each step is a module, and SerwerSMS brings 5 of them: one watches for new SMS, four send texts or voice messages, add contacts, or call the API directly.

Turn incoming texts into contacts. Watch New SMS picks up each message that reaches your account, and Create a Contact files the sender in SerwerSMS, so nobody retypes a number by hand.

Send a text when another tool says so. A signed quote, a paid order or a new booking in another app can start the scenario, and Send a Text Message tells the customer right away. For people who prefer a call, Send a Voice Message delivers the same news out loud.

Reach the parts the modules skip. Make an API Call talks to any feature of the SerwerSMS API with the same connection, which helps when the four actions do not cover your case.

One honest limit: Make's own documentation for SerwerSMS is thin and says so, and no module has a published description. Expect to discover each module's fields in the editor after connecting. If you are new to the editor, the Make training covers the basics, and Make troubleshooting helps when a run fails. Also weighing n8n? The n8n vs Make comparison sets both tools side by side.

Connect

How do you connect SerwerSMS to Make?

  1. 01

    Add a SerwerSMS module

    In your scenario, click the +, search for SerwerSMS and pick any of its modules. Then click Create a connection. A connection is your SerwerSMS account linked to Make once, then reused by every SerwerSMS module you add later.

  2. 02

    Name it and authorize

    Give the connection a name if you like, such as the account it belongs to. Then follow what the window asks: either authorize Make on the SerwerSMS page that opens, or paste the key SerwerSMS gives you. Make's documentation does not say which one this app uses.

  3. 03

    Save and check

    Click Save. Back in the module, the connection now appears in the list, and Make can fill the dropdowns with what it reads from your account. If a dropdown stays empty, open the connection again and recheck the account details.

First scenario

Build your first scenario with SerwerSMS

GoalWhen a new SMS reaches SerwerSMS, Make saves its sender as a SerwerSMS contact.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + in the middle. That empty circle is where your first module goes.

  2. 02

    Add the trigger

    Search for SerwerSMS, pick Watch New SMS and choose your connection (or create it now, as shown above). Fill in what the module asks; the exact settings only appear once the account is linked.

  3. 03

    Add the contact step

    Click the + on the right of the trigger and pick Create a Contact. In its fields, map data from the SMS the trigger returned, by clicking the items Make shows from the previous module.

  4. 04

    Test with Run once

    Send a test SMS to your SerwerSMS number, then click Run once. Each module shows a bubble with the bundles it received (a bundle is one item, here one message). Check that the contact looks right.

  5. 05

    Schedule and switch on

    Click the clock on the trigger to set how often Make checks for new SMS; a new scenario runs every 15 minutes by default. Then switch the scenario on, and it keeps working without you.

Triggers

What starts a SerwerSMS scenario?

1 module starts a scenario when something happens in SerwerSMS. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SerwerSMS as soon as it happens.

SerwerSMS1Watch New SMS

Watch New SMS

triggerIn the docs only

Watch New SMS gives you each new text message that lands in your SerwerSMS account, one bundle per message, ready for the next module to use. It is the only SerwerSMS trigger, so every scenario that reacts to an incoming SMS starts here.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a message shows up at the next check, not the second it arrives. The type comes from the module's name, since no official description exists.
When to use it
when replies, requests or codes come in by SMS and you want them logged, answered or turned into contacts.
Watch out
on the Free plan, checks happen 15 minutes apart at most often; paid plans go down to 1 minute.
Modules

What can the SerwerSMS modules do?

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

SerwerSMS1

Create a Contact

ActionIn the docs only

Create a Contact adds a person to your SerwerSMS contacts from data another module hands over, so your list grows without copy and paste. Pair it with Watch New SMS or with a form tool upstream.

When to use it
when a new customer, lead or sender should be reachable by SMS later.
Watch out
each run creates a contact, so a scenario fed twice with the same person can leave a duplicate. Test with Run once first.
SerwerSMS2

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any feature of the SerwerSMS API from your scenario, using the connection you already set up. It is the fallback for anything the other three actions and the trigger do not cover.

When to use it
when you need a SerwerSMS feature that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the SerwerSMS API documentation open while you build it.
SerwerSMS3

Send a Text Message

ActionIn the docs only

Send a Text Message has SerwerSMS send an SMS as soon as your scenario reaches this step, with text you write or build from earlier modules. A confirmation, a reminder or an alert goes out without anyone opening SerwerSMS.

When to use it
when an event in another app, such as a new order or a booking, should reach a customer's phone.
Watch out
send the first test to your own number, then check the wording before switching the scenario on.
SerwerSMS4

Send a Voice Message

ActionIn the docs only

Send a Voice Message delivers your message as a voice call through SerwerSMS instead of a written text. That helps with recipients who read texts late, or who simply prefer to hear an urgent update.

When to use it
pick it over Send a Text Message when the news cannot wait, such as a cancelled appointment or a failed delivery.
Watch out
no official description exists for this module, so run it once on your own phone and listen before real customers get it.
Need help

Need help automating SerwerSMS with Make?

A person reads every message.

FAQ

SerwerSMS and Make: common questions

01Is the SerwerSMS Make integration free?
Yes, on Make's side. SerwerSMS is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a check every 15 minutes at most often, runs of up to 5 minutes and files up to 5 MB. Paid plans raise the frequency to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one item. Your SerwerSMS account and its own costs are a separate matter.
02What do you need to connect SerwerSMS to Make?
A SerwerSMS account and a Make account. Make's documentation lists no specific prerequisite for this app. You add any SerwerSMS module, click Create a connection, optionally name it, then either authorize Make on the SerwerSMS page or paste the key SerwerSMS gives you, and click Save. The connection is reused by every SerwerSMS module in your scenarios, so you only do this once per account. If a dropdown stays empty after saving, reopen the connection and check the details you entered.
03Does the SerwerSMS trigger in Make work in real time?
No. Watch New SMS is a scheduled trigger, based on its name since no official description exists. Make checks SerwerSMS on the scenario's schedule, every 15 minutes by default, and picks up the messages that arrived since the last check. On a paid plan you can shorten the interval to 1 minute. If a few minutes of delay matters for your use, set the schedule accordingly and test with Run once.
04What if a SerwerSMS module is missing in Make?
Use Make an API Call. It reaches any feature of the SerwerSMS API with the same connection as the other modules, so you can cover features that have no dedicated module. Keep in mind that Make's documentation for SerwerSMS is limited and says so, which means you will rely on the SerwerSMS API reference to write the request. Start small, test with Run once, then build on it. Name the call clearly in the module so the next person reading the scenario understands it.
05Should you use Make or n8n for SerwerSMS?
It depends on what you already use. Make gives you 5 SerwerSMS modules, including Make an API Call for the rest, and a Free plan with 2 active scenarios to try it. If your team already runs n8n, check whether a SerwerSMS node exists there before switching tools. Compare the two on the modules available for your case and on how your team likes to build, not on habit alone.
Same platform

Other docs you might need on this stack.

Browse all integrations