Resources · Make integration

detecting-ai Make integrationAutomate detecting-ai with Make.

Need to check whether a piece of text was written by AI before it goes any further? The detecting-ai Make integration gives you 2 action modules for that check. This guide walks you through linking your API key, building a first scenario and choosing the right module.

Try the detecting-ai integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the detecting-ai Make integration do for you?

The detecting-ai Make integration lets a Make scenario, the automation you build in Make as a chain of modules, hand content to detecting-ai and receive its analysis without anyone copying and pasting. Each module is one brick of that chain, and detecting-ai brings two of them, both actions.

Screen incoming submissions. Content collected by another app, such as a guest article or an application answer, flows into Detect AI Generated Content before a person reads it. The editor opens a file that has already been checked.

Keep a record of every check. Map the result of the detection into a later module of another app, so each piece of content keeps a trace of its analysis next to it.

Reach the rest of the API. When the ready-made module is not enough, Make an API Call uses the same connection to call any endpoint of the detecting-ai API.

What Make does not offer here is a trigger: detecting-ai cannot start a scenario by itself. The scenario opens on another app or on Make's own schedule. The official documentation also says its text was generated with AI and may contain mistakes, so check important details with detecting-ai directly. If you are still choosing a platform, the n8n vs Make comparison lays out the criteria, the Make pricing page explains the plans, and the Make training teaches scenario building step by step.

Connect

How do you connect detecting-ai to Make?

  1. 01

    Copy your API key

    Sign in to your detecting-ai account, open the dashboard and click the API section. Copy the API key shown on screen. Make needs it to act on your behalf, and you will paste it in the next step.

  2. 02

    Add a detecting-ai module

    In your Make scenario, add the Detect AI Generated Content module and click Create a connection. A connection is your detecting-ai account linked to Make once, then reused by both modules. The Connection name field is optional.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the instructions Make shows on screen, and confirm. The connection now appears in the module, and any other detecting-ai module can pick it from the list without asking for the key again.

First scenario

Your first scenario with detecting-ai

GoalWhen new text reaches another app, Make sends it to detecting-ai and passes the result on.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since detecting-ai has no trigger, pick the app where your text arrives, for example a form or a shared document tool.

  2. 02

    Add Detect AI Generated Content

    Click the + on the right of that first module, search for detecting-ai and choose Detect AI Generated Content. Select your connection, or click Create a connection if this is your first time.

  3. 03

    Map the text to check

    Fill the module fields by mapping the text from the previous module. Each item that moves between modules is a bundle: here, one piece of content per bundle, checked one at a time.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received and confirm that detecting-ai sent back its analysis.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Then switch the scenario on. Every module run is an operation, the unit Make counts on your plan.

Modules

The detecting-ai modules in Make

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

detecting-ai1

Detect AI Generated Content

ActionIn the docs only

This action sends a piece of content to detecting-ai and returns its analysis inside the scenario, so the next module can use the result instead of someone reading the text first.

When to use it
right after the module that brings in new text, whenever that text should be checked before it is published or reviewed.
Watch out
the documentation lists no fields for this module, so open it in Make to see what it asks for and test on real content with Run once.
detecting-ai2

Make an API Call

ActionIn the docs only

Here you get access to any endpoint of the detecting-ai API from your scenario, through the connection you already created, with no second key to paste.

When to use it
when the task you need is not covered by Detect AI Generated Content, which is the only ready-made action of this app.
Watch out
you build the request yourself, so keep the detecting-ai API reference open and test each call with Run once before switching the scenario on.
Need help

Need help automating detecting-ai with Make?

A person reads every message.

FAQ

Questions about the detecting-ai Make integration

01Is the detecting-ai Make integration free?
Yes, on the Make side: detecting-ai is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Your detecting-ai subscription is a separate matter, described on the detecting-ai pricing page, and this guide does not quote its prices.
02What does the detecting-ai Make integration need to connect?
A detecting-ai account and its API key. Sign in to detecting-ai, open the dashboard, click the API section and copy the key displayed. In Make, add a detecting-ai module, click Create a connection, give it a name if you like and paste the key. That one connection then serves both modules of the app, including Make an API Call, so you only go through these steps once for each detecting-ai account.
03Can detecting-ai start a Make scenario in real time?
No, because detecting-ai has no trigger module in Make. The scenario starts elsewhere. Either its first module belongs to another app, and if that app has an instant trigger it calls Make through a webhook as soon as something happens, or the scenario runs on Make's schedule, every 15 minutes by default. In both cases Detect AI Generated Content comes second and checks the content that the first module delivered.
04What if a detecting-ai module is missing in Make?
Use Make an API Call. It calls any endpoint of the detecting-ai API with the connection you already have, so you can cover what Detect AI Generated Content does not. You write the request yourself from the detecting-ai API reference. Keep in mind that the official Make documentation for this app says its text was generated with AI and may contain mistakes, so confirm important details with detecting-ai before relying on them.
05Should the detecting-ai integration run on Make or n8n?
It depends on your criteria rather than on a winner. In Make, detecting-ai offers 2 modules, including Make an API Call for the rest of its API, and the editor draws each step so you can follow the flow visually. The same app often has an n8n node too; check that before deciding. Compare how each tool fits your team and the other apps in your stack, and read the n8n vs Make comparison linked above for the detailed criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations