Resources · Make integration

Avaza Make integrationAutomate Avaza with Make.

Tired of retyping the same client into Avaza after every signed deal? The Avaza Make integration gives you 19 modules: 14 actions and 5 searches on companies, contacts, projects, tasks and invoices. This guide links your account and walks you through a first scenario.

Try the Avaza integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Avaza Make integration automate?

The Avaza Make integration lets a Make scenario (the automation you build, a chain of steps) write to and read from your Avaza account. Each step is a module: here, 14 actions that create, read, update or delete records, and 5 searches that pull lists of them.

Project kickoff without copy and paste. A deal closes in your sales tool, and Make runs Create a Company, then Create a Project for that client, then Create a Task for the first deliverable. The account manager opens Avaza and the project is already there.

Invoices that follow the work. When a job is marked done elsewhere, Create an Invoice drafts the bill in Avaza. Later, List Invoices hands every invoice back to Make, one bundle (one item passed to the next module) at a time, so you can push them into a finance sheet.

A task list that stays in sync. Update a Task changes a task when its source changes, and List Tasks feeds a reporting tool with the current state of a project.

Know the gaps before you plan. Avaza has no trigger module in Make, so a scenario starts from another app or from Make's schedule. Anything the 19 modules skip goes through Make an API Call. The module documentation on Make's side is flagged as AI-generated, and it asks you to double-check important details with Avaza. For help getting started, see the Make training, and if you are weighing tools, the n8n vs Make comparison lays out the criteria. Errors after launch are covered in Make troubleshooting.

Connect

How do you connect Avaza to Make?

  1. 01

    Copy your API token in Avaza

    In Avaza, open Settings, click Manage Developer Apps, then Personal Access Tokens. Copy the token shown on screen. This menu only appears in an active Avaza account.

  2. 02

    Add an Avaza module in Make

    In your scenario, add any Avaza module, for example Create a Company, and click Create a connection. A connection is your Avaza account linked to Make once and reused by every Avaza module.

  3. 03

    Paste the token and save

    Give the connection a name in Connection name if you run more than one Avaza workspace (this field is optional). Paste the token you copied and confirm. Make can now read your companies, projects and tasks.

First scenario

Your first scenario with Avaza

GoalWhen a new client lands in another app, Make creates the company in Avaza and opens a project for it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where new clients appear first, such as your CRM or form tool, and its trigger.

  2. 02

    Add Create a Company

    Click the + to the right of that trigger, search for Avaza and choose Create a Company. Click Create a connection and paste your API token. Map the client name from the first module.

  3. 03

    Chain Create a Project

    Add one more Avaza module, Create a Project, with the + on the right. Map the company Make just created, so the project is filed under the right client instead of floating on its own.

  4. 04

    Test with Run once

    Click Run once and trigger a test client in the first app. Open each module's bubble to read the bundles it received, then check in Avaza that the company and the project appear.

  5. 05

    Schedule and switch it on

    Open the clock on the first module (Scheduling). A new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. Switch the scenario on and it runs by itself.

Modules

What each Avaza module does

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

Avaza1

Create a Company

Action

In Make“Creates a new company.”

Adds a new client company to Avaza, so projects, contacts and invoices have a home to attach to. It is usually the first Avaza step of an onboarding scenario.

When to use it
a deal is won or a signup form comes in and the client does not exist in Avaza yet.
Watch out
run List Companies first if the same client could arrive twice, or you end up with duplicates.
Avaza2

Create a Contact

Action

In Make“Creates a specified contact.”

Records a person in Avaza, the one you send invoices to or discuss the project with. Your team then has a name and details to call without searching through old emails.

When to use it
right after Create a Company, to attach the person who signed or filled in the form.
Watch out
map the company from the previous module, otherwise the contact is not tied to the right client.
Avaza3

Create an Invoice

Action

In Make“Creates a new invoice.”

Drafts an invoice in Avaza from data another module passes along, so billing starts as soon as the work is recorded instead of waiting for someone to remember it.

