Resources · Make integration

Prefinery Make integrationAutomate Prefinery with Make.

Need other tools to hear about every change in your Prefinery user list? The Prefinery Make integration offers 8 scheduled triggers and no actions. This page shows how to link your account, build a first scenario and pick the right trigger.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Prefinery Make integration do?

The Prefinery Make integration lets Make watch your Prefinery account and start an automation when something happens to a user or a referral. In Make, that automation is called a scenario: a chain of modules, where each module is one brick, such as a trigger that starts things or an action in another app.

All 8 Prefinery modules are triggers. Make's documentation lists them without detail, so their type is deduced from their Watch names: scheduled, which you can confirm by the clock badge on the module in the editor. Make polls Prefinery on the scenario's schedule instead of being called the moment something changes. Prefinery is the starting point of the flow; what happens next is done by modules from other apps.

A typical first build: Watch Created User picks up each new user, and a module from your CRM or your email tool receives that person. A second idea for a growth team: Watch Created Referral feeds a shared sheet so the team can see which referrals come in. A third, for support: Watch Suspended User or Watch Deleted User sends an alert to the channel your team reads, so nobody keeps contacting someone who left.

What the integration does not do: it cannot create, edit or remove anything in Prefinery, and it has no Make an API Call module. The official Make documentation for Prefinery is also thin; it says so itself, so what each trigger returns is best checked with a test run. If you are weighing platforms, the n8n vs Make comparison lays out the criteria, and the Make pricing page explains what a plan includes. To learn the editor step by step, see the Make training.

Connect

How do you connect Prefinery to Make?

  1. 01

    Add a Prefinery module

    In your scenario, click the + and search for Prefinery, then pick any of its triggers. Under the connection field, click Create a connection. A connection is your Prefinery account linked to Make once, then reused by every Prefinery module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, handy when you manage more than one Prefinery account. Then either approve Make on the Prefinery page that opens, or paste the key Prefinery gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. The connection now appears in the module, and any other Prefinery trigger you add later can select it from the list without asking you to log in again.

First scenario

Build your first scenario with Prefinery

GoalWhen a new user appears in Prefinery, Make passes that person to the next tool of your choice.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor. That empty circle is where your first module, the trigger, goes.

  2. 02

    Add Watch Created User

    Search for Prefinery, choose Watch Created User and pick the connection you created, or click Create a connection if this is your first Prefinery module.

  3. 03

    Add the next module

    Click the + on the right of the Prefinery module and choose the app that should receive the user. Map its fields with the data that the trigger passes along.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, a bundle being one item, here one user. Check them before going live.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; keep it or change it within your plan, then switch the scenario on.

Triggers

Which Prefinery triggers can start a scenario?

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

Prefinery1Watch Applied User

Watch Applied User

triggerIn the docs only

Use this trigger to react when a user shows up as applied in Prefinery, going by the module name, since Make's documentation gives no description. Each person it finds becomes one bundle for the rest of the scenario.

How it fires
scheduled, so Make checks the app on the scenario's schedule rather than hearing from Prefinery right away.
When to use it
you want applicants copied into a review sheet or announced to the team that screens them.
Watch out
run it once and look at the bundle to confirm what "applied" covers in your account.
Prefinery2Watch Created Referral

Watch Created Referral

triggerIn the docs only

This is the only trigger about referrals rather than users: it gives your scenario each referral that appears in Prefinery, going by its name. It suits anyone who tracks where sign-ups come from.

How it fires
scheduled, which means Make checks the app on the scenario's schedule, not the moment the referral happens.
When to use it
you log referrals in a spreadsheet or thank the person who shared the link.
Watch out
the documentation lists no fields, so read the bundle from Run once before mapping anything.
Prefinery3Watch Created User

Watch Created User

triggerIn the docs only

Pick this one when every new person in Prefinery should reach another tool: the module name says it follows created users, and each one arrives as a bundle ready to map.

How it fires
scheduled; Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
adding new sign-ups to your CRM or to an email list.
Watch out
on the Free plan the shortest gap between two scheduled runs is 15 minutes, so users arrive in small batches rather than one at a time.
Prefinery4Watch Deleted User

Watch Deleted User

triggerIn the docs only

