Resources · Make integration

Attentive Make integrationAutomate Attentive with Make.

Want Attentive clicks, opt-ins and replies to move your other tools on their own? The Attentive Make integration gives you 26 modules, 11 of them instant triggers. This guide is for marketers new to Make: connect your account, then build a first working scenario.

Try the Attentive integration on MakeSee the 26 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Attentive Make integration do for you?

The Attentive Make integration links your Attentive account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single step such as a trigger, an action or a search. Attentive tells Make when a subscriber clicks, opens, replies or opts out, and Make can send data back.

Feed your journeys with data from other tools. When a ticket closes in your helpdesk, Add a Custom Event hands that moment to Attentive, where the Segment Builder and Journey Builder can use it for email and text messages.

Keep a clean record of consent. Watch SMS Unsubscribed and Watch Email Unsubscribed fire the moment someone opts out, so a CRM or a spreadsheet can be updated without anyone copying names by hand.

Handle privacy requests without a ticket queue. Add a Deletion Request starts a privacy deletion, and Retrieve CCPA Delete Request by ID lets you check where it stands later.

What the integration does not include: there is no Make an API Call module for Attentive, so anything outside these 26 modules needs another route. Also note that the official Make documentation for this app is flagged as AI-generated and may contain mistakes, so test each module on a real subscriber before you rely on it. If you are also weighing n8n, our n8n vs Make comparison sets the two tools side by side, and the Make pricing breakdown explains what the plans include. Stuck on a failing run? Read Make troubleshooting.

Connect

How do you connect Attentive to Make?

  1. 01

    Add an Attentive module

    Open a scenario, click the +, search for Attentive and pick any module. Then click Create a connection. A connection is your Attentive account linked to Make once; every Attentive module in every scenario reuses it.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, for example the brand it belongs to. Then either authorize Make on the Attentive page that opens, or paste the credentials Attentive gives you for this purpose.

  3. 03

    Save and check the module

    Click Save. The connection now appears in the module's dropdown, and Make can start reading your Attentive data. If the save fails, check that your Attentive account is active before trying again.

First scenario

Your first scenario: send helpdesk events to Attentive

GoalWhen a support ticket closes in your helpdesk, Make adds a custom event to the matching Attentive subscriber.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick your helpdesk app and its module that watches for closed tickets. That module starts the flow.

  2. 02

    Add Add a Custom Event

    Click the + on the right of the first module, search for Attentive and choose Add a Custom Event. Click Create a connection if this is your first Attentive module.

  3. 03

    Map the ticket data

    Fill the Attentive fields with data from the helpdesk module: click into a field and pick the customer details the first module received. Make lists what it can read once both connections exist.

  4. 04

    Test with Run once

    Close a test ticket, then click Run once. Open each module's bubble to read the bundles it received, a bundle being one item passed along, here one ticket. Check that Attentive accepted the event.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set Scheduling. A new scenario checks every 15 minutes by default. Pick what suits you within your plan, then switch the scenario on.

Triggers

Attentive triggers: what starts a scenario

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

Attentive1Watch Custom Attribute Set

Watch Custom Attribute Set

Instant trigger

In Make“Triggers when a custom attribute is set.”

This trigger gives you a scenario that reacts whenever a custom attribute lands on a subscriber in Attentive. You get the subscriber and the attribute as a bundle, one item your next module can pass on.

How it fires
instant: Attentive calls Make through a webhook as soon as the attribute is set, so nothing waits for a schedule.
When to use it
copy a preference such as a favorite product line into your CRM the moment it changes.
Watch out
if a scenario of yours writes attributes with Add a Custom Attributes, those writes may well fire this trigger too (a deduction, not a documented rule), so keep the two in separate flows.
Attentive2Watch Email Message Link Click

Watch Email Message Link Click

Instant trigger

In Make“Triggers when a link is clicked in an email message.”

You hear about every click on a link inside an Attentive email, one bundle per click, which turns interest into something your other tools can act on straight away.

How it fires
instant: Attentive pings Make by webhook the moment the subscriber clicks.
When to use it
a click on a pricing or demo link in a campaign should alert a sales rep or tag the lead in your CRM.
Watch out
every click is its own bundle and each module that processes it counts as an operation on your Make plan, so add a filter right after the trigger if you only care about certain links.
Attentive3Watch Email Opened

Watch Email Opened

Instant trigger

In Make“Triggers when an email is opened.”

With this trigger your scenario learns that a subscriber opened an Attentive email, which is the earliest sign of attention you can catch from the email channel.

How it fires
instant: Attentive notifies Make over a webhook as soon as the open is recorded.
When to use it
log opens next to each contact in a reporting sheet, or tell your team which accounts read the latest announcement.
Watch out
opens pile up much faster than clicks, and an operation is one module run on one bundle, so keep the scenario short or filter early to save credits.
Attentive4Watch Email Sent

Watch Email Sent

Instant trigger

In Make“Triggers when an email message is sent.”

Every email message Attentive sends can reach Make as a bundle, giving you an outside record of what went to whom without exporting reports.

How it fires
instant: Attentive calls Make by webhook right after the message leaves.
When to use it
write a line to your CRM timeline each time a subscriber gets an email, so account managers see the full history in one place.
Watch out
this fires on sends, not on reads; pair it with Watch Email Opened if you need to know whether anyone looked at the message.
Attentive5Watch Email Subscribed

Watch Email Subscribed

Instant trigger

In Make“Triggers when a user opts in to an email subscription.”

The moment a person opts in to an email subscription, this trigger hands their details to your scenario, so a new subscriber can be welcomed across every tool, not only in Attentive.

How it fires
instant: Attentive pushes the opt-in to Make through a webhook as soon as it happens.
When to use it
create or update the contact in your CRM and mark the email consent there as well.
Watch out
a person who signs up for email may already exist elsewhere, so search for the contact first in the next app before creating a duplicate.
Attentive6Watch Email Unsubscribed

Watch Email Unsubscribed

Instant trigger

In Make“Triggers when a user opts out of an email subscription.”

Here your scenario is told that someone opted out of an email subscription, which lets you respect that choice in every other system that holds their address.

How it fires
instant: Attentive alerts Make by webhook the moment the opt-out is recorded.
When to use it
switch off the email flag in your CRM or remove the person from a newsletter list kept in another tool.
Watch out
an email opt-out does not tell you about SMS; if you need the full picture, follow with Get Subscription Eligibility For A User to see which subscriptions remain.
Attentive7Watch SMS Inbound Message

Watch SMS Inbound Message

Instant trigger

In Make“Triggers when a user replies to an SMS message.”

When a subscriber replies to one of your texts, this trigger passes the reply to Make, so a conversation that starts in SMS can reach a human instead of sitting unread.

How it fires
instant: Attentive calls Make through a webhook as soon as the reply arrives.
When to use it
post replies into a team chat channel or open a ticket in your helpdesk so support can answer.
Watch out
replies can be anything from a question to a single word, so add a filter or a router after the trigger before you open tickets for every message.
Attentive8Watch SMS Link Click

Watch SMS Link Click

Instant trigger

In Make“Triggers when a link is clicked in an SMS message.”

This is the text message twin of the email click trigger: each tap on a link inside an Attentive SMS becomes a bundle your scenario can use.

How it fires
instant: Attentive sends the click to Make over a webhook right away.
When to use it
a tap on a restock or event link in a text should flag the subscriber as a hot lead in your CRM or ping the store team.
Watch out
SMS clicks and email clicks come from separate triggers, and a scenario starts from one trigger, so covering both channels takes two scenarios.
Attentive9Watch SMS Sent

Watch SMS Sent

Instant trigger

In Make“Triggers when an SMS is sent.”

Each text Attentive sends can be recorded outside Attentive with this trigger, which is handy when several teams need to know who was contacted by SMS.

How it fires
instant: Attentive calls Make by webhook as soon as the SMS goes out.
When to use it
add the send to a customer's timeline in your CRM, so nobody on the team texts the same person twice about the same thing.
Watch out
a sent SMS says nothing about a reply; route answers through Watch SMS Inbound Message instead.
Attentive10Watch SMS Subscribed

Watch SMS Subscribed

Instant trigger

In Make“Triggers when a user opts in to an SMS subscription.”

A new opt-in to an SMS subscription reaches your scenario through this trigger, so you can act on text consent everywhere you store customer data.

How it fires
instant: Attentive notifies Make by webhook the moment the person subscribes.
When to use it
mark SMS consent on the CRM record, or send the new subscriber's details to a loyalty tool that rewards sign-ups.
Watch out
email and SMS sign-ups arrive through different triggers; if your CRM keeps one consent field per channel, build one scenario per trigger so each writes its own field.
Attentive11Watch SMS Unsubscribed

Watch SMS Unsubscribed

Instant trigger

In Make“Triggers when a user opts out of an SMS subscription.”

When someone opts out of an SMS subscription, this trigger tells Make at once, which keeps other tools from texting a person who said stop.

How it fires
instant: Attentive calls Make through a webhook as soon as the opt-out happens.
When to use it
clear the SMS consent flag in your CRM or remove the number from a list another app uses for texts.
Watch out
leaving SMS may not mean leaving email; if another tool needs to know what is left, check with Get Subscription Eligibility For A User.
Modules

Attentive actions and searches

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

Attentive1

Add a Client User Identifier or Custom Identifier(s) to a User

Action

In Make“Add a client user identifier or custom identifier(s) to a user.”

Tie an Attentive subscriber to the IDs your other systems use, so later events from your shop or CRM land on the right person.

When to use it
after a customer creates an account in your store, attach that account ID to their Attentive profile.
Watch out
run it before sending events keyed on that identifier; otherwise they may not land on the right person.
Attentive2

Add a Custom Attributes

Action

In Make“Add any attribute-based data to a user.”

Write any attribute you care about onto a subscriber, such as a size, a store location or a plan name, so segments in Attentive can use it.

When to use it
a customer updates their preferences in another tool and Attentive should reflect the change.
Watch out
the write is likely to fire Watch Custom Attribute Set as well, so do not start this same scenario from that trigger or it may loop.
Attentive3

Add a Custom Event

Action

In Make“Send user actions to use in the Attentive Segment Builder and Journey Builder for both email and text messages.”

Send Attentive any action a user took outside it, then build segments and journeys on that action in the Segment Builder and Journey Builder, for both email and text.

When to use it
a webinar signup, a closed ticket or a booked call should start a follow-up journey.
Watch out
pick clear, stable event names; journeys depend on them, and renaming later means updating every journey that listens.
Attentive4

Add a Deletion Request

Action

In Make“Creates a new privacy deletion request. This will be done within thirty days, provided the call was successful.”

File a privacy deletion request for a person in Attentive straight from a scenario, instead of handling each one by hand in the dashboard.

When to use it
a deletion form on your site or a support ticket asks for a customer's data to be erased.
Watch out
Attentive completes the deletion within thirty days if the call succeeds, not on the spot; note the request's ID to track it later with the retrieve module.
Attentive5

Add Offer Codes

Action

In Make“Add discount codes to an existing offer.”

Top up an existing Attentive offer with new discount codes, so the campaign never runs dry mid-send.

When to use it
your ecommerce platform or a spreadsheet generates a fresh batch of unique codes and they need to reach Attentive.
Watch out
this adds codes to an offer that already exists; create the offer in Attentive first, then point the module at it.
Attentive6

Add to Cart

Action

In Make“A user adds a product to their shopping cart.”

Tell Attentive that a user put a product in their cart, which gives your cart recovery messages a signal even when the cart lives in a tool Attentive does not track.

When to use it
a custom checkout or a marketplace store where cart activity reaches Make but not Attentive.
Watch out
test it with Run once on one real cart and check the bundle Attentive received before switching the scenario on.
Attentive7

Purchase

Action

In Make“Generates an order or purchase for a user.”

Record an order for a user in Attentive, so purchase based journeys and segments see sales made outside your main store.

When to use it
an order is paid in a point of sale, a B2B portal or an invoicing app and the buyer is also an Attentive subscriber.
Watch out
if your store already reports orders to Attentive, sending the same order here will likely count it twice.
Attentive8

Subscribe a User

Action

In Make“Opts a user into a subscription.”

Opt a person into an Attentive subscription from any form or tool Make can read, so sign-ups gathered elsewhere join your lists.

When to use it
a lead ticks a consent box on an event registration or a quiz and should start getting messages.
Watch out
only send people who actually agreed; the module subscribes whoever you map into it, so map only the contacts whose consent you actually collected.
Attentive9

Unsubscribe a User

Action

In Make“Unsubscribes a user from a subscription type or channel.”

Remove someone from a subscription type or a whole channel in Attentive, triggered by an opt-out recorded somewhere else.

When to use it
a customer asks your support team or your CRM to stop texts, and Attentive must stop too.
Watch out
choose the scope with care, since a single subscription type and an entire channel are not the same removal.
Attentive10

View a Product

Action

In Make“A user views a product.”

Log that a user viewed a product, which lets browse based messages in Attentive react to visits happening on sites or apps it cannot see.

When to use it
a mobile app or a separate storefront sends product views to Make, and you want browse follow-ups in Attentive.
Watch out
views can be numerous; each one sent costs operations, so filter to the products that matter.
Attentive11

Get Subscription Eligibility For A User

Search

In Make“List all subscription types and channels a user is subscribed to.”

Find out every subscription type and channel a user is currently on, so your scenario can decide what to do based on real consent.

When to use it
right after an unsubscribe trigger, to learn whether the person is still reachable on the other channel.
Watch out
as a search, it can return several items; add a filter or an aggregator if the next module expects just one.
Attentive12

Lookup Product Catalog Ingestion

Search

In Make“Views a specific product catalog upload and its statuses.”

Check one specific product catalog upload and read its statuses, which tells you whether Attentive accepted your latest product data.

When to use it
after a catalog update, before a campaign that depends on new products goes out.
Watch out
you need the ID of that upload; get it from View Recent Catalog Uploads if you do not already have it.
Attentive13

Retrieve CCPA Delete Request by ID

Search

In Make“Retrieves details on a deletion request.”

Pull the details of a deletion request you already filed, so you can answer a customer or close a privacy ticket with facts.

When to use it
a follow-up scenario that checks pending requests and updates the ticket once the deletion is done.
Watch out
it needs the request ID from Add a Deletion Request, so store that ID somewhere the moment the request is created.
Attentive14

Search Custom Attributes

Search

In Make“Retrieves all custom attribute data associated with a user.”

Read back all the custom attribute data Attentive holds for a user, useful when another tool needs the same profile details.

When to use it
before a sales call or a support reply, pull the subscriber's attributes into the ticket or CRM record.
Watch out
results come as several items; map only the attributes you need instead of copying everything across.
Attentive15

View Recent Catalog Uploads

Search

In Make“Lists recent catalog uploads with their statuses.”

List the latest catalog uploads with their statuses, a quick health check on the product feed Attentive relies on.

When to use it
send a message to the ecommerce team when an upload shows a failed status, before shoppers see outdated products.
Watch out
this gives an overview; to dig into one upload, pass its ID to Lookup Product Catalog Ingestion.
Need help

Need help automating Attentive with Make?

A person reads every message.

FAQ

Attentive and Make: common questions

01Is the Attentive Make integration free?
Yes, on the Make side. Attentive is a standard app, so it is available from the Free plan onward, alongside 3,000+ other standard apps. The Free plan comes with limits: 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lift these to a 1 minute interval, unlimited active scenarios and 40 minutes of execution, with usage counted in credits. You still need an active Attentive account of your own, since Make only connects to it.
02What do you need to connect Attentive to Make?
An active Attentive account and the authentication credentials that come with it. In Make, add any Attentive module, click Create a connection, optionally name it, then either authorize Make on the Attentive page or paste the credentials Attentive provides, and click Save. The connection is created once and shared by every Attentive module in all your scenarios. If saving fails, confirm first that your Attentive account is active and that you hold its credentials.
03Do Attentive triggers in Make fire instantly?
Yes. All 11 Attentive triggers are instant: Attentive calls Make through a webhook as soon as the event happens, whether that is an email open, a link click, an SMS reply or an opt-out. You will see a lightning badge on these modules in the editor. That differs from scheduled triggers, which Make checks on the scenario's schedule, every 15 minutes by default. The actions and searches that follow the trigger simply run in the same pass.
04What if an Attentive module is missing in Make?
It depends on what you need. The Attentive app in Make has no Make an API Call module, so you cannot go beyond its 26 modules from inside the app. Often another module comes close: Add a Custom Event covers many actions that have no dedicated module, since journeys can listen to it. If that is still not enough, the workaround has to come from a different app in the scenario, and our team can help you pick one.
05Make or n8n for Attentive?
It depends on how you work more than on the app. In Make, Attentive comes with 26 ready modules, including 11 instant triggers and searches for subscriptions, attributes, catalog uploads and deletion requests, all usable from the Free plan. Whether n8n offers an Attentive node, and which operations it covers, is worth checking on the n8n side before you decide. Pick the tool whose editor your team already knows and whose modules match your scenario.
Same platform

Other docs you might need on this stack.

Browse all integrations