Resources · Make integration

Visork Make integrationAutomate Visork with Make.

Need to screen content for nudity before it goes live? The Visork Make integration gives you 2 action modules, one built for nudity detection and one open door to the Visork API. This guide shows who it suits, how to link your account and how to build a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Visork Make integration do for you?

The Visork Make integration lets a Make scenario, the automation you build in Make as a chain of modules, hand content to Visork and use its answer in the next step. A module is one brick of that chain. Visork brings two of them, both actions, so something else has to start the scenario.

Moderating uploads on a community site. When a member submits content through another app, a scenario passes it to Detect a Nudity and routes the result to the next module, so a moderator only opens what needs a human look.

Keeping a product catalog clean. A marketplace team can run supplier content through the same module before it is published, and keep the answer next to the item in whatever tool they already use.

Reaching the rest of the API. Make an API Call calls any Visork endpoint with the connection you already set up, which covers what the listed module does not.

Know the limit before you start: Make says it cannot publish complete documentation for Visork, because too little public information exists about the app. Test every scenario with real content and read what comes back. The Make troubleshooting guide helps when a run fails, and Make pricing explains how operations are counted. Weighing tools? The n8n vs Make comparison lays out the criteria.

Connect

How do you connect your Visork account to Make?

  1. 01

    Add a Visork module

    In your scenario, add Detect a Nudity or Make an API Call, then click Create a connection. A connection is your Visork account linked to Make once, and every Visork module reuses it afterwards.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, which is optional but handy with several accounts. Then either authorize Make on the Visork page that opens, or paste the key Visork gives you, depending on what the window asks for.

  3. 03

    Save and check the module

    Click Save. The module now uses your connection. If Make can read anything from the account, it offers it in the fields below, so you pick values instead of typing them.

First scenario

Your first scenario with Visork and Make

GoalWhen new content lands in the app your users submit to, Make sends it to Visork and passes the answer on.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Visork has no trigger, so pick the app where submissions arrive and choose its module that starts the flow.

  2. 02

    Add Detect a Nudity

    Click the + on the right of that first module, search for Visork and pick Detect a Nudity. Click Create a connection if this is your first Visork module.

  3. 03

    Map the content

    Fill the module fields by mapping data from the first module: click a field and pick the value it received. That value is part of a bundle, one item passed from a module to the next.

  4. 04

    Test with Run once

    Click Run once, submit a test item in the source app, and open the bundles each module received. Check what Visork sent back before you add anything after it.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which is every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What the Visork modules do

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

Visork1

Detect a Nudity

ActionIn the docs only

This is the module you add when a scenario has to ask Visork whether a piece of content contains nudity, so the answer can decide what happens next instead of a person checking by hand.

When to use it
right after the module that receives user submissions, before anything gets published or shared.
Watch out
Make has no full documentation for this app, so run it once on known samples and read the returned bundle before you filter on it.
Visork2

Make an API Call

ActionIn the docs only

With this one you reach any Visork API endpoint from your scenario, reusing the same connection, which matters when the dedicated module does not cover what you need.

When to use it
Visork offers a feature in its API that has no module of its own in Make.
Watch out
you describe the request yourself, so Make gives no detail for this app, so the request details have to come from Visork itself; test with Run once before you switch the scenario on.
Need help

Need help automating Visork with Make?

A person reads every message.

FAQ

Visork and Make: common questions

01Is the Visork Make integration free?
Yes, Visork is a standard app, so its modules work on the Make Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per execution, 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 cap on active scenarios and allow 40 minutes per run. Usage is counted in operations, one per module per bundle. Any Visork subscription is separate and not covered here.
02What do you need to connect Visork to Make?
A Visork account and a Make account. Make's documentation lists no other prerequisite. Add a Visork module, click Create a connection, optionally name it, then authorize Make on the Visork page or paste the key Visork provides, and click Save. The connection is stored once and reused by both Visork modules. Since Make notes that its Visork documentation is limited, keep the key or login at hand and test the connection with a sample run right away.
03Does Visork trigger a Make scenario in real time?
No, Visork has no trigger in Make, neither scheduled nor instant, so it cannot start a scenario by itself. Start the flow from another app instead: the trigger of the tool where content arrives, or a schedule set on the first module, every 15 minutes by default. Visork then acts as a step in the middle. If the source app offers an instant trigger, which fires through a webhook, the check happens as soon as that app calls Make.
04What if a Visork module is missing in Make?
Use Make an API Call. It sends a request to any Visork API endpoint with the connection you already have, so a feature without its own module is still within reach. Keep in mind that Make currently cannot provide complete documentation for Visork, because public information about the app is scarce. So the request details have to come from Visork itself, and on Run once to confirm what comes back before the scenario goes live.
05Should you use Make or n8n for Visork?
It depends on the tool your team already runs. On Make, Visork offers 2 modules, a dedicated nudity check and a general API call, both usable from the Free plan. Many apps also have an n8n node, but nothing here confirms one for Visork, so check the n8n side before you decide. Compare the two on what matters to you: the modules available for this app, how you prefer to build, and where your other automations already live.