Resources · Make integration

OnSefy Make integrationAutomate OnSefy with Make.

Can Make check a new user with OnSefy before anyone lets them in? The OnSefy Make integration gives you 2 action modules and no trigger. This guide is for ops teams who run sign-ups: link your API key, then build a first scenario and test it.

Try the OnSefy integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the OnSefy Make integration do?

The OnSefy Make integration lets a Make scenario (the automation you build, a chain of modules) send user data to OnSefy and read the answer. A module is one brick of that chain. OnSefy brings two action modules, and because it has no trigger of its own, another app or a schedule has to start the run.

Screen a new account as it arrives. A sign-up lands in your form tool or your app, and the next module, Smart User Risk Assessment, passes that user to OnSefy. The documentation files OnSefy under AI and gives no description of this module, so treat the name as the promise and check the output during your first test.

Reach an endpoint the listed modules skip. Make an API Call reuses the same connection and lets you call any endpoint of the OnSefy API. It is the way out when you need something the risk module does not cover, provided you have the OnSefy API reference at hand.

Hand the verdict to the rest of your stack. Whatever OnSefy returns becomes a bundle (one item passed from module to module) that you can map into a CRM, a sheet or a message. New to mapping? The Make training walks through it.

What Make cannot do here: watch OnSefy for events, since no trigger exists. The documentation also warns that its own text is AI-generated and may contain mistakes, so confirm key details with OnSefy. If a run fails, Make troubleshooting covers the usual causes, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect OnSefy to Make?

  1. 01

    Copy your OnSefy credentials

    Log in to OnSefy, open Settings, then API Integration. Copy the API key shown on screen, then the Service ID. No account yet? The doc asks for an active OnSefy account before you start.

  2. 02

    Open the connection window in Make

    In your Make account, add an OnSefy module to a scenario and click Create a connection. A connection is your OnSefy account linked to Make once, then reused by both modules. The Connection name field is optional; a clear label helps later.

  3. 03

    Paste the key and the Service ID

    Enter the credentials you copied from OnSefy, or follow the instructions Make shows on screen. Save, and the connection appears in the module. From now on, any OnSefy module in any scenario can pick it from the list.

First scenario

Your first scenario with OnSefy

GoalWhen a new user record shows up in another app, Make sends it to OnSefy for a risk assessment.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since OnSefy has no trigger, this first module comes from the app where your new users appear.

  2. 02

    Set the starting module

    Search that other app by name, pick the module that returns new users, and connect the account. Each new user it finds becomes one bundle for the rest of the scenario.

  3. 03

    Add Smart User Risk Assessment

    Click the + on the right, search OnSefy, pick Smart User Risk Assessment and select your connection. Fill its fields by mapping the user data from the first module.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time, and you can open each module to read the bundles it received. Check what OnSefy returned before you rely on it anywhere.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go faster. Then switch the scenario on so it keeps checking new users.

Modules

What can OnSefy do in Make?

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

OnSefy1

Make an API Call

ActionIn the docs only

This module gets you any OnSefy endpoint that the risk module leaves out, using the connection you already created. You write the request yourself, so the OnSefy API reference becomes your guide.

When to use it
a call you need is missing from the module list, and waiting for a dedicated module is not an option.
Watch out
you write the request yourself, so run it once and read the returned bundle before mapping it further.
OnSefy2

Smart User Risk Assessment

ActionIn the docs only

You get OnSefy's risk view on one user, returned inside your scenario as a bundle you can pass to the next module. The documentation gives the name and nothing more, so your first test shows the actual output.

When to use it
a new account arrives from your sign-up form and you want it checked before your team grants access.
Watch out
each user checked costs one operation, the unit Make counts on your plan.
Need help

Need help automating OnSefy with Make?

A person reads every message.

FAQ

OnSefy and Make: frequent questions

01Is the OnSefy Make integration free?
Yes on the Make side: OnSefy is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs a scheduled scenario no more often than every 15 minutes, stops a run after 5 minutes and caps transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and count usage in credits each month. OnSefy itself needs an active account, and its own pricing page covers the subscription.
02What do you need to connect OnSefy to Make?
An active OnSefy account and two values from it: the API key and the Service ID, both listed under Settings, then API Integration. In Make, add an OnSefy module, click Create a connection, give it a name if you like and paste the two values. The connection is then shared by both OnSefy modules, so you only do this once per account. Keep the Service ID handy too: the doc asks you to copy it along with the key.
03Does OnSefy trigger Make scenarios in real time?
No, because OnSefy has no trigger module in Make. The scenario has to start somewhere else: a trigger from the app where your users sign up, or the schedule on the first module, every 15 minutes by default. When the starting app offers an instant trigger, the one with the lightning badge, it calls Make through a webhook as soon as something happens, and the OnSefy check follows within the same run.
04What if the OnSefy module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the OnSefy API with the connection you already have, so a missing module rarely blocks you. You write the request from the OnSefy API reference and test it with Run once. The Make documentation for OnSefy is AI-generated and may contain mistakes, so when something looks off, confirm the details with OnSefy directly. Each call you add still counts as one operation on your Make plan, like any other module.
05Should you use Make or n8n for OnSefy?
It depends on the tool your team already runs. In Make, OnSefy comes with Smart User Risk Assessment and Make an API Call, which covers the rest of its API. The same app often has an n8n node as well, but this page does not confirm one for OnSefy, so check the n8n node list before deciding. Pick the platform where the rest of your onboarding flow already lives. A missing piece on either side can often be covered by a generic API call.
Same platform

Other docs you might need on this stack.

Browse all integrations