Resources · Make integration

GoSMS Make integrationAutomate GoSMS with Make.

Send an SMS when something happens in another tool. The GoSMS Make integration gives you 8 action modules and no trigger. This guide explains each one, links your account, and walks you through a first scenario.

Try the GoSMS integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the GoSMS Make integration do for you?

The GoSMS Make integration lets a Make scenario (the automation you build, a chain of modules) send, check and delete text messages through your GoSMS account. Each module is one brick of that chain, and all eight GoSMS modules are actions: something else has to start the scenario.

Order confirmations by text. A shop or form app starts the scenario, then Odeslat textovou zprávu (Czech for "send a text message") texts the customer. Each item that flows between modules is called a bundle: here, one order.

A credit check before a campaign. Načti detail organizace (kredit, kanály) reads your organization's details, with credit and channels named in the module title, so a later step can stop the run when the balance looks thin.

A follow-up on replies. Načíst seznam odpovědí ke zprávě pulls the replies attached to one message, which you can route to a sheet or a CRM.

Two limits to know. The Make docs list no Make an API Call module for GoSMS, so what the eight modules cover is what you get. The doc page itself warns it was drafted with AI help, so check any detail that matters on the GoSMS side. Module names stay in Czech in the editor, as shown here.

Before you commit to a tool, the n8n vs Make comparison lays out the trade-offs, Make pricing covers plans, and Make training helps if scenarios are new to you.

Connect

How do you connect GoSMS to Make?

  1. 01

    Add a GoSMS module

    You need an active GoSMS account first. In Make, open your scenario, add any GoSMS module and click Create a connection. A connection is your GoSMS account linked to Make once, then reused by every GoSMS module.

  2. 02

    Name the connection

    The Connection name field is optional. Filling it pays off when you run several GoSMS accounts, say one per client, because the module dropdown then shows which is which.

  3. 03

    Paste your API credentials

    In GoSMS, open the account administration panel, find the section called API or API access, and copy the Client ID and Client secret. Paste both into Make, or follow the on-screen prompts to finish.

First scenario

Build your first scenario with GoSMS

GoalWhen a new order lands in another app, Make texts the customer with GoSMS and then reads back the message details.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Since GoSMS has no trigger, pick the app that holds your orders as the first module.

  2. 02

    Add the send module

    Click the + on the right, search for GoSMS and pick Odeslat textovou zprávu. Choose your connection, then map the phone number and text from the order module.

  3. 03

    Read the message back

    Add Načíst detail zprávy after it and map the message from the send step's output; Run once shows what that step returns. That gives you a record of what GoSMS accepted.

  4. 04

    Test with Run once

    Click Run once with your own number in a test order. Open each module's bubble to read the bundles it received and confirm the text reached your phone.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, 15 minutes minimum on the Free plan), then switch the scenario on.

Modules

What each GoSMS module does

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

GoSMS1

Načti detail organizace (kredit, kanály)

ActionIn the docs only

This module fetches your GoSMS organization details, and its name points to your credit and your sending channels. You get that data as a bundle other modules can test.

When to use it
place it ahead of a batch of sends so a filter can halt the run when credit looks low.
Watch out
the docs give no field list, so run it once to see what it returns.
GoSMS2

Načíst detail zprávy

ActionIn the docs only

Pick this one to pull the details of a single message you already sent, which gives you something to log or check after the fact.

When to use it
right after a send module, to store what GoSMS recorded in a sheet or a customer file.
Watch out
it reads one message at a time, so map it from the previous step's output rather than typing it.
GoSMS3

Načíst seznam odpovědí ke zprávě

ActionIn the docs only

Customer answers become usable data with this module: it loads the list of replies tied to one message you sent.

When to use it
after a confirmation text that asks the customer to reply, when those answers belong in your CRM or a support queue.
Watch out
a list can hold several replies, or none, so plan what the next module does in each case.
GoSMS4

Odeslat textovou zprávu

ActionIn the docs only

Sending an SMS is the core job here: this module texts a phone number with the content you map from earlier modules. Each send is one operation, the unit Make counts on your plan.

When to use it
for order confirmations, appointment notices or delivery updates fired by another app.
Watch out
test with your own number before you switch the scenario on.
GoSMS5

Otestovat vytvoření zprávy bez odeslání

ActionIn the docs only

As the name says, this module tests creating a message without sending it. You see whether GoSMS accepts your content and number while no text goes out.

When to use it
while you build a scenario that maps dynamic text, so you can check the result safely before switching to the real send module.
Watch out
swap it for the send module once your test passes, or nobody receives anything.
GoSMS6

Přijímat doručenky

ActionIn the docs only

Its Czech name reads "receive delivery receipts", so, judging by its name, it is the module to try when you want to know whether a text arrived. It appears as an action, not a trigger.

When to use it
when a failed delivery should update the customer record or alert your team.
Watch out
the doc says nothing about its settings, so click Run once and read the bundles before building on it.
GoSMS7

Přijímat odpovědi

ActionIn the docs only

With this module, replies to your GoSMS messages come into Make; the name means "receive replies". Unlike the reply list module, its title ties it to no single message.

When to use it
when every answer customers text back should land in one place, such as a shared inbox or a sheet.
Watch out
it is typed as an action, so another module or a schedule still has to start the scenario.
GoSMS8

Smazat textovou zprávu

ActionIn the docs only

Deleting a text message is all this module does, which keeps your GoSMS account clear of messages you no longer want there.

When to use it
when an order is cancelled in your shop and the related message should go too.
Watch out
a delete cannot be undone, so add a filter before it and test with a throwaway message first.
Need help

Need help automating GoSMS with Make?

A person reads every message.

FAQ

GoSMS and Make: common questions

01Is the GoSMS Make integration free?
Yes, on the Make side. GoSMS is a standard app, available from the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits each month. Your GoSMS subscription is separate: the GoSMS pricing page covers it, and you need an active account either way.
02What do you need to connect GoSMS to Make?
An active GoSMS account and its API credentials. In the GoSMS administration panel, open the API or API access section, copy the Client ID and the Client secret, and paste them when Make asks after you click Create a connection. If GoSMS prompts for a callback URI, use the one given in the Make docs, shown in the connection section above. Naming the connection is optional but helps once you manage more than one GoSMS account.
03Does the GoSMS Make integration react in real time?
No, because GoSMS has no trigger in Make: all eight modules are actions. The scenario starts from something else. The first option is a trigger from another app, such as your shop or form tool, followed by a GoSMS module. The second is to put a GoSMS module first and let Make's scheduling run it, every 15 minutes by default, or as often as each minute on a paid plan. Either way, timing depends on that first module.
04What if a GoSMS module is missing in Make?
It depends on what you need. The GoSMS app offers eight modules and no Make an API Call module, so you cannot reach other parts of the GoSMS API from this app. If your case falls outside send, read, test, receive and delete, look at another SMS app in Make, or ask the team behind this guide to review the setup. Also note the GoSMS doc page warns it was drafted with AI help, so verify any detail that matters.
05Should you use Make or n8n for GoSMS?
It depends on your stack. Make gives you eight ready GoSMS modules covering sending, reading, test messages, receipts, replies and deletion, available from the Free plan, which suits a first automation built in a visual editor. The same app often has an n8n node as well, so check what that node offers before you choose. No ranking applies here: compare the modules you actually need on each side and the tools already running in your team.
Same platform

Other docs you might need on this stack.

Browse all integrations