Resources · Make integration

Smartlook Make integrationAutomate Smartlook with Make.

What can Smartlook send to the rest of your stack? The Smartlook Make integration gives you 10 modules: 6 instant triggers and 4 actions. This guide is for product and growth teams who want Smartlook events to reach other tools, and it walks you from the connection to a first live scenario.

Try the Smartlook integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Smartlook Make integration do?

The Smartlook Make integration links your Smartlook project to Make, a tool where you build a scenario (an automation made of blocks called modules) without writing code. Smartlook can start a scenario the moment an alert, a heatmap or an issue shows up, and Make can also read a funnel, read an event or delete visitors in Smartlook.

Alerts that reach the right people. Watch Alerts starts a scenario as soon as Smartlook reports an alert, so the next module can post it to the chat or task tool your team already reads. Nobody has to keep the Smartlook tab open.

Privacy requests handled in one place. When someone asks to be forgotten, Delete Visitors removes their visitors from Smartlook by identifier. Put it at the end of the flow that already receives those requests, and the deletion stops depending on someone remembering it.

Product signals in a shared table. Watch Issues and Watch Notes pass each new item to Make as a bundle (one item moving from module to module). Get a Funnel or Get an Event can add details before the row lands in a base such as the one described on the Airtable Make integration page.

The listed modules do not cover the whole Smartlook API. For the rest, Make an API Call reuses your connection. The Smartlook doc page on Make also warns that its content is AI-generated and may contain mistakes, so check important details against Smartlook itself. If you are still choosing a platform, read n8n vs Make, and if you want a full course, see Make training.

Connect

How do you connect Smartlook to Make?

  1. 01

    Create an API token in Smartlook

    In Smartlook, open Project settings, click REST API, then New token. Give the token a label you will recognize, click Save and copy the token shown on screen. You need an active Smartlook account for this.

  2. 02

    Add a Smartlook module in your scenario

    In Make, add any Smartlook module and click Create a connection. A connection is your Smartlook account linked to Make once, then reused by every Smartlook module. The Connection name field is optional, but a clear name helps when you run several projects.

  3. 03

    Paste the token and save

    Paste the Bearer API token you copied, or follow the on-screen instructions, and confirm. Make now lists what it can read from your project, and the same connection works for the triggers, the actions and Make an API Call.

First scenario

Your first scenario: delete a visitor on request

GoalWhen a deletion request reaches another app, Make deletes the matching visitors in Smartlook.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to place the first module. That first module comes from the app where deletion requests arrive, such as your form or support tool.

  2. 02

    Add Delete Visitors

    Click the + on the right of the first module, search for Smartlook and pick Delete Visitors. Click Create a connection and paste your API token if you have not linked Smartlook yet.

  3. 03

    Map the visitor identifier

    In the Delete Visitors fields, map the visitor identifier (uid) coming from the first module. The request must carry that identifier, otherwise Smartlook has nothing to match.

  4. 04

    Test with a throwaway visitor

    Click Run once with a request that points to a test visitor, then open the bundles each module received. A deletion cannot be undone, so never test on a real person.

  5. 05

    Schedule and switch it on

    Set the Scheduling clock on the first module (every 15 minutes by default) and turn the scenario on. Each run counts operations, one per module and per bundle.

Triggers

Which Smartlook triggers start a scenario?

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

Smartlook1Watch Alerts

Watch Alerts

Instant trigger

In Make“Watch Alerts”

Watch Alerts turns a Smartlook alert into the start of a scenario, so the warning can travel to wherever your team actually looks. Each alert enters Make as one bundle that the next modules can read.

How it fires
instant, Smartlook calls Make through a webhook as soon as the alert happens.
When to use it
the alerts matter, but people miss them because they only live inside Smartlook.
Watch out
click Create a webhook before Create a connection, or the scenario never hears from Smartlook.
Smartlook2Watch Dashboards

Watch Dashboards

Instant trigger

In Make“Watch Dashboards”

With Watch Dashboards, dashboard activity in Smartlook becomes something Make can react to, for example by logging it in a table the whole product team shares. You get a trace outside Smartlook without copying anything by hand.

How it fires
instant, Smartlook notifies Make through a webhook the moment it happens.
When to use it
dashboards matter to several teams and you want their activity recorded in one shared place.
Watch out
the Make doc does not describe the bundle content, so run the scenario once and read what arrives before mapping fields.
Smartlook3Watch Heatmaps

Watch Heatmaps

Instant trigger

In Make“Watch Heatmaps”

Designers get their cue from Watch Heatmaps: a heatmap event in Smartlook starts the scenario, and Make can pass the news to a design channel or a review board. Nobody has to check the heatmap list to know something changed.

How it fires
instant, Smartlook sends the event to Make over a webhook right away.
When to use it
a page redesign is live and the design team wants heatmap updates in their own tools.
Watch out
every event received costs at least one operation on your Make plan, so keep an eye on volume once the scenario is on.
Smartlook4Watch Issues

