Resources · Make integration

Sling Make integrationAutomate Sling with Make.

Can your shift team's tasks, notes and messages update themselves? The Sling Make integration gives you 37 modules: 29 actions and 8 searches. This guide is for managers who run schedules in Sling, and it walks you from the first connection to a working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Sling Make integration automate?

The Sling Make integration lets Make write into your Sling account for you: it creates tasks, shift notes, messages, sales and groups, updates or deletes them, and reads them back. You build a scenario, the automation made of modules, where each module is one brick that does one job in one app.

Requests that turn into tasks. A store gets a maintenance request through a form. Another app's module receives it, Create a Task puts it in Sling, and Create a Task Comment attaches the details, so the next shift finds everything in one place.

Teams that stay in sync with your HR tool. When someone joins or moves location, Add a User to a Group and Remove a User from a Group keep Sling groups aligned with the staff list you already maintain elsewhere.

Sales figures that stop being retyped. A restaurant closing its till can send the total to Sling with Create a Sale, then correct it later with Update a Sale instead of editing by hand.

Two limits to know before you start. Sling has no trigger in Make, so a scenario never starts on its own because something changed in Sling: it starts on Make's schedule or on another app's event. And the documentation gives no figures on limits, so test with Run once before you rely on a scenario. Sling may also exist on n8n; if you are weighing both tools, read n8n vs Make. To learn the editor step by step, see Make training, and check Make pricing before you scale.

Connect

How do you connect Sling to Make?

  1. 01

    Add a Sling module

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

  2. 02

    Name the connection

    This field is optional, yet worth filling. A name such as the location or the admin account tells you at a glance which Sling account a module writes to, which matters as soon as you manage more than one.

  3. 03

    Authorize and save

    Depending on what Sling asks, approve Make's access on the Sling page that opens or paste the key Sling gives you. Then click Save. Make can now list the groups, tasks and conversations your account can see.

First scenario

Your first scenario with Sling

GoalWhen a request arrives in another app, Make creates a Sling task and adds a comment with the details.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Sling has no trigger, so the first module comes from the app where requests arrive, such as your form tool.

  2. 02

    Add Create a Task

    Click the + on the right of the first module, search Sling and pick Create a Task. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the request

    Fill the task with data from the first module: click a field and pick the values it received. Once connected, Make lists what it can read in your Sling account, so no need to type identifiers.

  4. 04

    Attach the details

    Add Create a Task Comment after the task and point it to the task the previous module just created. The comment carries the longer text, so the task title stays short.

  5. 05

    Test with Run once

    Click Run once and send a test request. Each module shows the bundles it received, a bundle being one item passed along. Check that the task and its comment appear in Sling.

  6. 06

    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 one bundle counts as one operation on your Make plan.

Modules

What Sling can do in Make

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

Sling1

Add a User to a Group

Action

In MakeAdds a user to the selected group.

Places a person in the Sling group you choose, so they get what that group sees without anyone clicking through the admin screens.

When to use it
a new hire is confirmed in your HR tool and must appear in the right location or team group.
Watch out
when someone changes team, pair it with Remove a User from a Group, or the person stays in both.
Sling2

Create a Conversation

Action

In MakeCreates a new conversation.

Opens a fresh conversation in Sling, which gives your scenario a place to post messages that a whole situation can share.

When to use it
an incident is logged in another tool and the people handling it need their own thread in Sling.
Watch out
it opens one conversation for every bundle it receives, so feed it one bundle per situation if you want a single thread.
Sling3

Create a Day Part

Action

In MakeCreates a new day part.

Adds a new day part to your Sling account, saving you from setting up the same slot by hand when a new pattern of work appears.

When to use it
a location opens a new service, such as a late opening, and the slot has to exist before shifts use it.
Watch out
check with List Day Parts first, or a second run creates a duplicate.
Sling4

Create a Group

Action

In MakeCreates a new group.

Builds a new group in Sling from data your scenario already has, so the structure of your teams follows the tool where it is decided.

When to use it
a new site or department is added in your HR or ops tool and Sling should mirror it.
Watch out
run Search Groups before it; a group with the same name may already exist.
Sling5

Create a Message

Action

In MakeCreates a new message.

Posts a message into a Sling conversation, which puts information from another app in front of the team where they already read.

