Resources · Make integration

MyPreferences 3.0 Make integrationAutomate MyPreferences 3.0 with Make.

Can Make keep MyPreferences 3.0 in step with the rest of your tools? The MyPreferences 3.0 Make integration offers 17 modules: 8 scheduled triggers and 9 actions. This guide shows how to link your account and build a first scenario without writing code.

Try the MyPreferences 3.0 integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the MyPreferences 3.0 Make integration do?

The MyPreferences 3.0 Make integration lets Make read and write your MyPreferences 3.0 data without code. You build a scenario, the automation that chains modules together, and each module is one brick: a trigger that starts the flow or an action that does one job on your account.

Profiles created from outside. A sign-up collected by another app can land in MyPreferences 3.0 through Create a Profile, and Update a profile keeps an existing record current when details change elsewhere.

Changes picked up on their own. The 8 Watch modules, from Watch consents to Watch tags, let a scenario start whenever Make finds items of that kind on its check, so the next app in the chain hears about them.

Segments sent where they are needed. Initiate a Segment Export starts an export, Retrieve segment export status tells you where it stands, and the two Retrieve segment export data modules collect the result.

A word of caution: the official documentation for this app is limited, with no field list and no description per module. Test every module with Run once before you rely on it. The Make review explains the editor itself, Make troubleshooting helps when a run fails, and if you are weighing tools, n8n vs Make sets the two side by side.

Connect

How do you connect MyPreferences 3.0 to Make?

  1. 01

    Add a module and open the connection

    Drop any MyPreferences 3.0 module into your scenario and click Create a connection. A connection is your account linked to Make once; every other module of the app reuses it.

  2. 02

    Give it a clear name

    Naming the connection is optional, but a label such as the workspace or client it belongs to saves confusion later, especially if a teammate opens the scenario after you.

  3. 03

    Authorize and save

    Depending on what MyPreferences 3.0 asks for, either approve Make on the app's own page or paste the key the app gives you. Then click Save and the module is ready to fill.

First scenario

Your first scenario with MyPreferences 3.0

GoalWhen a new sign-up reaches another app, Make creates the matching profile in MyPreferences 3.0.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. This first brick belongs to the app where your sign-ups arrive, such as a form tool.

  2. 02

    Set up the source app

    Pick that app's module, link its account, and fill in what it asks. Once the connection exists, Make lists the forms or objects it can read, so there is no need to type them by hand.

  3. 03

    Add Create a Profile

    Click the + on the right of the first module, search MyPreferences 3.0 and choose Create a Profile. Create the connection, then map each value from the sign-up into the fields Make shows.

  4. 04

    Test with Run once

    Click Run once and submit one test sign-up. Each module shows the bundles it received, a bundle being one item passing through, so you can check that a profile appears in MyPreferences 3.0.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan allows no shorter gap. Then flip the switch to turn the scenario on.

Triggers

What can start a MyPreferences 3.0 scenario?

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

MyPreferences 3.01Watch consents

Watch consents

triggerIn the docs only

You get one scenario run per consent item Make finds, which is handy when a consent change has to reach your CRM or your email tool. The documentation gives no description, so what counts as a consent comes only from the module name.

How it fires
scheduled, Make checks the app on the scenario's schedule, shown by the clock badge.
When to use it
when marketing needs to know that someone has given or withdrawn permission before the next send.
Watch out
run it once and read the bundles to see exactly what data the module returns before you map anything.
MyPreferences 3.02Watch contacts

Watch contacts

triggerIn the docs only

Contacts stored in MyPreferences 3.0 can feed the rest of your stack through this trigger, each one arriving as its own bundle. Pick it when the contact itself matters more than any preference attached to it.

How it fires
scheduled, Make checks the app on the scenario's schedule rather than being told by MyPreferences 3.0.
When to use it
copying contacts into a spreadsheet or a support tool so another team works from the same list.
Watch out
every bundle the trigger returns uses an operation, the unit Make counts on your plan, so a large batch costs more than one run.
MyPreferences 3.03Watch custom fields

Watch custom fields

triggerIn the docs only

This trigger keeps an eye on custom fields, the extra data points your account defines, and hands each one to the next module. It suits admins more than marketers, since it concerns how data is structured rather than who is in it.

