Resources · Make integration

SMS.dk Make integrationAutomate SMS.dk with Make.

Can your texts go out on their own when a new contact lands somewhere else? The SMS.dk Make integration gives you 10 action modules for messages, contacts and SMS groups. This guide shows teams who already use SMS.dk how to connect the account and build a first working scenario.

Try the SMS.dk integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the SMS.dk Make integration?

The SMS.dk Make integration lets a scenario (the automation you build in Make, a chain of modules) send texts and keep your SMS.dk contact list tidy without anyone copying data by hand. Each module is one brick of that chain, and all ten of them act: they send, create, update or remove something in your account.

Welcome text for every new lead. A form or CRM in another app hands over the person's details, Create a Contact stores them in SMS.dk and Send a Message fires the first text right after.

Segments that follow your customer data. When someone becomes a customer elsewhere, Add a Contact to SMS group moves them into the right list, and Remove a Contact from SMS group takes them out when the status changes. Send a Message to a Group then reaches the whole segment in one module.

A clean contact base. Update a Contact and Activate or deactivate a Contact mirror changes made in your main tool, so SMS.dk never holds stale data.

What the integration does not do: SMS.dk has no trigger in Make, so nothing in SMS.dk can start a scenario by itself. The flow always starts from another app or from the schedule. When a call is missing from the list, Make an API Call reaches the rest of the SMS.dk API. Before you commit, read the Make review and the Make pricing guide; if the same automation could run on another platform, n8n vs Make lays out how the two compare.

Connect

How do you connect your SMS.dk account to Make?

  1. 01

    Copy your API key from SMS.dk

    You need an active SMS.dk account first. Log in, click Kontoindstillinger in the upper-right corner, scroll down to the API Key section and copy the key shown there. Make uses it to act on your behalf.

  2. 02

    Add an SMS.dk module and start a connection

    In your scenario, add any SMS.dk module, for example Send a Message, then click Create a connection. A connection is your SMS.dk account linked to Make once and reused by every SMS.dk module after that.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear label helps when you manage several accounts. Paste the API key you copied, confirm, and Make can now list what it reads from your account.

First scenario

Your first scenario: welcome every new SMS.dk contact

GoalWhen a new lead shows up in another app, Make saves it as an SMS.dk contact and sends a welcome text.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your leads arrive, since SMS.dk itself cannot start the flow.

  2. 02

    Add Create a Contact

    Click the + on the right of that first module, search for SMS.dk and choose Create a Contact. Create the connection, then map the contact details coming from the previous module.

  3. 03

    Chain Send a Message

    Add Send a Message after the contact module and write the welcome text. Map the recipient from the earlier modules so each bundle (one item passing between modules, here one lead) gets its own text.

  4. 04

    Test with Run once

    Click Run once and create a test lead with your own number. Open each module's bubble to read the bundle it received, and check the text arrived on your phone.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What each SMS.dk module does

SMS.dk gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SMS.dk1

Activate or deactivate a Contact

ActionIn the docs only

Flips a contact between active and inactive while keeping the record in your account, which lets you pause someone without losing their history.

When to use it
a customer asks for a break from your texts, or a subscription is paused in your billing tool, and you may want the contact back later.
Watch out
map the status from the source app rather than typing a fixed value, or every run sets the same state.
SMS.dk2

Add a Contact to SMS group

ActionIn the docs only

Places an existing contact into one of your SMS groups, so the person starts receiving the texts you send to that segment.

When to use it
a lead signs up for a specific offer or location and belongs in a dedicated list rather than your whole base.
Watch out
the contact must already exist, so put Create a Contact before this module when the person is new.
SMS.dk3

Create a Contact

ActionIn the docs only

Adds a fresh person to your SMS.dk account using data from an earlier module, so nobody retypes phone numbers from a spreadsheet or a form.

When to use it
a form submission, a new order or a new CRM record should turn into someone you can text.
Watch out
if the same person can reach the scenario twice, filter duplicates upstream, otherwise you end up with two records.
SMS.dk4

Create an SMS group

ActionIn the docs only

Opens a new group in SMS.dk from inside the scenario, which gives you a ready list for a campaign, an event or a branch.