Watch Issues

Instant trigger

In Make“Watch Issues”

Engineers see problems sooner once Watch Issues is in place, because each issue Smartlook reports lands in Make and can open a ticket in the tool the developers already work in. The issue arrives as a bundle, ready to map.

How it fires
instant, a webhook from Smartlook reaches Make as soon as the issue appears.
When to use it
bugs spotted in session data should enter the development backlog without a manual copy.
Watch out
map only the fields you checked in a Run once test, since the doc lists none.
Smartlook5Watch Notes

Watch Notes

Instant trigger

In Make“Watch Notes”

Notes written in Smartlook usually stay there. Watch Notes pulls each new one into a scenario, so a comment left on a recording can become a task, a message or a row in a research log.

How it fires
instant, Smartlook tells Make through a webhook as soon as the note exists.
When to use it
researchers annotate sessions and want those findings to reach the people who decide what to build.
Watch out
in the module list, Watch Notes and Watch Issues sit side by side, so check the name before you pick one.
Smartlook6Watch Shares

Watch Shares

Instant trigger

In Make“Watch Shares”

Sharing is a signal too. Watch Shares starts a scenario whenever Smartlook reports a share, which lets you keep a record of what was sent around or tell the owner of the project that something left the tool.

How it fires
instant, Smartlook pushes the share to Make through a webhook without waiting for a schedule.
When to use it
you want visibility on shared recordings or dashboards across a larger team.
Watch out
on the Free plan only 2 scenarios can be active, so plan which Smartlook triggers deserve a slot.
Modules

What can Make do in Smartlook?

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

Smartlook1

Delete Visitors

Action

In Make“Delete Visitors by uids”

Delete Visitors erases visitors from your Smartlook project using their identifiers (uids), which gives you a clean way to honor removal requests from inside a scenario.

When to use it
a privacy or account-closure request arrives in another app and must reach Smartlook too.
Watch out
a deletion cannot be rolled back, so test on a dummy visitor before switching the scenario on.
Smartlook2

Get a Funnel

Action

In Make“Returns details about a specified funnel.”

Get a Funnel brings back the details of one funnel you choose, so a report, a message or a table can show its data without anyone opening Smartlook.

When to use it
an alert just fired and you want the related funnel attached to the message your team receives.
Watch out
it returns one specified funnel per bundle, not a list, so tell it which funnel you need each time.
Smartlook3

Get an Event

Action

In Make“Returns details about a specified event.”

Pick Get an Event when a scenario needs the full details of one specific Smartlook event, for instance to enrich a ticket or a spreadsheet row that only carries a reference to it.

When to use it
a trigger gave you an event reference and the next app needs more than that.
Watch out
it returns one event per bundle, and every call counts as an operation on your Make plan.
Smartlook4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the other modules covers what you need, Make an API Call reaches any endpoint of the Smartlook API with the connection you already set up, no new token required.

When to use it
the action you want exists in the Smartlook API but has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Smartlook API documentation open while you build it.
Need help

Need help automating Smartlook with Make?

A person reads every message.

FAQ

Smartlook and Make: common questions

01Is the Smartlook Make integration free?
Yes, on the Make side. Smartlook is a standard app, available from the Free plan. That plan keeps 2 active scenarios, a minimum of 15 minutes between scheduled runs, 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 and allow unlimited active scenarios. You still need an active Smartlook account with API access, and its subscription is set by Smartlook, not by Make.
02What do you need to connect Smartlook to Make?
An active Smartlook account and a Bearer API token. You create the token in Smartlook under Project settings, then REST API, then New token: give it a label, save, and copy it. In Make, add a Smartlook module, click Create a connection, and paste the token. With an instant module, Make first asks you to create a webhook, then the connection. One connection serves every Smartlook module in your scenarios.
03Do Smartlook triggers in Make work in real time?
Yes. All 6 Smartlook triggers are instant: Smartlook calls Make through a webhook as soon as the alert, dashboard, heatmap, issue, note or share event happens, instead of Make checking on a schedule. The scenario has to be switched on to receive those calls. The 4 actions work differently: they run when the scenario reaches them, after whatever module starts the flow. To see what each event carries, click Run once and read the bundle the trigger received.
04What if the Smartlook module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Smartlook API with the connection you already created, so you are not limited to the 4 listed actions. Keep in mind that the Smartlook page of the Make documentation says its content is AI-generated and may contain mistakes, so verify key details in the Smartlook documentation before you rely on them in production. Each call through that module counts as an operation on your plan, like any other module.
05Should you use Make or n8n for Smartlook?
It depends on the tool your team already runs. In Make, Smartlook offers 10 modules, instant triggers and Make an API Call, which covers most flows described on this page. The same app often has an n8n node as well, so check whether it exists before switching platforms. Pick the one your team knows and will maintain; the comparison linked higher on this page lays out the criteria. On the Make side, the connection only needs the Smartlook API token described above.
Same platform

Other docs you might need on this stack.

Browse all integrations