When to use it
a delivery is confirmed by a supplier email and the floor team needs to know before they plan the stockroom.
Watch out
the conversation must exist; get it from Create a Conversation or List Conversations earlier in the flow.
Sling6

Create a Sale

Action

In MakeCreates a new sale.

Records a sale in Sling straight from your till or shop system, so the figures your managers look at stop depending on manual entry.

When to use it
a point of sale closes a day's session and sends a total you want next to the schedule.
Watch out
test with Run once on one sale first, since a wrong mapping repeats on every bundle.
Sling7

Create a Shift Note

Action

In MakeCreates a new shift note.

Writes a note on a shift, which hands the next person on duty context that would otherwise stay in someone's inbox.

When to use it
a customer complaint lands in your helpdesk and the manager on the next shift should see it before starting.
Watch out
keep the note short and map only the useful fields from the previous module; long raw text is hard to read on a phone.
Sling8

Create a Task

Action

In MakeCreates a new task.

Turns an event from another app into a Sling task, so nothing gets lost between the tool where a request arrives and the team that acts on it.

When to use it
a repair request comes in through a form and a staff member should see it in their Sling tasks.
Watch out
one bundle gives one task; if the form sends several lines, decide which ones deserve a task.
Sling9

Create a Task Comment

Action

In MakeCreates a new comment for the selected task.

Adds a comment under a task you select, which keeps follow-up details attached to the work instead of scattered in chats.

When to use it
a supplier replies about a pending repair and the answer should sit under the matching task.
Watch out
the module needs the right task; map it from Create a Task or find it with Search Tasks first.
Sling10

Delete a Day Part

Action

In MakeDeletes the selected day part.

Removes a day part you select, which clears slots that no longer match how a location works.

When to use it
a service is closed for good in your planning tool and the matching slot should disappear from Sling too.
Watch out
treat the deletion as final; point it at a test day part with Run once before the scenario touches real ones.
Sling11

Delete a Group

Action

In MakeDeletes the selected group.

Removes a Sling group you select, keeping the account tidy when a team or site stops existing.

When to use it
a location is marked as closed in the system where your company tracks its sites.
Watch out
check with Get a Group that you hold the right one; a mapping mistake here removes a group people still use, and nothing in the scenario brings it back.
Sling12

Delete a Message

Action

In MakeDeletes the selected message.

Takes down a message you select from a conversation, useful when an automated post turns out to be wrong.

When to use it
a scenario posted an announcement that was cancelled at the source, and the team should no longer see it.
Watch out
you need the message itself; store it from Create a Message or find it with List Messages before deleting.
Sling13

Delete a Sale

Action

In MakeDeletes the sale.

Erases a sale from Sling, which lets a cancelled transaction disappear from the numbers without manual cleanup.

When to use it
your shop system voids a ticket that a scenario had already pushed to Sling.
Watch out
prefer Update a Sale when only the amount is wrong; deleting removes the record instead of fixing it.
Sling14

Delete a Shift Note

Action

In MakeDeletes the selected shift note.

Removes a note from a shift, so outdated warnings stop appearing to the people on duty.

When to use it
the helpdesk ticket behind a note is resolved and the next manager no longer needs the alert.
Watch out
a note edited by hand in Sling goes too; if the team adds their own text, consider Update a Shift Note instead.
Sling15

Delete a Task

Action

In MakeDeletes the selected task.

Removes a task you select, keeping the task list clean when the reason for it vanishes upstream.

When to use it
a request is withdrawn in the form tool before anyone in the team starts on it.
Watch out
if the history matters, change the task with Update a Task rather than deleting it.
Sling16

Delete a Task Comment

Action

In MakeDeletes the selected comment for the selected task.

Removes one comment from a task and leaves the task itself in place, which is handy when a single automated remark is wrong.

When to use it
a scenario posted duplicate comments on a task during a test and you want the thread clean again.
Watch out
the module needs both the task and the comment; List Task Comments gives you the second one.
Sling17

Get a Group

Action

In MakeReturns information about the selected group.

Reads the details of one group, so later modules can use its information without you copying it anywhere.

When to use it
before sending a message or adding a user, you want to confirm the group matches what your HR tool says.
Watch out
it returns one group you already know; to find a group by what it contains, use Search Groups.
Sling18

Get a Sale

Action

In MakeReturns information about the sale.

Fetches one sale from Sling, which lets you send its details to a spreadsheet or a report without exporting by hand.

When to use it
your accountant flags a transaction and you want its Sling record next to the invoice.
Watch out
the module reads a sale you point to, so keep a reference from the scenario that created it.
Sling19

Get a Shift Note

Action

In MakeReturns information about the selected shift note.

Pulls the content of one shift note into your scenario, ready to be forwarded or archived elsewhere.

When to use it
a note raised by the team needs to reach the maintenance contractor through email or another channel.
Watch out
to go through several notes at once, List Shift Notes fits better than calling this module in a loop.
Sling20

Get a Task

Action

In MakeReturns information about the selected task.

Returns the current state of one task, so a scenario can decide what to do based on what Sling holds right now.

When to use it
before posting a comment or closing the request in your ticket tool, you check the task in Sling first.
Watch out
the module targets one task you already know; to find tasks by what they contain, Search Tasks is the right choice.
Sling21

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Calls any endpoint of the Sling API with the connection you already set up, which covers what the other Sling modules leave out.

When to use it
you need an action on Sling data that none of the listed modules offers.
Watch out
you write the request yourself, so keep the Sling API documentation open and test with Run once before activating.
Sling22

Remove a User from a Group

Action

In MakeRemoves the user from the selected group.

Takes a person out of a group, so access in Sling follows departures and transfers without a manager having to remember them.

When to use it
your HR tool records that an employee moves to another site or leaves the company.
Watch out
the person stays in Sling; only the membership of that group changes.
Sling23

Update a Day Part

Action

In MakeUpdates the selected day part.

Changes an existing day part, which lets a new planning decision reach Sling without rebuilding the slot.

When to use it
the opening hours of a service change in the tool where your ops team decides them.
Watch out
point it at a test day part first and check the result with Run once.
Sling24

Update a Group

Action

In MakeUpdates the selected group.

Edits a group that already exists, so a renamed team or site shows the same name in Sling as everywhere else.

When to use it
a store is renamed after a rebrand and your staff list already carries the new name.
Watch out
find the group with Search Groups first; updating by a guessed reference fails or hits the wrong group.
Sling25

Update a Message

Action

In MakeUpdates the selected message.

Rewrites a message already posted, which keeps a thread readable when a fact changes after the announcement.

When to use it
a delivery slot moves and the message your scenario posted earlier should show the new time.
Watch out
people may have read the first version; for a big change, a new message with Create a Message is clearer.
Sling26

Update a Sale

Action

In MakeUpdates the sale.

Corrects a sale in Sling, so a refund or adjustment in your shop system reaches the figures your managers read.

When to use it
a partial refund changes a total that Create a Sale had pushed earlier.
Watch out
keep the reference of the sale from the scenario that created it; without it, you cannot tell Make which sale to fix.
Sling27

Update a Shift Note

Action

In MakeUpdates the selected shift note.

Edits the text of a note already on a shift, so the team sees the latest status rather than an old alert.

When to use it
the helpdesk ticket behind a note moves forward and the manager on duty should know where it stands.
Watch out
the new text replaces what the team may have added by hand, so read it first with Get a Shift Note.
Sling28

Update a Task

Action

In MakeUpdates the selected task.

Changes a task in Sling when things move elsewhere, so the task list always tells the truth.

When to use it
the ticket behind a task is closed in your support tool and the Sling task should say so.
Watch out
two scenarios writing to the same task can overwrite each other; keep one scenario in charge of each change.
Sling29

Update a Task Comment

Action

In MakeUpdates the selected comment.

Rewrites a comment you select, which fixes an automated remark without cluttering the task with a second one.

When to use it
a supplier sends a corrected quote and the comment that quoted the first price should reflect it.
Watch out
keep the comment reference from Create a Task Comment or find it with List Task Comments.
Sling30

List Conversations

Search

In MakeLists all conversations.

Brings every conversation your account can see into the scenario, each one as a separate bundle you can filter.

When to use it
you want to post into an existing thread and need to pick it by its name rather than hard-code it.
Watch out
a search returns zero, one or many bundles, and every module after it runs once per bundle, each run costing an operation.
Sling31

List Day Parts

Search