When to use it
an order is paid in your shop tool, or a milestone is closed in another app.
Watch out
test with Run once on a dummy client first, because a real invoice may be seen by your accountant before you catch a mapping mistake.
Avaza4

Create a Project

Action

In Make“Creates a new project.”

Opens a project in Avaza with its name and client already set, which gives the delivery team a workspace the moment the deal is signed.

When to use it
after Create a Company or Get a Company, when a new engagement starts for that client.
Watch out
the project needs to know its company, so place a company module before it and map its result rather than typing a name by hand.
Avaza5

Create a Task

Action

In Make“Creates a new task.”

Turns a request coming from elsewhere into a task inside an Avaza project, so nothing lives only in an inbox or a chat thread.

When to use it
a support ticket, a form reply or a new row in a sheet has to become work for the team.
Watch out
a task belongs to a project; map the project from Create a Project or List Projects so it does not end up in the wrong place.
Avaza6

Delete a Task

Action

In Make“Deletes a specified task.”

Removes one task from Avaza, useful to keep a project clean when a request is cancelled at its source and should not stay on anyone's plate.

When to use it
a ticket is closed as a duplicate, or a client withdraws a request you had already turned into a task.
Watch out
deletion is final on this path, so run the scenario with Run once on a test task before you let it touch real projects.
Avaza7

Get a Company

Action

In Make“Returns a specified company.”

Reads one company you point to and hands its details to the next modules. Handy when a later step needs the client's data but only has its identifier.

When to use it
before Create a Project or Create an Invoice, when the scenario starts from an ID stored in another tool.
Watch out
it expects a specific company; if you only have a name, List Companies is the better fit.
Avaza8

Get a Contact

Action

In Make“Return a specified contact.”

Fetches the details of a single contact, so an email or a message built later in the scenario can greet the right person by name.

When to use it
you already know which contact you want, for instance because an earlier module returned their ID.
Watch out
one contact comes back, never a list; to browse people across companies, switch to List Contacts instead.
Avaza9

Get an Invoice

Action

In Make“Returns a specified invoice.”

Pulls one invoice out of Avaza, ready to be copied into your accounting tool or attached to a follow-up message for the client.

When to use it
a payment arrives in another app and you need the matching invoice to reconcile it.
Watch out
you must say which invoice you want; map its identifier from a previous module rather than typing it, or the scenario will always read the same one.
Avaza10

Get a Project

Action

In Make“Returns a specified project.”

Loads one project with its details, which lets a report or a notification show the project's real name instead of a bare number.

When to use it
a task or an invoice points to a project, and the next step needs more about it.
Watch out
despite the plural in its internal key, this module returns a single project; List Projects is the one that brings back several.
Avaza11

Get a Task

Action

In Make“Returns a specified task.”

Reads a single task so you can check where it stands before the scenario does anything else with it, such as updating or closing it.

When to use it
a scenario receives a task ID from another tool and has to decide whether to act.
Watch out
this module only reads; pair it with Update a Task when you actually want a change to land in Avaza.
Avaza12

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Avaza API to your scenario with the same connection, so you can reach any endpoint the ready-made modules leave out.

When to use it
you need something none of the other listed modules offers, such as a record type they do not cover.
Watch out
you write the request yourself, so keep Avaza's API documentation open and test every call with Run once before switching the scenario on.
Avaza13

Update a Company

Action

In Make“Updates a specified company.”

Changes an existing company in Avaza, which keeps client records aligned with what your CRM or billing tool says after an edit.

When to use it
a client's record is edited in your source tool and Avaza should follow.
Watch out
find the right company first with Get a Company or List Companies, then map its identifier here so you do not edit the wrong client.
Avaza14

Update a Task

Action

In Make“Updates a specified task.”

Edits a task that already exists, so the Avaza copy reflects what happened in the tool where the work is tracked.

When to use it
a ticket moves forward in your helpdesk and the matching Avaza task should move with it.
Watch out
the scenario needs the task's identifier; store it when Create a Task runs, or look it up with List Tasks.
Avaza15

List Companies

Search

In Make“Returns a list of companies.”

Hands you your Avaza companies one at a time. Each client travels as its own bundle through the rest of the scenario, so what follows runs once per company.

When to use it
to check whether a client already exists before Create a Company, or to export the client base to a sheet.
Watch out
a search can return zero, one or many companies, and every one that flows on uses operations, which Make counts on your plan.
Avaza16

List Contacts

Search

In Make“Returns a list of contacts.”

Brings back the people stored in Avaza, one bundle each, which is the starting point for syncing them with a mailing tool or a CRM.

When to use it
you want every contact in another system, or you need to spot one before creating it again.
Watch out
when nothing matches, zero bundles come out and the modules after it simply do not run, which can look like a silent failure.
Avaza17

List Invoices

Search

In Make“Returns a list of invoices.”

Sends back your Avaza invoices one by one, a clean base for a finance dashboard or a spreadsheet your accountant can read.

When to use it
your accountant wants invoices copied into a spreadsheet, or a monthly review needs them all in one place.
Watch out
every invoice is its own bundle. A long list therefore multiplies the operations used by each module you place after this one.
Avaza18

List Projects

Search

In Make“Returns a list of projects.”

Lists the projects in your Avaza account so a scenario can loop over them, one bundle per project, without anyone opening Avaza.

When to use it
to build a portfolio report, or to find the project a new task should belong to.
Watch out
if you need a single known project, Get a Project is lighter and avoids running the next steps once per project.
Avaza19

List Tasks

Search

In Make“Returns a list of tasks.”

Collects tasks from Avaza as individual bundles, which feeds a status report, a team digest or a check before an update.

When to use it
a manager wants open work pushed to a chat channel, or you must locate a task to edit it.
Watch out
without care the scenario acts on every returned task; test with Run once and read the bundles before letting later modules change anything.
Need help

Need help automating Avaza with Make?

A person reads every message.

FAQ

Avaza and Make: common questions

01Is the Avaza Make integration free?
Yes, on the Make side. Avaza is a standard app, so its 19 modules are available from the Free plan. That plan caps you at 2 active scenarios, a 15 minute minimum gap between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the gap to 1 minute and remove the scenario cap. Usage is counted in operations each month. You still need your own active Avaza account, whose pricing is set by Avaza.
02What do you need to connect Avaza to Make?
An active Avaza account and a personal API token. In Avaza, go to Settings, then Manage Developer Apps, then Personal Access Tokens, and copy the token. In Make, add any Avaza module, click Create a connection, optionally name it, and paste the token. The connection is saved once and every Avaza module in your scenarios reuses it, so you do this step a single time per Avaza account. If the token changes later, update it in the connection and every module follows.
03Does the Avaza Make integration react in real time?
No, because Avaza has no trigger module in Make. A scenario therefore starts from somewhere else: a trigger from another app, such as a CRM or a form tool, or Make's own schedule on the first module. With a schedule, Make runs the scenario every 15 minutes by default, and paid plans allow a gap as short as 1 minute. If the other app offers an instant trigger, the scenario starts as soon as that app calls Make.
04What if an Avaza module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Avaza API with the connection you already set up, so you are not limited to the 19 listed modules. You write the request yourself, so keep the Avaza API documentation nearby. Also note that the Make documentation for this app is marked as AI-generated and may contain mistakes, so confirm important details with Avaza before you rely on them.
05Should you use Make or n8n for Avaza?
It depends on your criteria rather than on Avaza itself. On Make, Avaza comes with 19 modules, works from the Free plan and covers companies, contacts, projects, tasks and invoices, with Make an API Call for the rest. Many apps also have an n8n node, so check whether one exists for Avaza before choosing. Compare the two tools on how your team likes to build and on what your other apps support, not on a single integration.
Same platform

Other docs you might need on this stack.

Browse all integrations