Resources · Make integration

attachmentAV Make integrationAutomate attachmentAV with Make.

Want every incoming file or link checked for malware before anyone opens it? The attachmentAV Make integration gives you 2 action modules, one for files and one for URLs. This guide shows how to connect your account and build a first scan step.

Try the attachmentAV integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you do with the attachmentAV Make integration?

It lets Make send a file or a web address to attachmentAV and get the scan result back inside a scenario, which is the automation you build in Make: a chain of modules, each one a single brick such as an action. You add the check in the middle of a flow you already run, with no code.

Screen customer uploads. A form or a mailbox hands a file to Make, Scan a File for Viruses/Malware checks it, and only then does the next module store it or pass it to a colleague. Each file is one bundle, the item that flows from one module to the next.

Vet links before sharing them. When a support ticket or a chat message contains a URL, Scan a URL for Viruses/Malware checks the address first, so your team decides with the result in hand.

Add a safety gate to an existing flow. If a scenario already moves documents between tools, one extra scan module sits between the source and the destination without changing the rest.

What Make does not give you here: there is no trigger, so attachmentAV never starts a scenario by itself, and there is no Make an API Call module for anything beyond these two scans. You also need a paid attachmentAV plan. If the scan step fails, the Make troubleshooting guide helps you read the error. Weighing another tool? The n8n vs Make comparison lays out the differences, and Make pricing explains how operations are counted.

Connect

How do you connect attachmentAV to Make?

  1. 01

    Get your API key

    In your attachmentAV account, open the subscription section, pick the subscription plan meant for Make and finish checkout if asked. The API key then appears on screen: copy it, the connection needs nothing else.

  2. 02

    Add a module and create the connection

    In your scenario, add one of the attachmentAV modules and click Create a connection. A connection is your attachmentAV account linked to Make once, then reused by both modules. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the on-screen instructions, then save. From then on the module shows your connection in its list and you can fill in the rest of its settings.

First scenario

Your first scenario: scan every new file before it moves on

GoalWhen another app hands Make a new file, attachmentAV scans it and Make passes on the result.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your files arrive, since attachmentAV has no trigger of its own.

  2. 02

    Set up the source module

    Connect the source app and fill in its fields. Once the connection exists, Make lists the folders or objects it can read, so you choose from a menu instead of typing a path.

  3. 03

    Add the scan

    Click the + to the right of the first module, search for attachmentAV and pick Scan a File for Viruses/Malware. Select your connection, then map the file coming from the previous module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can open the scan output and see what the next step will get.

  5. 05

    Schedule and switch on

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

Modules

What the attachmentAV modules do

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

attachmentAV1

Scan a File for Viruses/Malware

ActionIn the docs only

Sends a file from your scenario to attachmentAV and brings the verdict back, so an attachment gets checked before it lands in shared storage or reaches a teammate.

When to use it
right after the module that receives files from outside, such as a web form upload or an email attachment, and before any module that saves them.
Watch out
on the Make Free plan, files are capped at 5 MB, so larger documents need a paid Make plan to pass through.
attachmentAV2

Scan a URL for Viruses/Malware

ActionIn the docs only

Checks a web address with attachmentAV instead of a file, which is handy when what arrives is a link and nothing has been downloaded yet.

When to use it
a lead form, a ticket or a message contains a link that someone on your team will click, and you want the result before anyone clicks.
Watch out
pick this module rather than the file scan whenever you only hold the address, since the file module is built for a file, not a link.
Need help

Need help automating attachmentAV with Make?

A person reads every message.

FAQ

attachmentAV and Make: common questions

01Is the attachmentAV Make integration free?
Partly. On the Make side, attachmentAV is a standard app, so it works from the Free plan, which allows 2 active scenarios, a scheduled run every 15 minutes at most, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. On the attachmentAV side, the documentation requires a paid subscription and an API key, so the scans themselves are not free. Paid Make plans lift the interval to 1 minute and the run time to 40 minutes.
02What does it take to connect attachmentAV to Make?
You need a Make account, an attachmentAV account with a paid subscription, and the API key that attachmentAV shows once you pick the subscription plan for Make. In Make, add an attachmentAV module, click Create a connection, optionally name it, then paste the key. The same connection then serves both modules, the file scan and the URL scan, so you set it up once for the whole scenario and reuse it in every later scenario too.
03Can attachmentAV start a Make scenario on its own?
No. attachmentAV has no trigger module, so it never starts a scenario. The flow begins with another app, for example a form or storage tool where files show up, or with the schedule on the first module, which runs every 15 minutes by default on a new scenario. A trigger from another app can be scheduled, where Make checks at intervals, or instant, where that app calls Make through a webhook as soon as something happens. attachmentAV then runs as a step inside it.
04What if an attachmentAV module is missing in Make?
The integration only covers two actions, a file scan and a URL scan, and it has no Make an API Call module to reach other parts of the attachmentAV service. If you need more, look for another app in Make that covers the task, or ask the Hack'celeration team to review your case. Also note the vendor warning in the Make documentation: the page is AI-generated from attachmentAV docs and may contain mistakes, so check anything important with attachmentAV directly.
05Make or n8n for attachmentAV?
It depends on where the rest of your automations already live. In Make, attachmentAV gives you two ready scan modules that work from the Free plan, as long as you hold a paid attachmentAV subscription. The same app often has an n8n node too, so if your team already runs its flows in n8n, check there first. Pick the tool where the steps before and after the scan already exist, so the check slots in without rebuilding anything.
Same platform

Other docs you might need on this stack.

Browse all integrations