In MakeLists all day parts.

Returns all day parts of the account, which gives your scenario the full picture before it adds or changes a slot.

When to use it
a scenario must check whether a slot already exists before calling Create a Day Part.
Watch out
every day part becomes its own bundle, and each module after it runs once per bundle, so keep the next steps light.
Sling32

List Messages

Search

In MakeLists all messages for the selected conversation.

Reads the messages of the conversation you select, which lets you archive or forward a thread without copying it.

When to use it
an incident is closed and you want its Sling discussion saved in the incident record elsewhere.
Watch out
each message becomes its own bundle; to send them as one block, place an aggregator after this module.
Sling33

List Notifications

Search

In MakeLists all notifications.

Collects the notifications of your Sling account, so their content can travel to a channel your managers watch more closely.

When to use it
a scheduled scenario picks up notifications and passes the relevant ones to email or a chat tool.
Watch out
a later run may list notifications you already forwarded, so keep track of what you sent to avoid repeats.
Sling34

List Shift Notes

Search

In MakeLists all shift notes.

Gathers the shift notes of the account as bundles, a quick way to review what the team wrote without opening each shift.

When to use it
you want notes copied into a spreadsheet where the operations lead reviews recurring problems.
Watch out
everything comes back as separate bundles, and each one costs an operation in the modules that follow.
Sling35

List Task Comments

Search

In MakeLists all comments for the selected task.

Shows every comment on the task you select, which gives a scenario the full discussion behind a piece of work.

When to use it
a task is finished and its comments should be attached to the ticket in your support tool.
Watch out
you need the task first; get it from Search Tasks or from the module that created it.
Sling36

Search Groups

Search

In MakeSearches for groups.

Finds groups matching what you look for, so your scenario works on the right team without you storing references by hand.

When to use it
a new hire's site arrives as a name from your HR tool and you need the matching Sling group before Add a User to a Group.
Watch out
a search can return several groups, and the next module then runs once for each of them, which is rarely what you want.
Sling37

Search Tasks

Search

In MakeSearches for tasks.

Looks up tasks in Sling, which lets a scenario locate existing work before creating or changing anything.

When to use it
a request comes back from your form tool and you want to know if a task already exists for it.
Watch out
zero results is a normal answer, and then the modules after it simply do not run, so plan what should happen in that case.
Need help

Need help automating Sling with Make?

A person reads every message.

FAQ

Questions about the Sling Make integration

01Is the Sling Make integration free?
Yes, Sling is a standard app in Make, so its modules work on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations: each module run on one bundle is one. Your Sling subscription itself is a separate matter between you and Sling.
02What do you need to connect Sling to Make?
A Sling account and a Make account. The Sling documentation lists no special prerequisite. You add any Sling module, click Create a connection, optionally name it, then either approve Make on the Sling page or paste the key Sling gives you, and click Save. The connection is reused by every Sling module in your scenarios, so you do this once per account. Make only sees what that Sling account can see, so connect with a user whose access covers the groups, tasks and conversations your scenarios will touch.
03Can a change in Sling start a Make scenario in real time?
No. Sling has no trigger module in Make, neither scheduled nor instant, so nothing happening in Sling can start a scenario by itself. You have two ways to start anyway. Put another app's trigger first, for example a form or HR tool, and let the Sling modules act on its data. Or start with a Sling search such as Search Tasks and let Make run the scenario on its schedule, every 15 minutes by default and at least 15 minutes apart on the Free plan, 1 minute on paid plans.
04What if the Sling module you need is missing in Make?
Use Make an API Call. It is part of the 37 Sling modules and calls any endpoint of the Sling API with the same connection, so you can reach data the other modules do not cover. You write the request yourself, so open the Sling API documentation next to it and test with Run once. The Sling documentation in Make gives no figures on limits, which is another reason to try each scenario on a small sample before you switch it on for the whole team.
05Should you use Make or n8n for Sling?
It depends on how you prefer to build. In Make, Sling comes with 37 modules, 29 actions and 8 searches, Make an API Call included, and runs from the Free plan. Sling may also be available in n8n; check its node list for the exact coverage before comparing. Then weigh the criteria that matter to you: which modules you need, how your team likes to build and maintain automations, and which tool your other apps already use. The comparison page linked above goes through these points.