Resources · Make integration

Greip - Fraud Prevention Make integrationAutomate Greip - Fraud Prevention with Make.

Can Make flag a risky sign-up before it turns into a chargeback? The Greip - Fraud Prevention Make integration brings 16 modules: 7 scheduled triggers and 9 actions. This guide connects your account, then walks you through a first scenario that scores new emails.

Try the Greip - Fraud Prevention integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Greip - Fraud Prevention Make integration do for you?

It lets Make, a no-code automation tool, send data to Greip and act on the answer. A scenario (the automation you build in Make, a chain of modules) can score an email, an IP or a phone number, look up a card BIN or an IBAN, and pass the result to the rest of your stack.

Screen sign-ups before they reach your CRM. Place Score an Email Address right after your form app, then route low-trust addresses to a manual review list instead of your welcome sequence.

Check a payment before you ship. Lookup a BIN/IIN reads the card's issuing bank from its first digits, and Score an IP Address adds a risk score for the IP behind the order. Together they give your ops team something concrete to judge.

Keep comments clean. Detect a Profanity can sit between a review form and your site, so offensive text gets held back rather than published.

Know the limits first. Make's own documentation for Greip is marked as limited: it lists the modules but describes none of them, so field names and results only show up once you connect and click Run once. The seven triggers are listed as scheduled, which means Make polls Greip on a timer instead of hearing from it instantly. If you are still choosing a tool, the n8n vs Make comparison lays out the criteria, and the Make training covers the editor from scratch.

Connect

How do you connect Greip - Fraud Prevention to Make?

  1. 01

    Add a Greip module

    In a scenario, click the + and search for Greip - Fraud Prevention. Pick any module, then click Create a connection. A connection is your Greip account linked to Make once, reused by every Greip module afterward.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, such as the account it belongs to. Then either approve Make on Greip's own page or paste the key Greip gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Make returns you to the module, and the connection now appears in its dropdown. Every other Greip module in any scenario can pick the same connection without logging in again.

First scenario

Your first scenario with Greip - Fraud Prevention

GoalWhen a new sign-up reaches your form app, Make asks Greip to score the email address before anything else happens.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Start with the trigger of the app where sign-ups arrive, like your form tool.

  2. 02

    Add Score an Email Address

    Click the + on the right of that first module, search for Greip - Fraud Prevention and pick Score an Email Address. Choose the connection you created earlier.

  3. 03

    Map the email

    In the Greip module, map the email coming from the first module. Each bundle, one item passed from module to module, here carries one sign-up and its address.

  4. 04

    Test with Run once

    Submit a test sign-up, then click Run once. Open the bubble above the Greip module to read what came back: that is where you discover the fields Greip returns.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each Greip call counts as one operation on your plan.

Triggers

What starts a Greip - Fraud Prevention scenario?

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

Greip - Fraud Prevention1Watch Fraudulent Payments

Watch Fraudulent Payments

triggerIn the docs only

This trigger gives you a scenario that reacts to payments Greip has marked as fraudulent, judging by its name, so each case can land with a person rather than sit in a dashboard nobody opens.

How it fires
scheduled: Make checks the app on the scenario's schedule, 15 minutes apart by default, and picks up what is new since the last check.
When to use it
you want a ticket or a message to your finance lead whenever a flagged payment appears.
Watch out
the doc gives no description of this module, so confirm with Run once which payments it actually returns before you build refunds on it.
Greip - Fraud Prevention2Watch New Hosts Authorized

Watch New Hosts Authorized

triggerIn the docs only

Here you get a heads-up whenever a new host appears on your Greip account's authorized list, as the module name suggests, which helps whoever manages access keep track of changes.

How it fires
scheduled: Make checks the app on the scenario's schedule and only sees a new host at the next poll, not the moment it is added.
When to use it
a security or IT channel should learn about every newly authorized domain.
Watch out
nothing in the doc says what a host record contains, so read the first bundle before mapping anything into a message.
Greip - Fraud Prevention3Watch Profane Content

Watch Profane Content

triggerIn the docs only

Your moderation queue gets fed automatically: going by its name, this trigger picks up content Greip has flagged as profane and starts the scenario with it.

How it fires
scheduled: Make checks the app on the scenario's schedule, so flagged items arrive in batches at each run rather than one by one as they happen.
When to use it
community managers want flagged posts copied to a sheet or a chat room for review.
Watch out
if you only need to test a single text, the Detect a Profanity action is the lighter choice; this trigger suits a stream of content.
Greip - Fraud Prevention4Watch Subscription Expiry

Watch Subscription Expiry

triggerIn the docs only

You stay ahead of your own Greip plan: the name points to a trigger about your subscription reaching its end, which is the kind of reminder that tends to get lost in an inbox.

How it fires
scheduled: Make checks the app on the scenario's schedule and passes along what it finds on that pass.
When to use it
the person who pays for tools should get a task before fraud checks stop working.
Watch out
the doc does not say how early this fires relative to the expiry date, so do not assume a notice period; check the bundle after a Run once.
Greip - Fraud Prevention5Watch Suspicious Email Addresses

Watch Suspicious Email Addresses

triggerIn the docs only

This one hands you the email addresses Greip considers suspicious, based on its name, so your team can act on them in the tools it already uses instead of checking Greip by hand.

How it fires
scheduled: Make checks the app on the scenario's schedule; on the Free plan the shortest gap between two runs is 15 minutes.
When to use it
you want to tag matching contacts in your CRM or pause their onboarding emails.
Watch out
it likely surfaces results from checks Greip has already run; to score a fresh address yourself, use the Score an Email Address action.
Greip - Fraud Prevention6Watch Suspicious IPs

Watch Suspicious IPs

triggerIn the docs only

With it, the IP addresses Greip labels as suspicious turn into rows, alerts or tasks, as the module name indicates, giving support and security the same list to work from.

How it fires
scheduled: Make checks the app on the scenario's schedule, which you set on the clock of this first module.
When to use it
a shared sheet of flagged IPs helps your team spot repeat visitors across accounts.
Watch out
each IP that comes through is one bundle, and every module after it runs once per bundle, which adds operations on your plan quickly.
Greip - Fraud Prevention7Watch Suspicious Phone Numbers

Watch Suspicious Phone Numbers

triggerIn the docs only

Phone numbers Greip treats as suspicious become the starting point of your scenario, going by the name, so dubious numbers can be kept out of SMS campaigns or callback lists.

How it fires
scheduled: Make checks the app on the scenario's schedule and processes everything new it finds in one run.
When to use it
your sales team should stop calling numbers already flagged during sign-up.
Watch out
the doc lists no fields for this trigger; run it once on real data and note what the number looks like before you filter on it.
Modules

What can Greip - Fraud Prevention do in a scenario?

Greip - Fraud Prevention gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Greip - Fraud Prevention1

Detect a Profanity

ActionIn the docs only

You find out whether a piece of text contains offensive language before it goes public, which is what the module name promises, and the scenario can branch on that answer.

When to use it
a product review or comment arrives from a form and should be held if it is abusive.
Watch out
map only the text itself; test with Run once to see how Greip reports a match.
Greip - Fraud Prevention2

Lookup a BIN/IIN

ActionIn the docs only

Card details come back from the first digits of a card number, the BIN or IIN, so you learn which bank issued a card without asking the customer anything.

When to use it
an order looks unusual and your team wants the card's origin next to the order before shipping.
Watch out
send the BIN only, never a full card number, into a module or a log you do not control.
Greip - Fraud Prevention3

Lookup an ASN

ActionIn the docs only

An ASN identifies the network an IP belongs to, and this lookup tells you who runs it, which helps separate a home connection from a hosting provider.

When to use it
after Lookup an IP Address, when you want the network owner as a second clue.
Watch out
the doc does not say which ASN format it expects; check the input on your first Run once.
Greip - Fraud Prevention4

Lookup an IBAN

ActionIn the docs only

Bank account numbers get a sanity check before you pay or debit them: judging by the name, this module returns what Greip knows about an IBAN.

When to use it
a supplier sends new bank details, and your finance team wants them checked before the first transfer.
Watch out
a lookup does not prove who owns the account, so keep a human approval step for changed details.
Greip - Fraud Prevention5

Lookup an IP Address

ActionIn the docs only

This gives you context on an IP address, such as where it seems to come from, without scoring it, which is handy when you want facts rather than a verdict.

When to use it
you log a sign-up and want its origin stored next to the account for later review.
Watch out
if you need a risk rating to decide automatically, Score an IP Address is the better fit.
Greip - Fraud Prevention6

Make an API Call

ActionIn the docs only

Anything in the Greip API that the other modules do not cover stays reachable, with the same connection, so you are not stuck when a need goes beyond the list.

When to use it
Greip offers an endpoint that no module on this page matches.
Watch out
you write the request yourself, so keep Greip's API reference open while you build it.
Greip - Fraud Prevention7

Score a Phone Number

ActionIn the docs only

A phone number comes back with a risk score, so you can decide automatically whether it deserves a call, an SMS or a closer look first.

When to use it
a lead form collects numbers and your sales team only wants credible ones in its queue.
Watch out
the doc does not describe the score, so read one real result before choosing the threshold that decides who gets called.
Greip - Fraud Prevention8

Score an Email Address

ActionIn the docs only

Every new address gets a trust score before it enters your lists, which stops throwaway or fake emails from slipping into onboarding and newsletters.

When to use it
right after a sign-up form, as in the first scenario on this page.
Watch out
one address is one operation; for a large import, score only new contacts rather than your whole list again.
Greip - Fraud Prevention9

Score an IP Address

ActionIn the docs only

You get a risk score for the IP behind a sign-up or an order, so a risky visitor can be held back before you approve anything.

When to use it
checkout or account creation, when a high score should send the case to manual review.
Watch out
make sure you pass the visitor's IP, not your own server's, or every score will look the same.
Need help

Need help automating Greip - Fraud Prevention with Make?

A person reads every message.

FAQ

Questions about the Greip - Fraud Prevention Make integration

01Is the Greip - Fraud Prevention Make integration free?
Yes, on the Make side. Greip - Fraud Prevention is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to one minute and allow up to 40 minutes of execution. Your Greip subscription is a separate matter, handled on Greip's side.
02What do you need to connect Greip - Fraud Prevention to Make?
A Greip account and access to its credentials. Make's documentation for Greip lists no prerequisites and no specific connection steps, so the generic flow applies: add any Greip module, click Create a connection, optionally name it, then authorize Make on Greip's page or paste the key Greip provides, and click Save. After that, every Greip module in any scenario can reuse the same connection. If the window asks for something you cannot find, the Make troubleshooting page on this site is a good next stop.
03Do Greip - Fraud Prevention triggers in Make react in real time?
No. All seven Greip triggers are listed as scheduled, meaning Make polls Greip on the scenario's schedule instead of being notified by a webhook. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan; paid plans go down to one minute. If a flagged payment must trigger something within seconds, these triggers will not do that, and the right design depends on what Greip itself can send.
04What if a Greip - Fraud Prevention module is missing in Make?
Use Make an API Call. It calls any endpoint of the Greip API from inside the scenario, with the connection you already set up, so you are not limited to the nine actions listed. Keep in mind that Make's documentation for Greip is marked as limited and describes none of the modules, so test each one with Run once to see what it returns before relying on a specific field.
05Should you use Make or n8n for Greip - Fraud Prevention?
It depends on where the rest of your automations live. On Make, Greip comes with 16 modules, including seven scheduled triggers and Make an API Call, and it is available from the Free plan. n8n often has a node for the same app, but this page does not confirm one for Greip, so check its node list before deciding. The comparison page on this site sets the two tools side by side on neutral criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations