Resources · Make integration

FraudLabs Pro Make integrationAutomate FraudLabs Pro with Make.

Can a status change in FraudLabs Pro set off work in your other tools? The FraudLabs Pro Make integration gives you 2 modules: one trigger and one API call. This guide is for store and ops teams new to Make, and it walks you from the API key to a live scenario.

Try the FraudLabs Pro integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the FraudLabs Pro Make integration do?

The FraudLabs Pro Make integration links your FraudLabs Pro account to Make, a visual tool where you chain apps together without code. What you build there is called a scenario. Here it can start when a status changes in FraudLabs Pro, then reach any part of the FraudLabs Pro API.

Alert the right people when a status moves. The Watch status change trigger picks up the change, and the + on its right adds the next brick, called a module, from whichever app your team reads every day. Each changed item travels as a bundle, one item passed from one module to the next.

Reach what the listed modules leave out. Make an API call sends a request to any FraudLabs Pro endpoint with the same connection, so the short catalog does not cap what you can automate.

Chain both. Start on the trigger, then use the API call to fetch or send the extra data your follow-up needs, and test the whole chain before switching it on.

Keep the limits in mind. Make documents this app with no description per module, and its own doc page warns that the text is AI-generated from the FraudLabs Pro documentation, so check important details with FraudLabs Pro. The Make review covers the editor in depth, Make pricing explains how operations are counted, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect FraudLabs Pro to Make?

  1. 01

    Copy your API key

    Log in to FraudLabs Pro and open your account dashboard. Find the section labeled API key and copy the key shown on screen. Make needs it to act on your behalf, so keep it at hand for step three.

  2. 02

    Add a FraudLabs Pro module

    In your scenario, search for FraudLabs Pro, pick a module and click Create a connection. A connection is your FraudLabs Pro account linked to Make once, then reused by both modules. You can type a label in Connection name if you like.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the instructions Make shows on screen, and confirm. The connection now appears in the module, and Make can read your FraudLabs Pro data.

First scenario

Your first scenario with FraudLabs Pro

GoalWhen a status changes in FraudLabs Pro, Make calls the FraudLabs Pro API to handle the follow-up.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor. That empty circle becomes your first module.

  2. 02

    Place the trigger

    Search for FraudLabs Pro, choose Watch status change and pick the connection you created. Then fill the fields the module shows you.

  3. 03

    Add the API call

    Click the + on the right of the trigger and add Make an API call. Enter the endpoint you need from the FraudLabs Pro API docs and map values from the trigger into it.

  4. 04

    Test with Run once

    Click Run once, then change a status in FraudLabs Pro if nothing is waiting. Open the bubble above each module to read the bundles it received and the answer returned.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then turn the scenario on. From then on Make checks for new status changes by itself.

Triggers

What starts a FraudLabs Pro scenario

1 module starts a scenario when something happens in FraudLabs Pro. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by FraudLabs Pro as soon as it happens.

FraudLabs Pro1Watch status change

Watch status change

triggerIn the docs only

Watch status change gives your scenario a starting point: each time a status moves in your FraudLabs Pro account, the change enters Make as a bundle you can pass to the next module.

How it fires
scheduled, Make checks the app on the scenario's schedule. That means every 15 minutes by default, and never faster than 15 minutes on the Free plan.
When to use it
whenever someone on your team has to act after a status update, rather than refreshing the dashboard.
Watch out
Make lists this module without a description, so read its fields in the editor and run a test before relying on it.
Modules

What else FraudLabs Pro can do in Make

FraudLabs Pro gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

FraudLabs Pro1

Make an API call

ActionIn the docs only

With Make an API call, any endpoint of the FraudLabs Pro API is within reach of your scenario, through the connection you already set up. No second login, no extra key to paste.

When to use it
when your need goes beyond watching status changes, since this is the only action the app offers in Make.
Watch out
you write the endpoint and its parameters yourself, so keep the FraudLabs Pro API documentation open while you fill the module.
Need help

Need help automating FraudLabs Pro with Make?

A person reads every message.

FAQ

FraudLabs Pro and Make: common questions

01Is the FraudLabs Pro Make integration free?
Yes, on the Make side. FraudLabs Pro is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at most, 5 minutes of run time per execution and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Every module run counts as one operation on your plan. Your FraudLabs Pro subscription is separate and set on their pricing page.
02What do you need to connect FraudLabs Pro to Make?
An active FraudLabs Pro account with an API key, and a Make account. Log in to FraudLabs Pro, open your dashboard, find the section labeled API key and copy it. In Make, add any FraudLabs Pro module, click Create a connection, name it if you want, then paste the key. Both modules then share that single connection, so you only do this once per account. If the key is missing or the account is inactive, Make cannot create the connection.
03Does the FraudLabs Pro trigger react in real time?
No. Watch status change is a scheduled trigger: Make checks FraudLabs Pro on the schedule set on the first module of the scenario. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval allowed, while paid plans go down to 1 minute. A status that changes right after a check will reach the scenario at the next one. Make gives this module no description, so its type is read from its listing: look for the clock badge on the module to confirm it.
04What if a FraudLabs Pro module is missing in Make?
Use Make an API call. It sends a request to any endpoint of the FraudLabs Pro API with the connection you already have, so a missing module rarely blocks you. You pick the endpoint and fill the parameters based on the FraudLabs Pro API documentation. Keep in mind that Make's doc page for this app is AI-generated from the FraudLabs Pro documentation and may contain mistakes, so confirm important details directly with FraudLabs Pro before going live.
05Should you use Make or n8n for FraudLabs Pro?
It depends on your criteria. In Make, FraudLabs Pro offers one scheduled trigger and one API call module, available from the Free plan, and the API call reaches any endpoint the listed modules skip. Many apps also have an n8n node, so check whether FraudLabs Pro has one and what it covers before you decide. Compare the two on the modules you actually need, then on how each tool counts runs against your plan. The n8n vs Make comparison on this site goes deeper.
Same platform

Other docs you might need on this stack.

Browse all integrations