Resources · Make integration

SugarSync Make integrationAutomate SugarSync with Make.

Your SugarSync folders can move files around on their own. The SugarSync Make integration gives you 16 modules: 2 triggers that spot new files or photos, plus actions and searches. This guide links your account and walks you through a first working scenario.

Try the SugarSync integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SugarSync Make integration do for you?

The SugarSync Make integration links your SugarSync account to Make, a visual automation tool, so files and folders react to events without manual clicks. You build a scenario, which is the automation itself: a chain of modules, each one a single brick such as a trigger, an action or a search.

A backup copy for every new file. Watch New Files spots what lands in a folder, Get a File fetches it, and Upload a File drops a copy into a separate backup folder, so a shared drop zone never holds the only version.

Photo albums that feed other tools. Watch New Photos in Album picks up each new picture in an album you choose. A studio can pass those photos to a design tool, a chat channel or a spreadsheet log handled by another app in the same scenario.

Tidy folders on demand. List Folders and List Files return what sits in a directory; Archive a File, Archive a Folder or Delete a File then clean up. Start small and test before you let a scenario remove anything.

One honest limit: Make says its SugarSync documentation is incomplete, because little public information exists about the app. Expect to discover some settings in the editor itself. The Make troubleshooting guide helps when a run fails, and the Make pricing page explains how operations are counted. If you are also weighing n8n, the n8n vs Make comparison lays out the differences between the two tools.

Connect

How do you connect SugarSync to Make?

  1. 01

    Add a SugarSync module

    Open a scenario, click the +, search for SugarSync and pick any module. When Make asks for an account, click Create a connection. A connection is your SugarSync account linked once, then reused by every SugarSync module.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, such as the team or the account it belongs to. Make then sends you to SugarSync to approve access, or asks for the key the app gives you. Approve it with the account that owns the folders.

  3. 03

    Save and check the folders

    Click Save. Back in the module, open a folder field: once the connection works, Make lists the folders it can read, so you pick them instead of typing a path by hand.

First scenario

Build your first scenario: back up every new SugarSync file

GoalWhen a file lands in a SugarSync folder, Make fetches it and uploads a copy to a backup folder.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for SugarSync and pick Watch New Files as the first module.

  2. 02

    Point the trigger at a folder

    Pick your connection, then choose the folder to watch from the list Make shows. Every new file there becomes one bundle, meaning one item passed along to the next module.

  3. 03

    Fetch the file

    Click the + on the right, add Get a File and map the file from the trigger. Mapping means clicking the value the previous module returned instead of typing it.

  4. 04

    Upload the copy

    Add Upload a File, map the data from Get a File and choose a backup folder. Pick a folder other than the watched one, or each copy would start the scenario again.

  5. 05

    Test, schedule, switch on

    Drop a file in the folder and click Run once to read what each module received. Then set the schedule on the first module, every 15 minutes by default, and switch the scenario on.

Triggers

What starts a SugarSync scenario

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

SugarSync1Watch New Files

Watch New Files

Scheduled trigger

In Make“Watches for new files in a specified directory.”

This trigger gives you a scenario that reacts to every new file in a SugarSync directory you pick. Each file it finds arrives as its own bundle, ready to be fetched, copied, logged or announced by the modules that follow.

How it fires
it is a scheduled trigger, so Make checks the app on the scenario's schedule. A new scenario checks every 15 minutes by default; the Free plan cannot go below that, paid plans can go down to 1 minute.
When to use it
a shared intake folder where colleagues or clients drop contracts, invoices or briefs that need the same handling each time.
Watch out
never write files back into the watched directory, or the scenario keeps triggering on its own output.
SugarSync2Watch New Photos in Album

Watch New Photos in Album

Scheduled trigger

In Make“Watches for new photos in a specified album.”

Here the scenario starts from pictures instead of documents: each new photo added to a SugarSync album you choose comes through as one bundle. That gives a photographer or a marketing team a way to route fresh images without opening the album.

How it fires
scheduled, so Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario. Nothing is pushed to Make the moment a photo lands.
When to use it
an album that collects event or product shots which should reach another tool, such as a chat channel or an asset sheet.
Watch out
it only looks at albums, so a picture saved in a plain folder calls for Watch New Files instead.
Modules

What SugarSync can do inside a scenario

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

SugarSync1

Archive a File

Action

In Make“Archives a specified file.”

Archive a File takes one specific file out of your working folders, so they stay short. As the name suggests, it sets the file aside rather than erasing it: a fit for work that is finished but worth keeping.

When to use it
after a signed contract has been copied elsewhere, archive the original that sat in the intake folder.
Watch out
Make does not document where archived files end up, so run it once on a test file before relying on it.
SugarSync2

Archive a Folder

Action

In Make“Archives a specified folder.”

With Archive a Folder, a whole directory leaves your active tree in one step instead of file by file. That keeps closed projects out of the way; as with any archive, the aim is to set them aside, not to erase them.

When to use it
a project is marked as closed in your CRM, and its SugarSync folder should follow.
Watch out
it acts on everything inside the folder, so map the right folder rather than a parent one by mistake.
SugarSync3

Create a Folder

Action

In Make“Creates a new folder.”

Create a Folder gives every new client, order or project its own place in SugarSync the moment the event happens elsewhere. You stop building the same folder structure by hand.

When to use it
a deal is won or a form is submitted, and the team needs a dedicated folder ready before the first file arrives.
Watch out
map the new folder's reference into later modules so the next uploads land inside it.
SugarSync4

Create a Text File

Action

In Make“Creates a new file with .txt extension.”

This module writes a brand new file with a .txt extension straight into SugarSync, filled with text mapped from earlier modules. It is the quickest way to leave a readable note next to other files.

When to use it
save a short summary of a form answer or an email beside the documents of the same client.
Watch out
it only produces plain text; for any other file type, pass data to Upload a File.
SugarSync5

Delete a File

Action

In Make“Deletes a specified file.”

Delete a File removes one file you point to, which keeps temporary or duplicate files from piling up after a scenario has used them.

When to use it
a scan was copied to its final folder and the leftover in the drop zone is no longer needed.
Watch out
a deletion from a scenario cannot be undone by Make, so test it on a dummy file with Run once, and prefer Archive a File when in doubt.
SugarSync6

Delete a Folder

Action

In Make“Deletes a specified folder.”

When a directory has served its purpose, Delete a Folder removes it in a single step rather than emptying it file by file. Useful for scratch folders that a scenario creates for its own work.

When to use it
a temporary folder built for one batch of files is empty and no longer referenced.
Watch out
everything inside goes with it, so double check the mapped folder before switching the scenario on.
SugarSync7

Get a File

Action

In Make“Retrieves a file.”

Get a File retrieves one file from SugarSync so the next modules can work with its content: send it as an attachment, copy it or pass it to another app.

When to use it
right after Watch New Files, when the trigger tells you a file exists but the following step needs the file itself.
Watch out
each retrieval counts as an operation, and the Free plan caps files at 5 MB, so large media may call for a paid plan.
SugarSync8

Get a Folder

Action

In Make“Returns information about a specified folder.”

Get a Folder returns information about one directory, which lets a scenario confirm what it is about to touch before acting on it. Think of it as reading the label on a box.

When to use it
check a client folder's details before archiving it or before routing files into it.
Watch out
it describes the folder rather than listing its content; to see the files inside, reach for List Files.
SugarSync9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call covers whatever the other SugarSync modules leave out: it calls any endpoint of the SugarSync API from your scenario, reusing the same connection you already created.

When to use it
you need a SugarSync feature that has no dedicated module in the list above.
Watch out
you have to know the endpoint and its parameters yourself, and Make's own SugarSync documentation is limited, so check SugarSync's references first.
SugarSync10

Update a File

Action

In Make“Updates file information.”

Update a File changes the information attached to a file that already exists, so its details stay consistent without renaming things by hand in SugarSync.

When to use it
once an invoice is marked as paid in accounting, bring the matching file's details in line with that status.
Watch out
it edits the file's information, not its content; to replace the content, upload a new file instead.
SugarSync11

Update a Folder

Action

In Make“Updates the information of a specified folder.”

With Update a Folder, the details of an existing directory follow what happens in your other tools, such as a project that changes status or owner.

When to use it
a client renames their company in the CRM and the folder holding their files should reflect it.
Watch out
map the folder from a search or a trigger rather than typing it, so the change hits the right directory every run.
SugarSync12

Upload a File

Action

In Make“Uploads a new file.”

Upload a File puts a new file into the SugarSync folder you choose, using file data received from an earlier module or another app. Attachments, exports and generated documents all end up stored in one place.

When to use it
save each attachment of an incoming email into the matching client folder.
Watch out
never target the folder a Watch New Files trigger is watching, or each upload restarts the scenario.
SugarSync13

List Files

Search

In Make“Returns a list of files.”

List Files returns the files sitting in SugarSync as a set of results, one bundle per file, which the next modules then treat one by one. It is the starting point of any cleanup or report.

When to use it
build an inventory of a folder in a spreadsheet, or pick the files that should be archived.
Watch out
a search can return zero, one or many bundles, and every later module runs once per bundle, which multiplies operations.
SugarSync14

List Folders

Search

In Make“Returns a list of folders.”

List Folders hands back the directories in SugarSync, one bundle per folder, so a scenario can walk through them instead of relying on a single hard-coded one.

When to use it
find the folder of a given client by name before uploading into it or archiving it.
Watch out
add a filter after the search when you expect one folder; without it, every folder found goes down the rest of the scenario.
Need help

Need help automating SugarSync with Make?

A person reads every message.

FAQ

SugarSync and Make: common questions

01Is the SugarSync Make integration free?
Yes, SugarSync is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops a run after 5 minutes, handles files up to 5 MB and includes 512 MB of data transfer. Paid plans such as Core, Pro, Teams and Enterprise lift those limits: 1 minute intervals, unlimited active scenarios and runs up to 40 minutes. Usage is counted in operations, one per module run on one bundle. Your SugarSync subscription is a separate matter handled on SugarSync's side.
02What do you need to connect SugarSync to Make?
A SugarSync account and a Make account, nothing more according to Make's documentation, which lists no specific prerequisite. You add any SugarSync module, click Create a connection, optionally name it, approve access on SugarSync's page or paste the key the app provides, then click Save. The connection is stored once and reused by all 16 SugarSync modules. Make notes that its SugarSync documentation is incomplete, so if something looks off, check the account you approved with before anything else.
03Do SugarSync triggers in Make run in real time?
No. Both SugarSync triggers, Watch New Files and Watch New Photos in Album, are scheduled triggers. Make checks SugarSync on the scenario's schedule rather than being alerted by the app. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can check as often as every minute. Each check that finds new files or photos passes them on as separate bundles, so several items can arrive together after a quiet interval.
04What if a SugarSync module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the SugarSync API from your scenario with the connection you already set up, so features without a dedicated module stay within reach. The catch is that you need to know the endpoint and its parameters, and Make says its own SugarSync documentation is limited because little public information exists about the app. Test each call with Run once and read the returned bundle before building the rest of the scenario around it.
05Should you use Make or n8n for SugarSync?
It depends on the tool you already work in. On Make, SugarSync comes with 16 ready modules, 2 scheduled triggers and an API call module, all usable from the Free plan. Many apps also have an n8n node, so check the n8n side for SugarSync before choosing. Compare how each tool fits your team and the rest of your stack rather than the app alone. If your other automations already live in Make, keeping SugarSync there means one editor and one place to monitor runs.
Same platform

Other docs you might need on this stack.

Browse all integrations