Resources · Make integration

SlickText Make integrationAutomate SlickText with Make.

Can Make react the moment someone joins your SlickText audience? Yes. The SlickText Make integration gives you 18 modules, 5 of them instant triggers, and none of them needs code. This guide links your account, then walks you through a first working scenario.

Try the SlickText integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SlickText Make integration automate?

The SlickText Make integration lets Make watch your SlickText contacts and inbox, then act on them for you: send a message, sort a contact into lists, or update a record. You build it as a scenario, the automation you assemble in Make from modules, the small bricks that each do one job.

A welcome text that never gets forgotten. Watch Created Contacts fires as soon as someone is added, and Send Message to Contact greets them right away. A gym or a salon can greet every new member without anyone opening SlickText.

A clean audience fed by your other tools. When a form or a store records a customer, Create or Update a Contact adds them or refreshes the existing record, and Add a Contact to List files them under the right list. No duplicates to clean up later.

Replies that reach the right person. Watch Received Messages passes each inbox reply to Make, which can forward it to your help desk or a team chat so a human answers.

Where a listed module stops, Make an API Call reaches any other endpoint of the SlickText API with the same connection. The Make documentation lists no specific limit for this app. SlickText may also have an n8n node; the n8n vs Make comparison helps you pick a tool, and the Make training covers the editor from scratch. If a run fails, start with Make troubleshooting.

Connect

How do you connect SlickText to Make?

  1. 01

    Create an API key in SlickText

    In your SlickText dashboard, open Settings, then API and Webhooks and API Keys. Click Create API Key and copy the key shown on screen. You need an active SlickText account for this.

  2. 02

    Add a SlickText module in Make

    In your scenario, add any SlickText module 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.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then save. Make can now read your contacts and lists, and the fields of the module fill in from your own account.

First scenario

Your first scenario: a welcome message for every new contact

GoalWhen a contact is created in SlickText, Make sends that contact a welcome message.

  1. 01

    Start a new scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module. Everything you add from here sits on one canvas.

  2. 02

    Add Watch Created Contacts

    Search for SlickText and pick Watch Created Contacts. Click Create a webhook, then Create a connection, and paste your API key when Make asks for it.

  3. 03

    Chain Send Message to Contact

    Click the + on the right of the trigger and add Send Message to Contact. Map the contact from the trigger into the module, then type your welcome text.

  4. 04

    Test with Run once

    Click Run once, then add a test contact in SlickText, ideally with your own number. Each module shows the bundle it received, one bundle being one item passed along, here one contact.

  5. 05

    Switch the scenario on

    When the test message lands, switch the scenario on. Each run of each module counts as one operation, the unit Make uses to measure usage on your plan.

Triggers

Which SlickText triggers can start a scenario?

5 modules start a scenario when something happens in SlickText. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SlickText as soon as it happens.

SlickText1Watch Created Contacts

Watch Created Contacts

Instant trigger

In Make“Triggers when a contact is created.”

Starts your scenario the moment a new person lands in your SlickText contacts, so every follow-up happens while their interest is fresh. The trigger hands Make the new contact as a bundle you can map into later modules.

How it fires
instant, SlickText calls Make through a webhook as soon as the contact is created.
When to use it
welcome texts, a copy of each new signup in your CRM, or a ping to your sales team.
Watch out
create the webhook before the connection, or the trigger stays silent.
SlickText2Watch Deleted Contacts

Watch Deleted Contacts

Instant trigger

In Make“Triggers when a contact is deleted.”

Tells Make when a contact disappears from SlickText, which keeps your other tools from messaging someone who is no longer in your audience. Pair it with a module in your CRM or spreadsheet that removes or flags the same person.

How it fires
instant, SlickText notifies Make through a webhook right after the deletion.
When to use it
keeping a mailing tool or a customer sheet in step with SlickText.
Watch out
the contact is already gone in SlickText, so a later SlickText lookup on it will find nothing.
SlickText3Watch Inbox Status

Watch Inbox Status

Instant trigger

In Make“Triggers when the status of an inbox conversation is changed.”

Lets you act on the life of a conversation rather than on single messages: Make hears about it whenever the status of an inbox conversation changes. That gives you a clean signal to log, report or alert on without polling anything.

How it fires
instant, SlickText sends the change to Make through a webhook as soon as it happens.
When to use it
logging closed conversations in a support sheet, or alerting a manager when a thread is reopened.
Watch out
it reports status changes only; new replies come through Watch Received Messages.
SlickText4Watch Received Messages

Watch Received Messages

Instant trigger

In Make“Triggers when an inbox message is received.”

Brings every incoming inbox message into Make, so a customer reply can reach the person who should answer it, wherever they work. Each message arrives as its own bundle, ready to be sent to a chat, a ticket or a spreadsheet.

How it fires
instant, SlickText calls Make through a webhook as soon as the message is received.
When to use it
turning replies into help desk tickets or team chat posts.
Watch out
if the scenario sends a text back, check it cannot answer its own messages in a loop.
SlickText5Watch Updated Contacts

Watch Updated Contacts

Instant trigger

In Make“Triggers when an existing contact is updated.”

Gives your scenario a nudge whenever an existing contact changes in SlickText, so the copy of that person in your other tools never drifts. The updated contact reaches Make as a bundle you can map field by field into the next module.

How it fires
instant, SlickText notifies Make through a webhook as soon as the update is saved.
When to use it
syncing profile changes back to a CRM or an order system.
Watch out
if a later module updates the same contact in SlickText, the trigger fires again; add a filter to avoid a loop.
Modules

What can SlickText do inside a scenario?

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

SlickText1

Add a Contact to List

Action

In Make“Adds an existing contact to one or more lists.”

Files a contact who already exists in SlickText under one or more lists, so the right campaigns reach them later without manual sorting.

When to use it
after a purchase or a form choice, to tag a customer by product or interest.
Watch out
the contact has to exist first; place Create or Update a Contact before it when in doubt.
SlickText2

Create a Custom Field

Action

In Make“Creates a new SlickText custom field. Creating a custom field will make that field available for all contacts in your brand.”

Adds a new custom field to SlickText, and that field becomes available on every contact of your brand. It lets a scenario store data your default fields do not cover.

When to use it
once, while setting up, before other modules start writing values into that field.
Watch out
the field applies brand-wide, so keep this module out of scenarios that run on every contact.
SlickText3

Create a List

Action

In Make“Creates a new, empty list in SlickText.”

Opens a brand-new, empty list in SlickText, ready to receive contacts from the next modules of the same scenario.

When to use it
when a new event, store opening or product launch needs its own audience, created from a row in a spreadsheet or a project tool.
Watch out
the list starts empty; chain Add a Contact to List to fill it.
SlickText4

Create or Update a Contact

Action

In Make“Creates a new contact if the number is not found or updates the existing contact.”

Keeps one record per person: if the mobile number is not in SlickText yet, the module creates the contact, and if it is, it updates the existing one. That spares you a search step and duplicate profiles.

When to use it
whenever a form, a store or a CRM sends you a customer and you are not sure they already exist.
Watch out
the match runs on the number, so format numbers the same way everywhere.
SlickText5

Delete a Contact

Action

In Make“Deletes an existing contact.”

Removes an existing contact from SlickText, which keeps your audience clean when someone leaves in another tool you use.

When to use it
when a customer closes their account or asks to be erased from your CRM, and SlickText must follow.
Watch out
treat a deletion as final and run the scenario on test contacts before switching it on.
SlickText6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Covers what the other SlickText modules do not: it sends an authorized request to any endpoint of the SlickText API, reusing the connection you already created.

When to use it
when the SlickText API offers an action that has no module of its own in Make.
Watch out
you write the request yourself, so keep the SlickText API documentation open while you set it up.
SlickText7

Remove a Contact from a List

Action

In Make“Removes a contact from one or more lists.”

Takes a contact out of one or more lists while keeping the contact itself in SlickText, so they stop receiving campaigns aimed at those lists.

When to use it
when a trial turns into a paid plan and the person should leave the trial list.
Watch out
to erase the person entirely, you need Delete a Contact instead.
SlickText8

Retrieve a Contact

Action

In Make“Retrieves a single contact by mobile number or contact ID.”

Fetches one contact from SlickText by mobile number or contact ID, so later modules can use their details in a message or a record.

When to use it
when your trigger only gives you a phone number and you need the full SlickText profile.
Watch out
it returns a single person; to pull several at once, Search Contacts fits better.
SlickText9

Send a Campaign

Action

In Make“Sends a campaign message to subscribed contacts on selected lists and segments.”

Sends a campaign message to the subscribed contacts of the lists and segments you pick, straight from a scenario.

When to use it
when an event in another tool, like a new product going live in your store, should reach one targeted audience.
Watch out
only subscribed contacts on those lists or segments receive it, so check who is inside before a real send.
SlickText10

Send a Campaign to All

Action

In Make“Sends a campaign message to all subscribed contacts.”

Sends one campaign message to every subscribed contact you have in SlickText, with no list or segment to choose.

When to use it
for news that concerns everyone, such as an unplanned closure announced from a shared calendar or a status page.
Watch out
it reaches your whole audience at once; test on a small list with Send a Campaign first.
SlickText11

Send Message to Contact

Action

In Make“Sends a single message to an existing contact.”

Sends one message to one existing contact, which makes it the module for personal, event-driven texts rather than broadcasts.

When to use it
an order confirmation, an appointment reminder triggered by a booking, or a welcome after signup.
Watch out
the contact must already exist in SlickText; create or update them in an earlier module if needed.
SlickText12

List Contacts

Search

In Make“Retrieves all contacts on a list.”

Returns every contact on a list you choose, each one as a separate bundle, so the modules after it run once per person.

When to use it
exporting a list to a spreadsheet or copying its members into another tool.
Watch out
a long list means many bundles, and every module that follows uses one operation per bundle.
SlickText13

Search Contacts

Search

In Make“Searches and retrieves contacts by specified attributes. Leave blank to retrieve all contacts.”

Finds contacts by the attributes you set and returns zero, one or many results; leave the criteria empty and it returns all of them.

When to use it
checking whether a customer already exists before you act, or pulling a group that shares one attribute.
Watch out
an empty search brings back your whole audience, so add a filter before any send module.
Need help

Need help automating SlickText with Make?

A person reads every message.

FAQ

SlickText and Make: frequently asked questions

01Is the SlickText Make integration free?
Yes, on the Make side. SlickText is a standard app, so it works from the Free plan onward. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. You still need an active SlickText account with its own subscription.
02What do you need to connect SlickText to Make?
An active SlickText account and an API key. In SlickText, go to Settings, then API and Webhooks, then API Keys, click Create API Key and copy it. In Make, add a SlickText module, click Create a connection, give it a name if you like and paste the key. For the five triggers, which are instant modules, click Create a webhook first and then Create a connection. The same connection serves every SlickText module afterwards.
03Do SlickText triggers in Make work in real time?
Yes. All five SlickText triggers are instant: Watch Created Contacts, Watch Deleted Contacts, Watch Inbox Status, Watch Received Messages and Watch Updated Contacts. SlickText calls Make through a webhook as soon as the event happens, instead of Make checking on a schedule. That is why these modules show a lightning badge in the editor and ask you to create a webhook during setup. The scenario must be switched on for Make to receive those calls.
04What if the SlickText module you need is missing in Make?
Use Make an API Call. It sends an authorized request to any endpoint of the SlickText API, with the connection you already set up, so it covers actions the 18 listed modules do not offer. You write the request from the SlickText API documentation. The Make documentation for this app lists no specific limit, and it notes that its content is AI-generated from the SlickText documentation, so verify important details with SlickText directly.
05Should you use Make or n8n for SlickText?
It depends on what the rest of your workflow runs on. In Make, SlickText comes with 18 modules: 5 instant triggers, 11 actions and 2 searches, including Make an API Call for anything else. SlickText may also have an n8n node. Compare the actions each side offers for your use case before you choose, and prefer the tool your team already knows. Neither option is ranked here; the n8n vs Make comparison on this site lays out the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations