Resources · Make integration

Avisa API Make integrationAutomate Avisa API with Make.

Want another tool to send files through Avisa API on its own? The Avisa API Make integration gives you 7 action modules, from sending a document to checking a number. This page connects your account, builds a first scenario with you and explains each module.

Try the Avisa API integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Avisa API Make integration do for you?

The Avisa API Make integration lets a Make scenario (the automation you build, a chain of modules) act inside your Avisa API account. Every module is an action, so something else has to start the scenario: another app, or the schedule Make gives each new scenario, every 15 minutes by default.

Files that leave on their own. A contract signed in another tool can flow into Send a Document, so the recipient gets the file without anyone opening Avisa API.

Visuals for a campaign. Send an Image and Send a Media cover pictures and other media, fed by whatever app stores them upstream.

A safety check first. Check a Number can sit before a send, and Check a Instance Status tells you whether your Avisa API setup is ready before the scenario goes further.

The official modules come without descriptions, and the doc itself warns that its text may contain errors, so test each module with Run once. Anything the list misses goes through Make an API Call. The same app may also exist as an n8n node; the n8n vs Make comparison lays out how the two tools differ. For a guided start, see Make training, and when a run fails, Make troubleshooting.

Connect

How do you connect Avisa API to Make?

  1. 01

    Get your API key

    Before touching Make, you need an active Avisa API account and an API key from it. No account yet? Create one on Avisa API first, then keep the key at hand for the next step.

  2. 02

    Add a module and create the connection

    In your scenario, add any Avisa API module and click Create a connection. A connection is your Avisa API account linked to Make once, then reused by every module of the app. The Connection name field is optional.

  3. 03

    Paste your credentials

    Enter the credentials you copied from Avisa API, or follow the instructions Make shows on screen, then save. The connection now appears in the dropdown of every Avisa API module you add later.

First scenario

Your first scenario with Avisa API

GoalWhen a new entry arrives in another app, Make checks the number with Avisa API and then sends the document.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Avisa API has no trigger, pick the app that holds your contacts or form entries.

  2. 02

    Add Check a Number

    Click the + on the right of that first module, search for Avisa API and choose Check a Number. Select your connection, then map the number from the previous module.

  3. 03

    Add Send a Document

    Click the next + and pick Send a Document. Fill its fields by mapping data from the earlier modules, so each bundle (one item, here one entry) gets its own file.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Open them to confirm the number check and the send behave as you expect.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, 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 each Avisa API module does

Avisa API gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Avisa API1

Check a Instance Status

ActionIn the docs only

Asks Avisa API about the state of your instance, so the scenario learns whether it can go on before anything is sent. The module name suggests this; the doc gives no description.

When to use it
at the start of a scenario that sends many files, as a guard placed ahead of the sending modules.
Watch out
read what it returns with Run once before building a filter on it.
Avisa API2

Check a Number

ActionIn the docs only

Its name points to a check on a phone number, a deduction since the doc gives no description: useful before you spend an operation on a send that might go nowhere. Its exact output is not documented, so look at the bundle it returns during your first test.

When to use it
right after a new contact comes in from a form or a CRM, before Send a Document or Send an Image.
Avisa API3

Make an API Call

ActionIn the docs only

Opens the whole Avisa API to your scenario, reusing the connection you already created. You write the request yourself, and in exchange you reach any endpoint the six other modules leave out.

When to use it
when none of the listed modules does what you need.
Watch out
you need to know the endpoint from the Avisa API documentation.
Avisa API4

Send a Document

ActionIn the docs only

Sends a file, such as a quote, an invoice or a contract, through your Avisa API account to the recipient you map. It is the module for paperwork rather than pictures.

When to use it
once a document is ready in another tool, for example after a deal is closed in your CRM.
Watch out
the Free plan handles files up to 5 MB.
Avisa API5

Send a Media

ActionIn the docs only

Covers media sends in general, the broader choice when the file is not strictly a picture or a document. Which formats it accepts is not described in the doc, so test with a real file.

When to use it
when your source app stores mixed files and you want one module to handle them.
Watch out
run it once and check the result before switching on.
Avisa API6

Send a Messenger

ActionIn the docs only

Pushes a message out through Avisa API. The name is all the doc provides, so open the module in the editor to see which fields it asks for before planning around it.

When to use it
when the scenario needs to notify someone rather than attach a file, for instance to confirm that a request was received.
Avisa API7

Send an Image

ActionIn the docs only

Delivers a picture to your recipient, like a product visual or a scanned receipt. Pick it over Send a Media when you know the file is an image and want the clearest setup.

When to use it
a new product photo lands in a shared folder and should reach a client.
Watch out
on the Free plan, files stay under 5 MB.
Need help

Need help automating Avisa API with Make?

A person reads every message.

FAQ

Questions about the Avisa API Make integration

01Is the Avisa API Make integration free?
Yes, on the Make side. Avisa API is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs at most every 15 minutes, stops each execution after 5 minutes, handles files up to 5 MB and moves 512 MB of data. Paid plans go down to a 1 minute interval, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations, one per module run on a bundle. What your Avisa API account costs is a separate matter, set by Avisa API.
02What do you need to connect Avisa API to Make?
An active Avisa API account and an API key. In Make, add any Avisa API module, click Create a connection, name it if you like, then enter the credentials copied from Avisa API or follow the on-screen instructions. The doc also mentions a Bearer Token found in Postman, inside the authentication section of your workspace or API collection. Once saved, the same connection serves all 7 modules, so you set it up only once per account.
03Does Avisa API trigger a Make scenario in real time?
No, Avisa API has no trigger in Make, neither scheduled nor instant. Its 7 modules are all actions, so the scenario must start somewhere else. The usual option is a trigger from another app, for example a form or a CRM that watches for new entries. The other is the schedule on the first module: a new scenario runs every 15 minutes by default, and paid plans can go down to 1 minute. Pick the start that matches the event you care about.
04What if an Avisa API module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Avisa API with the connection you already have, so a gap in the list does not block you. You will need the endpoint details from the Avisa API documentation. Also keep in mind that the Make doc for this app says its content was generated from the vendor documentation and may contain errors, so verify key behaviour with Run once and contact Avisa API directly when something does not match.
05Should you use Make or n8n for Avisa API?
It depends on the tool your team already works in. On Make, Avisa API offers 7 action modules plus a free entry through the Free plan, and each run is counted in operations. The same app may also have an n8n node, which is worth checking before you decide. Compare what each tool offers for your exact use: the modules you need, how the scenario starts, and how usage is counted. No ranking between the two applies to every case.
Same platform

Other docs you might need on this stack.

Browse all integrations