Resources · Make integration

SmartSuite Make integrationAutomate SmartSuite with Make.

Can SmartSuite records create and update themselves while you work elsewhere? The SmartSuite Make integration gives you 12 modules, including 2 instant triggers, to handle records without code. This guide connects your workspace and walks you through a first scenario.

Try the SmartSuite integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SmartSuite Make integration do for you?

The SmartSuite Make integration links your SmartSuite workspace to Make, a visual tool where you chain apps together without writing code. Each automation you build there is called a scenario: it reacts when a record appears or changes, and it can create, update, find or delete records for you.

Leads that land in the right table. A sales team collecting requests in another app can send each one to SmartSuite with Upsert a Record, so a returning contact gets refreshed instead of duplicated.

A follow-up that starts the moment a record exists. Watch New Records fires as soon as someone adds a row, which lets an operations lead notify the right person or fill in missing details with Update a Record.

Cleanup done in one pass. When a project closes, Find Records pulls every matching item and Bulk Update Records or Bulk Delete Records handles them together instead of one click at a time.

Two limits to know before you start: the integration needs a paid SmartSuite account, and its modules work on records only. For any other endpoint of the SmartSuite API, Make an API Call reuses the same connection. If you already weigh Make against other tools, read our n8n vs Make comparison, then our Make review for the editor itself. Teams that prefer guided practice can look at the Make training.

Connect

How do you connect SmartSuite to Make?

  1. 01

    Generate your API key in SmartSuite

    In SmartSuite, open your Profile icon at the top right, then My Profile. In the API Key section, click + Generate New Key and copy the value shown under Your API token. Keep it somewhere safe.

  2. 02

    Open a SmartSuite module in Make

    Add any SmartSuite module to your scenario and click Create a connection. A connection is your SmartSuite account linked to Make once, then reused by every SmartSuite module. You can give it a name in Connection name.

  3. 03

    Fill in the workspace and token

    In Workspace ID, type the part of your SmartSuite URL that identifies the workspace: for https://app.smartsuite.com/workspace/home, that is workspace. Paste the key into API Token, click Save, and confirm access if asked.

First scenario

Build your first SmartSuite scenario

GoalWhen a new request arrives in another app, Make adds it to SmartSuite or refreshes the existing record.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Pick the app where your requests start, such as a form tool, and choose its trigger module.

  2. 02

    Add Upsert a Record

    Click the + on the right of that first module, search for SmartSuite and choose Upsert a Record. Use Create a connection with your workspace ID and API token.

  3. 03

    Map the incoming data

    Once connected, Make lists what it can read in SmartSuite. Pick your table, then drag each value from the first module into the matching SmartSuite field.

  4. 04

    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, here one request. Check SmartSuite for the record.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set Scheduling, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

SmartSuite triggers in Make

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

SmartSuite1Watch New Records

Watch New Records

Instant trigger

In Make“Triggers when a new record is created”

You get a scenario that starts the moment a record is created in SmartSuite, so whatever should follow a new entry happens without anyone remembering to do it.

How it fires
instant. SmartSuite calls Make through a webhook as soon as the record exists, which is why the module carries the lightning badge.
When to use it
a new client, task or request should immediately alert a colleague, feed another tool, or get completed by an Update a Record step.
Watch out
click Create a webhook before Create a connection, and avoid creating records in the same table from this scenario, or each new record will set it off again.
SmartSuite2Watch Updated Records

Watch Updated Records

Instant trigger

In Make“Triggers when a record is updated”

This one hands you every record the moment it changes, so a status switch or an edited field can drive the next step instead of waiting for someone to notice it.

How it fires
instant. SmartSuite notifies Make through a webhook right after the update, without Make polling on a schedule.
When to use it
a deal moves to won, a ticket gets closed, and another app or person must hear about it right away.
Watch out
if this scenario itself runs Update a Record on the same table, it will trigger itself in a loop; write to a different table instead.
Modules

Every SmartSuite module in Make

SmartSuite gives you 10 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

9 modules
SmartSuite1

Bulk Create Records

Action

In Make“Creates many SmartSuite records”

Adds a whole batch of new SmartSuite records in a single module, handy when a list of rows arrives at once from a spreadsheet or an export.

When to use it
you import several items together, like the attendees of an event, and want them in SmartSuite without chaining a module per row.
SmartSuite2

Bulk Delete Records

Action

In Make“Deletes many SmartSuite records”

Removes many SmartSuite records at once, which keeps a table clean after a project ends or a test import goes wrong.

When to use it
after Find Records has gathered the exact items to clear.
Watch out
it deletes whatever records it receives, so run the scenario once on a small set and read the bundles before letting it loose.
SmartSuite3

Bulk Update Records

Action

In Make“Updates many SmartSuite records”

Changes a group of existing records together, so a new status or owner reaches every item in one go instead of record by record.