When to use it
a new event is published in your booking tool and its attendees need their own list for reminders.
Watch out
keep this module out of flows that run per contact, or you create one group for each person who passes through.
SMS.dk5

Delete a contact

ActionIn the docs only

Removes a contact from your SMS.dk account for good, which is what you want when someone asks to have their data erased.

When to use it
a deletion request is logged in your support desk or CRM and SMS.dk must follow.
Watch out
there is no undo here; if the person may come back, Activate or deactivate a Contact is the safer choice.
SMS.dk6

Make an API Call

ActionIn the docs only

Calls any endpoint of the SMS.dk API with the connection you already set up, so you are not stuck when the nine other modules stop short.

When to use it
you need an SMS.dk feature that has no module of its own and the API offers it.
Watch out
you write the request yourself, so keep the SMS.dk API documentation open and test with Run once before switching on.
SMS.dk7

Remove a Contact from SMS group

ActionIn the docs only

Takes a contact out of one group and leaves the contact itself in place, so the person stops getting that segment's texts but stays in your account.

When to use it
a trial ends, an order ships or a lead changes stage, and the old list no longer fits.
Watch out
pair it with Add a Contact to SMS group when someone moves between segments, so they sit in exactly one.
SMS.dk8

Send a Message

ActionIn the docs only

Sends one text to one recipient, with content you can build from data mapped from earlier modules, such as a first name or an order number.

When to use it
a single event calls for a personal text, like a booking confirmation or a delivery notice.
Watch out
the module runs once per bundle, so a list of fifty contacts arriving together means fifty texts and fifty operations.
SMS.dk9

Send a Message to a Group

ActionIn the docs only

Reaches every member of an SMS group with one module, which keeps a broadcast inside a single operation instead of one per person.

When to use it
an announcement is ready, say a store closure or a last-minute change, and the whole segment must hear it.
Watch out
if several bundles reach this module in one run, the group gets the text several times; feed it one bundle only.
SMS.dk10

Update a Contact

ActionIn the docs only

Changes the details of a contact that already exists, so a new phone number or a corrected name in your main tool reaches SMS.dk too.

When to use it
a customer edits their profile in your shop or CRM and you want texts to keep landing on the right phone.
Watch out
the module needs to know which contact to change, so map the identifier from the step that created or found it.
Need help

Need help automating SMS.dk with Make?

A person reads every message.

FAQ

SMS.dk and Make: frequent questions

01Is the SMS.dk Make integration free?
Yes, on the Make side. SMS.dk is a standard app, available from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans drop the interval to one minute, lift the cap on active scenarios and count usage in credits each month. The texts themselves depend on your SMS.dk subscription, which Make does not cover, so check that side on the SMS.dk pricing page before you plan a large send.
02What does it take to connect SMS.dk to Make?
An active SMS.dk account and its API key. You find the key in SMS.dk under Kontoindstillinger, in the upper-right corner, then in the API Key section further down. In Make, add any SMS.dk module, click Create a connection, give it a name if you like and paste the key. That single connection then serves every SMS.dk module in all your scenarios, so you only go through this once per account.
03Does SMS.dk trigger Make scenarios in real time?
No, because SMS.dk has no trigger module in Make at all. Something else has to start the scenario. The most common option is a trigger from another app, like a form or a CRM, that hands over the data your SMS.dk modules need. The other option is the schedule on the first module, every 15 minutes by default, with the interval you pick. In both cases SMS.dk only acts on what the scenario sends it; it never starts a run by itself.
04What if an SMS.dk module is missing in Make?
It depends on what the SMS.dk API allows. The integration includes Make an API Call, which reaches any endpoint of that API with the connection you already created, so a feature without its own module is usually still within reach. You write the request yourself, which means reading the SMS.dk API documentation first. Note also that the Make documentation for this app flags its content as AI-generated, so confirm important details with SMS.dk directly.
05Make or n8n for SMS.dk: which one fits?
It depends on the tool your team already runs. On Make, SMS.dk comes with ten modules covering messages, contacts and SMS groups, plus Make an API Call for the rest, and it works from the Free plan. The same app often has an n8n node too. Pick the platform where the other apps of your flow, such as your CRM or your forms, are already connected, and compare the node list on the n8n side before you decide.
Same platform

Other docs you might need on this stack.

Browse all integrations