Keep your other tools clean with this trigger: going by its name, it hands your scenario the users removed from Prefinery, so you can remove or flag them elsewhere too.

How it fires
scheduled; Make checks the app on the scenario's schedule and picks up deletions since the last check.
When to use it
a person leaves your list and should stop getting emails or disappear from a shared sheet.
Watch out
test with Run once to see which details are still available about a user who no longer exists in Prefinery.
Prefinery5Watch Imported User

Watch Imported User

triggerIn the docs only

When people enter Prefinery through an import instead of signing up themselves, this trigger lets you treat them apart, judging by its name. That keeps bulk arrivals out of flows meant for organic sign-ups.

How it fires
scheduled, with Make checking the app on the scenario's schedule.
When to use it
imported contacts need a different welcome or a separate tag in your CRM.
Watch out
a large import turns into many bundles, and each module that processes one counts as an operation, the unit Make counts on your plan.
Prefinery6Watch Resubscribed User

Watch Resubscribed User

triggerIn the docs only

Spot the users who come back: as its name suggests, this trigger catches people who resubscribe in Prefinery, so a comeback does not go unnoticed by your other tools.

How it fires
scheduled; Make checks the app on the scenario's schedule instead of waiting for a signal from Prefinery.
When to use it
putting a returning user back on your mailing list or telling the team who came back.
Watch out
if you also use Watch Created User, check with a test that the same person does not end up processed twice.
Prefinery7Watch Suspended User

Watch Suspended User

triggerIn the docs only

Get a heads-up on accounts put on hold: this trigger, by its name, reports users suspended in Prefinery, which lets support or sales stop outreach to them at once.

How it fires
scheduled, as Make checks the app on the scenario's schedule and returns what changed since its last pass.
When to use it
a suspended user should be flagged in your CRM or posted to your support channel.
Watch out
Make's documentation does not say what a suspension covers, so match it against your own Prefinery settings.
Prefinery8Watch Updated User

Watch Updated User

triggerIn the docs only

Keep a copy of your users in sync: judging by its name, this trigger returns users whose details changed in Prefinery, the broadest of the 8 triggers.

How it fires
scheduled; Make checks the app on the scenario's schedule and collects the updates since the last check.
When to use it
a CRM record or a spreadsheet row should follow each edit made in Prefinery.
Watch out
this trigger may also catch changes that other Watch triggers cover, so check with Run once what it catches before you act on it, or you pay operations twice.
Need help

Need help automating Prefinery with Make?

A person reads every message.

FAQ

Prefinery and Make: common questions

01Is the Prefinery Make integration free?
Yes, Prefinery is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a scheduled run at most every 15 minutes, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the limit on active scenarios and allow 40 minutes per run. Usage is counted in credits, one per operation. Your Prefinery subscription is a separate matter.
02What do you need to connect Prefinery to Make?
A Prefinery account and a Make account. Make's documentation lists no specific prerequisite for Prefinery and no app-specific steps, so the generic flow applies: add a Prefinery module, click Create a connection, name it if you want, authorize Make on the Prefinery page or paste the key Prefinery gives you, then click Save. The connection is then reused by every Prefinery module in your scenarios, so you only do this once per account.
03Do Prefinery triggers work in real time in Make?
No. Going by their Watch names, and with no other detail in Make's documentation, all 8 Prefinery triggers are scheduled (look for the clock badge on the module): Make checks Prefinery on the scenario's schedule instead of being called by the app. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans can go down to 1 minute. Each check can bring back several bundles at once, and your next modules handle them one by one, which keeps the flow predictable even when many users change together.
04What if a Prefinery module is missing in Make?
It depends on what you need. The integration only has triggers, so Make cannot write anything back into Prefinery, and there is no Make an API Call module for this app to fill the gap. Make's documentation for Prefinery is also limited. For a custom need, look at another app that covers the step, or ask a Make agency team to review the scenario with you before you build around a missing piece.
05Should you use Make or n8n for Prefinery?
It depends on your criteria rather than on the app. The same app often has an n8n node too, so check what each tool offers for it before you decide. In Make, you get 8 scheduled triggers, no actions and no API call module, which suits flows that start in Prefinery and continue in other apps. Compare the modules available on both sides for your exact case, then choose the editor your team is most comfortable reading and maintaining.