When to use it
a campaign ends and all its related entries must switch to the same stage. Pair it with Find Records to pick the right items first, and keep Update a Record for single changes.
SmartSuite4

Create a Record

Action

In Make“Creates a SmartSuite record”

Turns one incoming item into a fresh SmartSuite record, the basic move for sending data from another app into your workspace.

When to use it
each form submission or signed quote should become a new row.
Watch out
it always creates, even if the same person already exists. When duplicates are a risk, Upsert a Record is the safer choice.
SmartSuite5

Delete a Record

Action

In Make“Deletes a SmartSuite record”

Erases one specific SmartSuite record, useful when an item cancelled elsewhere should disappear from your workspace too.

When to use it
a customer withdraws a request in your support tool and the matching row has to go.
Watch out
it deletes the record it is given, so make sure the one identified earlier really is the one you want gone.
SmartSuite6

Get a Record

Action

In Make“Gets a SmartSuite Record by field match or SmartSuite search syntax”

Brings back one SmartSuite record, matched on a field value or through SmartSuite search syntax, so later modules can use its data.

When to use it
you know an email or reference and need that one record's details before updating it or writing to another app.
Watch out
Make lists this module as an action returning a single record; when several could match, Find Records suits better.
SmartSuite7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call”

Opens the rest of the SmartSuite API from your scenario, using the connection you already set up, for anything the listed modules do not cover.

When to use it
you need something beyond records, and none of the other eleven modules does it.
Watch out
you write the request yourself, so keep the SmartSuite API documentation open to know what to ask for.
SmartSuite8

Update a Record

Action

In Make“Updates a SmartSuite record”

Edits one existing SmartSuite record with fresh values, keeping your workspace in step with what happens in other tools.

When to use it
a payment clears in your billing app and the client row should show it, or a new record needs details added right after creation.
Watch out
it needs the right record first, usually found by Get a Record or passed by a trigger.
SmartSuite9

Upsert a Record

Action

In Make“Upserts a SmartSuite record”

Keeps a single clean record per item: an upsert updates the record when it already exists and creates it when it does not.

When to use it
contacts or orders reach you more than once, and you want the latest version in SmartSuite without building your own search-then-decide logic.
Watch out
test with Run once on a known item to confirm it updates rather than duplicates.

Searches

1 module
SmartSuite10

Find Records

Search

In Make“Finds multiple records by field match or SmartSuite search syntax.”

Searches a SmartSuite table by field match or SmartSuite search syntax and returns every record that fits, each one as its own bundle.

When to use it
you need all the open tasks of a client, or every item to update or delete in bulk.
Watch out
the modules after it run once per record found, and each run counts as an operation, so narrow the search before connecting heavy steps.
Need help

Need help automating SmartSuite with Make?

A person reads every message.

FAQ

SmartSuite and Make: common questions

01Is the SmartSuite Make integration free?
On the Make side, yes: SmartSuite is a standard app available from the Free plan. That 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 Make plans lower the interval to 1 minute and allow unlimited active scenarios. The catch sits on the SmartSuite side: the integration requires a paid SmartSuite account, so a free SmartSuite workspace cannot be connected.
02What do you need to connect SmartSuite to Make?
You need a paid SmartSuite account and two values. The first is your API token, generated from your SmartSuite profile page, in the API Key section, with the Generate New Key button. The second is your workspace ID, the part of your SmartSuite URL that names the workspace. In Make, click Create a connection on any SmartSuite module, enter both values and click Save. For an instant trigger, create the webhook first, then the connection.
03Do SmartSuite triggers in Make react in real time?
Yes. Both SmartSuite triggers, Watch New Records and Watch Updated Records, are instant: SmartSuite calls Make through a webhook as soon as a record is created or changed, instead of Make checking on a schedule. That is why they show the lightning badge in the editor. There is no scheduled SmartSuite trigger. If your scenario starts from another app instead, its schedule applies, every 15 minutes by default, or 1 minute at the lowest on a paid plan.
04What if a SmartSuite module is missing in Make?
Use Make an API Call. It sends any request to the SmartSuite API with the connection you already have, which covers what the 12 listed modules do not, since they all deal with records. You write the request yourself, so it helps to have the SmartSuite API documentation at hand. The official Make documentation for this app gives no numbered limit, so there is no documented cap to plan around beyond your Make plan.
05Should you use Make or n8n for SmartSuite?
It depends on how your team likes to build. Make gives SmartSuite 12 ready modules, two of them instant triggers, plus Make an API Call for the rest, all set up visually and testable with Run once. Many apps also have an n8n node, and it is worth checking what exists there for SmartSuite before choosing. Compare the modules available on each side for your exact use case rather than relying on general claims about either tool.
Same platform

Other docs you might need on this stack.

Browse all integrations