How it fires
scheduled, Make polls the app on the rhythm set on the first module.
When to use it
alerting whoever maintains your data model when a field shows up that other tools need to learn about.
Watch out
the doc says nothing about what each bundle contains, so test before building logic around it.
MyPreferences 3.04Watch groups

Watch groups

triggerIn the docs only

Groups found in MyPreferences 3.0 turn into scenario runs here, one bundle per group, so a list you organize in the app can be mirrored somewhere else. Choose it over Watch contacts when you care about the grouping, not the people.

How it fires
scheduled, Make asks the app for groups each time the scenario's schedule comes around.
When to use it
keeping audience lists in an email platform aligned with the groups your team manages in MyPreferences 3.0.
Watch out
on the Free plan only 2 scenarios can be active, so group several syncs wisely.
MyPreferences 3.05Watch preferences

Watch preferences

triggerIn the docs only

Preferences are the heart of this app, and this trigger brings them into Make so another tool can respect what a person chose. It sits closest to consent handling, yet reads preferences rather than permissions, judging by its name.

How it fires
scheduled, Make looks at the app on the scenario's own timetable, never instantly.
When to use it
passing a subscriber's topic choices to the tool that sends your newsletters.
Watch out
with the default schedule of 15 minutes, a change can wait until the next check before anything happens downstream.
MyPreferences 3.06Watch profiles

Watch profiles

triggerIn the docs only

Profiles flow out of MyPreferences 3.0 with this trigger, one bundle per profile, ready for the next module. Judging by its name, it covers the person as a whole, so try it when Watch contacts leaves out what you need, and check the bundle with Run once.

How it fires
scheduled, Make checks the app at the interval set in Scheduling.
When to use it
feeding a reporting sheet that should reflect every profile in the app.
Watch out
pairing it with Update a profile on the same records can make the scenario pick up its own edits again, so send the data elsewhere.
MyPreferences 3.07Watch standard profile fields

Watch standard profile fields

triggerIn the docs only

Where Watch custom fields covers the fields you add yourself, this one follows the standard profile fields the app provides. It helps you document or copy the base structure of your profiles into another system.

How it fires
scheduled, Make queries MyPreferences 3.0 whenever the scenario's clock allows.
When to use it
preparing a field mapping for a migration or a new integration, so nobody has to list the fields by hand.
Watch out
the documentation is thin for this app, so confirm the output with Run once before trusting it in a live flow.
MyPreferences 3.08Watch tags

Watch tags

triggerIn the docs only

Tags in MyPreferences 3.0 become triggers for other work: each one Make detects arrives as a bundle the next module can act on. It fits teams that label records to drive follow-up steps.

How it fires
scheduled, Make fetches tags from the app according to the scenario's schedule.
When to use it
creating a matching label in a CRM or help desk so both tools speak the same vocabulary.
Watch out
scheduled runs on the Free plan cannot be closer than 15 minutes, and paid plans go down to 1 minute.
Modules

What can Make do in MyPreferences 3.0?

MyPreferences 3.0 gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

MyPreferences 3.01

Create a Profile

ActionIn the docs only

You end up with a fresh profile in MyPreferences 3.0 without retyping anything, filled from whatever the previous module passed along.

When to use it
right after a form, a checkout or a CRM entry produces a new person who should exist in your preference center.
Watch out
the doc lists no fields, so check after Run once which values are required.
MyPreferences 3.02

Initiate a Segment Export

ActionIn the docs only

This action kicks off an export of a segment, the first step before you can read its contents anywhere else. On its own it starts the job; it does not hand you the data.

When to use it
when a campaign or report needs a segment's members outside MyPreferences 3.0.
Watch out
follow it with Retrieve segment export status before trying to collect the result.
MyPreferences 3.03

Make an API call

ActionIn the docs only

Anything the listed modules do not cover can still be reached here: this module calls any endpoint of the MyPreferences 3.0 API with the connection you already set up.

When to use it
when a task needs an endpoint that no ready-made module handles.
Watch out
you write the request yourself, so keep the app's API documentation open.
MyPreferences 3.04

Make an integration API call

ActionIn the docs only

A second, separate API module exists alongside Make an API call, and its name points to integration endpoints of the app. The documentation does not explain the difference between the two.

When to use it
when the endpoint you need is part of the integration side of MyPreferences 3.0 rather than its general API.
Watch out
test both with Run once to see which one accepts your request.
MyPreferences 3.05

Retrieve a Profile

ActionIn the docs only

Pull up one existing profile and the rest of the scenario can use its details, for example to personalize a message or check a status before acting.

When to use it
in the middle of a flow, once you know which person you are dealing with and need their current record.
Watch out
it works on one profile at a time, so plan one operation per person.
MyPreferences 3.06

Retrieve segment export data

ActionIn the docs only

Once an export is finished, this module brings its contents back into the scenario so you can send them to a sheet, a CRM or an email tool. The name suggests results come back page by page.

When to use it
after Retrieve segment export status confirms the export is ready.
Watch out
each bundle it returns uses an operation, which adds up on large segments.
MyPreferences 3.07

Retrieve segment export data - Not paginated

ActionIn the docs only

Same goal as the previous module, collecting a finished export, but in one go rather than in pages, if the name is taken at face value. That can simplify the next steps when the segment stays small.

When to use it
when you prefer the whole export in a single response.
Watch out
on the Free plan a run stops after 5 minutes and data transfer is capped at 512 MB, so a heavy export can hit the ceiling.
MyPreferences 3.08

Retrieve segment export status

ActionIn the docs only

You learn whether a segment export you started is ready, which saves you from fetching data that does not exist yet.

When to use it
between Initiate a Segment Export and either Retrieve segment export data module, as the checkpoint that decides whether to continue.
Watch out
the documentation gives no list of status values, so read a real bundle with Run once before adding a filter on it.
MyPreferences 3.09

Update a profile

ActionIn the docs only

Changes made in another tool reach the existing MyPreferences 3.0 profile, so both systems describe the person the same way.

When to use it
when an address, a name or a choice changes in your CRM or shop and the preference center should follow.
Watch out
avoid starting this scenario with Watch profiles, otherwise each update can come back as a new run.
Need help

Need help automating MyPreferences 3.0 with Make?

A person reads every message.

FAQ

Questions about the MyPreferences 3.0 Make integration

01Is the MyPreferences 3.0 Make integration free?
Yes, MyPreferences 3.0 is a standard app, so it works on the Free plan of Make. That 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 such as Core, Pro and Teams lift the active scenario cap and bring the interval down to 1 minute. Usage is counted in operations, one per module per bundle. The pricing of MyPreferences 3.0 itself is a separate matter to check with the app.
02What do you need to connect MyPreferences 3.0 to Make?
You need a MyPreferences 3.0 account and a Make account, nothing more according to the documentation, which lists no prerequisite. Add any module of the app, click Create a connection, name it if you like, then either authorize Make on the app's page or paste the key MyPreferences 3.0 provides, and save. The doc gives no app-specific steps, so these are the standard Make steps. The same connection then serves all 17 modules, so you only do this once per account.
03Do MyPreferences 3.0 triggers in Make fire instantly?
No. All 8 triggers of this app are scheduled triggers, not instant ones. Make checks MyPreferences 3.0 at the interval set on the first module, which is every 15 minutes by default for a new scenario. On the Free plan that is also the shortest gap allowed; paid plans can go down to 1 minute. Note that the types come from the module names, since the directory entry was unavailable, so check the clock badge on each Watch module in the editor.
04What if a MyPreferences 3.0 module is missing in Make?
It depends on what you need, but you have two ways out. The app includes Make an API call, which reaches any endpoint of the MyPreferences 3.0 API with your existing connection, and a second module, Make an integration API call. Keep in mind that the official documentation for this app is limited: there are no module descriptions or field lists. If neither API module fits, you can look at whether another app in your stack holds the same data.
05Should you use Make or n8n for MyPreferences 3.0?
It depends on the tool your team already uses. On Make, MyPreferences 3.0 offers 17 modules, with 8 scheduled triggers and 9 actions covering profiles and segment exports, plus two API modules for anything else. The same app often has an n8n node as well. The honest criterion is where the rest of your automations live and which editor your team is comfortable in, since keeping everything in one place is simpler to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations