Resources · Make integration

SlickText (legacy) Make integrationAutomate SlickText (legacy) with Make.

Your SMS contact list can trigger work on its own. The SlickText (legacy) Make integration gives you 10 modules: 1 trigger, 8 actions and 1 search. This page is for marketers and ops leads who text customers, and it walks you from the API key to a running scenario.

Try the SlickText (legacy) integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SlickText (legacy) Make integration do?

It links your SlickText (legacy) account to Make so contacts and text messages move without copy and paste. In Make you build a scenario, the automation itself, out of modules: each module is one brick, a trigger that starts the flow, an action that does something, or a search that looks things up.

A welcome text for every new subscriber. Watch Contacts spots contacts added to your account, and Send a Message to a Contact greets each one by text. Nobody has to check the list by hand.

A clean opt-out when another tool says stop. When a customer unsubscribes in your CRM or help desk, Search Contacts finds them in SlickText and Opt-out a Contact records the choice, so your SMS list respects what they asked for elsewhere.

A campaign pushed from your own data. Send a Message to a Textword List sends one text to everyone on a list, for example when a new product goes live in your store. Edit a Contact keeps names and details in line with the source you trust.

The SlickText documentation in Make is short: it lists the modules without describing their fields or limits, so test each step with Run once before you rely on it. When a listed module falls short, Make an API Call reaches the rest of the API with the same connection. The same app may also exist in n8n; the n8n vs Make comparison helps you pick. New to the editor? The Make training starts from zero, and Make troubleshooting covers errors you may meet.

Connect

How do you connect SlickText (legacy) to Make?

  1. 01

    Generate your API keys

    In SlickText, open the My Account page from the dashboard, go to the API section and click Generate API Keys. Copy the API key and the client secret shown on screen. You need an active SlickText account for this.

  2. 02

    Start a connection in Make

    Add any SlickText (legacy) module to your scenario and click Create a connection. A connection is your SlickText account linked to Make once, then reused by every SlickText module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste your credentials

    Enter the API key and client secret you copied, or follow the instructions Make shows on screen, then save. Once the connection works, the module fields open up and you can fill them in.

First scenario

Your first scenario with SlickText (legacy)

GoalWhen a new contact appears in SlickText (legacy), Make sends that contact a welcome text.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for SlickText (legacy) and pick Watch Contacts.

  2. 02

    Link your account

    Click Create a connection and paste your API key and client secret. Make can now read your contacts, and the module fields show what it found once the connection exists.

  3. 03

    Add the welcome text

    Click the + on the right of Watch Contacts and choose Send a Message to a Contact. Map the contact from the first module, so each new person, one bundle each, gets their own text.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles each module received. Check that the right contact came through before any real message goes out.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default. Adjust it if your plan allows, then switch the scenario on so it runs without you.

Triggers

What starts a SlickText (legacy) scenario

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

SlickText (legacy)1Watch Contacts

Watch Contacts

triggerIn the docs only

You get a scenario that reacts to your contact list: each contact it picks up becomes a bundle, one item passed to the next module, ready to be texted, tagged or copied to another tool.

How it fires
scheduled. Make checks SlickText on the scenario's schedule, every 15 minutes by default, and at 15 minutes minimum on the Free plan. The Make documentation lists this module without a type, so the scheduled behavior comes from its name; confirm it with Run once.
When to use it
a signup form feeds your SMS list and every new subscriber should get a greeting or land in your CRM.
Modules

What SlickText (legacy) can do in Make

SlickText (legacy) gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SlickText (legacy)1

Delete a Contact

ActionIn the docs only

This one removes a contact from your SlickText account, so your list only keeps people you should still be texting after a cleanup or a data request.

When to use it
a customer asks to have their data erased and another tool records that request.
Watch out
treat a deletion as final and test on a dummy contact first.
SlickText (legacy)2

Edit a Contact

ActionIn the docs only

Your SlickText records stay accurate because this module updates an existing contact with fresh details coming from the tool you treat as the reference.

When to use it
a customer changes their name or details in your store or CRM and SlickText should follow.
Watch out
it changes one contact, so find the right one first with Search Contacts.
SlickText (legacy)3

Get a Contact

ActionIn the docs only

With a single contact already identified, this module fetches its record so the next steps of the scenario can reuse what SlickText knows about that person.

When to use it
you already hold the contact reference and want its details before deciding whether to send a text.
Watch out
it reads one contact; to look someone up by what you know, use Search Contacts.
SlickText (legacy)4

Make an API Call

ActionIn the docs only

Anything the listed modules leave out becomes reachable: this module calls any endpoint of the SlickText API, using the connection you already created, with no second login.

When to use it
you need an operation that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the SlickText API documentation open while you build it.
SlickText (legacy)5

Opt-in a Contact

ActionIn the docs only

A subscriber who said yes somewhere else gets recorded as opted in inside SlickText, so the consent you collected follows them into your texting tool.

When to use it
a customer ticks the SMS box at checkout or on a form outside SlickText.
Watch out
run it only on a real consent event, never as a bulk fix on a whole list.
SlickText (legacy)6

Opt-out a Contact

ActionIn the docs only

The opposite gesture keeps you respectful: this module records that a contact no longer wants your texts, while their record stays in the account.

When to use it
someone unsubscribes in your CRM, your newsletter tool or through a support ticket.
Watch out
pick this rather than Delete a Contact when you want to keep the history of that person.
SlickText (legacy)7

Search Contacts

SearchIn the docs only

Finding the right person before acting on them is what this search does: it looks through your SlickText contacts and hands back the matches it finds.

When to use it
another app gives you a customer and you need the matching SlickText contact before editing or opting them out.
Watch out
a search can return zero, one or several bundles, and each one runs the next modules.
SlickText (legacy)8

Send a Message to a Contact

ActionIn the docs only

One person, one text: this module sends an SMS to a single contact, which suits confirmations, reminders and welcome messages triggered by an event.

When to use it
an order ships, an appointment is booked or a new subscriber joins, and that person should hear about it.
Watch out
each bundle sends one text and uses one operation, so check with Run once how many arrive.
SlickText (legacy)9

Send a Message to a Textword List

ActionIn the docs only

Broadcasts get simpler here, since this module texts everyone on one of your Textword lists in a single step instead of looping over contacts.

When to use it
a product launch, a flash sale or a store closing that the whole list should know about.
Watch out
place it after a module that returns one bundle only, or the list gets the text several times.
Need help

Need help automating SlickText (legacy) with Make?

A person reads every message.

FAQ

SlickText (legacy) and Make: common questions

01Is the SlickText (legacy) Make integration free?
Yes, on the Make side. SlickText (legacy) is a standard app, so it is available from the Free plan. 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 go down to a 1 minute interval with unlimited active scenarios, and usage is counted in operations each month. You still need an active SlickText account, whose price depends on SlickText, not on Make.
02What is needed to connect SlickText (legacy) to Make?
An active SlickText account and its API credentials. In the SlickText dashboard, open the account page, go to the API section and click Generate API Keys, then copy the API key and the client secret displayed. In Make, add a SlickText (legacy) module, click Create a connection, optionally name it, and paste both values. The connection is then reused by every SlickText module in your scenarios, so this setup happens only once.
03Does the SlickText (legacy) trigger work in real time?
No. Watch Contacts is a scheduled trigger: Make checks SlickText on the scenario's schedule instead of being called by the app. A new scenario runs every 15 minutes by default, 15 minutes is the minimum on the Free plan, and paid plans can go down to 1 minute. The Make documentation does not state the type, which is inferred from the module's name, so verify the behavior with Run once. There is no instant trigger for this app.
04What if a SlickText (legacy) module is missing in Make?
Use Make an API Call. This module can reach any endpoint of the SlickText API with the connection you already set up, which covers what the 10 listed modules leave out. The Make documentation for this app is brief and marked as AI-generated from SlickText's own docs, so check important details against SlickText's documentation and contact SlickText if something looks wrong. Test every new call with Run once before switching the scenario on.
05Should SlickText (legacy) be automated with Make or n8n?
It depends on the tool your team already uses. On Make, this app offers 10 modules: a scheduled Watch Contacts trigger, contact edits, opt-in and opt-out, searches, texts to one contact or to a Textword list, and Make an API Call for the rest. The same app may also have an n8n node. Compare the modules each side offers for your actual flow, and pick the editor where your other scenarios already live.
Same platform

Other docs you might need on this stack.

Browse all integrations