Resources · Make integration

TeamWave Make integrationAutomate TeamWave with Make.

Can TeamWave stay up to date while your other apps feed it? The TeamWave Make integration gives you 27 modules, 18 actions and 9 searches, across deals, contacts, companies and projects. This page walks sales and project teams from the connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TeamWave Make integration do for you?

The TeamWave Make integration lets Make write to and read from your TeamWave account without code. You build a scenario, the automation itself, from modules: each module is one brick that creates, updates, deletes or looks up a deal, a contact, a company or a piece of a project.

Leads that reach the CRM on their own. A form or a webinar tool collects a name, Search for Persons checks whether TeamWave already knows it, then Create a Person and Create a Deal open the record and the opportunity. Sales starts from a clean pipeline instead of a pile of emails.

Projects that start the day an order is paid. Your shop or billing app confirms the sale, Create a Project sets up the delivery space, and Create a Task in a Project with Create a Milestone lay out the first steps for the team.

Contacts that stay current. When someone changes details in another tool, Update a Person or Update an Organization repeats the change in TeamWave, and Delete a Person handles removal requests.

What Make does not do here: TeamWave has no trigger module, so a scenario starts from another app or from a schedule. There is also no module to read a single deal, which is where Make an API Call helps. The Make documentation for TeamWave says it was generated with AI, so double-check anything critical with TeamWave. Before you pick a tool, the Make review and the n8n vs Make comparison give the wider picture, and the Make pricing page explains the plans.

Connect

How do you connect TeamWave to Make?

  1. 01

    Add a TeamWave module

    In your scenario, search for TeamWave, pick any of its modules and click Create a connection. A connection is your TeamWave account linked to Make once; every TeamWave module you add later reuses it.

  2. 02

    Copy your API key

    In TeamWave, click the Profile icon in the top right corner, choose Settings, then open the API Keys section in the left menu and copy the key displayed on screen.

  3. 03

    Name and save the connection

    Back in Make, type a name in Connection name if you want to recognize it later (the field is optional), paste the API key and save. Make can now read and write in your TeamWave account.

First scenario

Build your first scenario with TeamWave

GoalWhen a new lead arrives in another app, Make adds the person to TeamWave and opens a deal for them.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to place the first module. Choose the app where your leads land, such as your form tool: TeamWave has no trigger, so the start comes from there.

  2. 02

    Add Create a Person

    Click the + on the right of that first module, search for TeamWave and pick Create a Person. Click Create a connection and paste your API key if you have not done it yet.

  3. 03

    Map the lead to the contact

    Fill the fields of Create a Person with data from the first module. Each lead travels as one bundle, a single item passed from module to module, and each bundle becomes one contact.

  4. 04

    Open the deal

    Add Create a Deal with the + on the right, keep the same connection and map the lead details again, so the new deal tells your sales team who the prospect is and where they came from.

  5. 05

    Test with Run once

    Click Run once, send a test lead through your form, then read the bundles each module received. Open TeamWave and check that both the person and the deal are there.

  6. 06

    Schedule and switch it on

    Check the clock on the first module (a new scenario runs every 15 minutes by default) and switch the scenario on. Each new lead now reaches TeamWave without copy and paste.

Modules

What each TeamWave module does

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

TeamWave1

Create a Deal

Action

In Make“Creates a deal.”

Create a Deal opens a new sales opportunity in TeamWave from data another app sends, so your pipeline fills itself instead of waiting for someone to retype a lead.

When to use it
a quote request lands in your form tool and sales should see it as a deal straight away.
Watch out
Make offers no module to look up deals, so keep the result of this step if a later module has to update the same deal.
TeamWave2

Create a Milestone

Action

In Make“Creates a milestone in a project.”

Create a Milestone adds a checkpoint to an existing TeamWave project, which gives the team a visible stage to aim for without opening the project by hand.

When to use it
a contract gets signed in another tool and the delivery phase needs its first marker inside the project.
Watch out
the milestone belongs to a project, so identify that project first; List Projects helps when you only know its name.
TeamWave3

Create an Event in a Project

Action

In Make“Creates an event in a project.”

Create an Event in a Project puts a kickoff, a review or a client call on a TeamWave project, right where the project team already looks for what is coming.

When to use it
a meeting gets booked in your scheduling app and the project should keep a trace of it.
Watch out
the module works inside one project, so have that project identified in an earlier step before this one runs.
TeamWave4

Create an Organization

Action

In Make“Creates an organization.”

Create an Organization records a new company in your TeamWave CRM, giving the account one record your whole team can find and build on.

When to use it
a new customer signs up in your billing tool and should appear as a company in TeamWave.
Watch out
run Get an Organization or List All Organizations first when the company may already exist, which keeps the CRM free of doubles.
TeamWave5

Create a Person

Action

In Make“Creates a person.”

Create a Person adds a contact to TeamWave, so every name collected by a form, a webinar tool or a spreadsheet becomes someone your sales team can actually call.

When to use it
each new sign-up in another app should turn into a TeamWave contact without copy and paste.
Watch out
place Search for Persons before it and skip the creation when the search already returns that contact.
TeamWave6

Create a Project

Action

In Make“Creates a project.”

Create a Project spins up a fresh TeamWave project the moment the scenario decides work should begin, which saves setting it up by hand for every new client.

When to use it
an order is paid in your online store and delivery needs its own project.
Watch out
tasks, events and milestones come after; add those modules next and map the new project from this step into them.
TeamWave7

Create a Task in a Project

Action

In Make“Creates a task in a project.”

Create a Task in a Project drops a to-do into a TeamWave project, so a request that arrives by email or form turns into work the team sees instead of a forgotten message.

When to use it
a client asks for a change through a support form and the project team should pick it up from its list.
Watch out
the task needs its project; if the scenario only knows the project name, List Projects can find it first.
TeamWave8

Delete a Deal

Action

In Make“Deletes a deal.”

Delete a Deal removes a deal from TeamWave, which keeps your pipeline honest when an opportunity was created by mistake or cancelled in another system.

When to use it
a test entry or a duplicate slipped in, and another tool already flags it as void.
Watch out
treat every deletion as final and try it with Run once on a dummy deal before you switch the scenario on.
TeamWave9

Delete a Milestone

Action

In Make“Deletes a milestone in a project.”

Delete a Milestone takes a checkpoint out of a TeamWave project, so a plan that changed elsewhere no longer shows a stage nobody works toward.

When to use it
a phase is dropped from the contract and the project in TeamWave should say the same.
Watch out
List Milestones in a Project gives you the exact milestone to target; a guess can remove the wrong one.
TeamWave10

Delete an Event

Action

In Make“Deletes an event.”

Delete an Event clears an event from TeamWave, which stops the team from preparing for a meeting that was already cancelled somewhere else.

When to use it
a booking gets cancelled in your scheduling app and the matching TeamWave event should disappear with it.
Watch out
List Project Events can return many events, so make sure the scenario passes only the cancelled one to this module.
TeamWave11

Delete an Organization

Action

In Make“Deletes an organization.”

Delete an Organization removes a company record from your TeamWave CRM, useful when you clean up accounts created twice or that never belonged there.

When to use it
a data cleanup in another tool marks a company as a duplicate or as spam.
Watch out
confirm with Get an Organization that you hold the right record, then consider the deletion permanent.
TeamWave12

Delete a Person

Action

In Make“Deletes a person.”

Delete a Person erases a contact from TeamWave, so someone who asked to be removed from your lists no longer sits in the CRM either.

When to use it
a removal request reaches your email tool and TeamWave should follow the same decision.
Watch out
Search for Persons can return several people, so check that the scenario deletes only the one contact you mean.
TeamWave13

Delete a Task in a Project

Action

In Make“Deletes a task in a project.”

Delete a Task in a Project removes a to-do from a TeamWave project, which keeps task lists clean when a request is withdrawn before anyone starts on it.

When to use it
a ticket is closed as not needed in your helpdesk and the matching task should go too.
Watch out
Get a Task in a Project confirms the target first; without it, a wrong mapping can remove live work.
TeamWave14

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the TeamWave API with the connection you already set up, which covers whatever the other modules on this page leave out.

When to use it
you need to read a single deal, since no Get module exists for deals, or any other TeamWave action missing from the list.
Watch out
you describe the request yourself, so keep the TeamWave API documentation open while you build it.
TeamWave15

Update a Deal

Action

In Make“Updates a deal.”

Update a Deal changes an existing deal in TeamWave, so the pipeline follows what happens in your other tools, like a quote that was signed or a budget that moved.

When to use it
your e-signature app confirms a step and the deal should reflect it without anyone touching the CRM.
Watch out
there is no deal search module, so reuse the deal from the step that created it or fetch it with Make an API Call.
TeamWave16

Update an Organization

Action

In Make“Updates an organization.”

Update an Organization keeps a company record in TeamWave current when its details change in another system, such as your invoicing tool.

When to use it
a customer edits its company details in the billing portal and sales should see the same thing in TeamWave.
Watch out
locate the record first with Get an Organization or List All Organizations; an update needs a company that already exists.
TeamWave17

Update a Person

Action

In Make“Updates a person.”

Update a Person refreshes a TeamWave contact with what you learned elsewhere, so the next call starts from current information instead of an old note.

When to use it
someone changes jobs or contact details through a form and the CRM should match.
Watch out
run Search for Persons or Get a Person before it, so the change lands on the right contact and not on a namesake.
TeamWave18

Update a Task in a Project

Action

In Make“Updates a task in a project.”

Update a Task in a Project edits a to-do that already sits in a TeamWave project, letting another tool report progress without a teammate retyping it.

When to use it
a client approves a draft in your proofing tool and the task should show that step is done.
Watch out
Get a Task in a Project gives you the current task before you change it, which helps when only part of it should move.
TeamWave19

Get an Organization

Search

In Make“Gets an organization.”

Get an Organization fetches one company record from TeamWave so later modules can reuse its details in an email, an invoice or a report.

When to use it
you already know which company you want and need its data in the middle of a scenario.
Watch out
as a search module it can come back empty; decide what the scenario should do when no company matches.
TeamWave20

Get a Person

Search

In Make“Gets a person.”

Get a Person pulls one TeamWave contact into your scenario, ready to personalize a message or fill a document with that person's details.

When to use it
an earlier step already identified the contact and you need the full record before writing to them.
Watch out
to look someone up from partial information, such as a name typed in a form, Search for Persons is the better starting point.
TeamWave21

Get a Task in a Project

Search

In Make“Gets a task in a project.”

Get a Task in a Project reads one task from a TeamWave project, so a scenario can check where the work stands before it sends an update or changes anything.

When to use it
a client asks for status in your helpdesk and the reply should quote the task as it is now.
Watch out
it needs both the project and the task; List Task Groups helps you find the task when you only have the project.
TeamWave22

List All Organizations

Search

In Make“Show list of all organizations.”

List All Organizations returns the companies stored in TeamWave, one bundle per company, which is the base for mirroring your CRM in a spreadsheet or another tool.

When to use it
you want every account copied into a sheet, or a batch of companies checked against another list.
Watch out
every module after it runs once per company, and each run counts as an operation on your Make plan.
TeamWave23

List Milestones in a Project

Search

In Make“Lists milestones in a project.”

List Milestones in a Project brings back the checkpoints of one TeamWave project, so a scenario can share progress with a client or a manager without a status meeting.

When to use it
a client asks where the project stands and the answer should come straight from TeamWave.
Watch out
a young project may return nothing yet, so decide what the next module does with an empty result.
TeamWave24

List Project Events

Search

In Make“Show project events.”

List Project Events collects the events of a TeamWave project, handy for copying them into another calendar or summarizing what is planned for the team.

When to use it
a project manager wants the project meetings mirrored in the calendar the client already uses.
Watch out
before chaining it to Delete an Event, narrow the result down, since a list rarely holds only the event you mean.
TeamWave25

List Projects

Search

In Make“Show list of all projects.”

List Projects returns your TeamWave projects so a scenario can find the right one by name or handle each of them in turn.

When to use it
you only know a project's name from another app and need the project itself to create a task or an event.
Watch out
on a busy account the list gets long, and every project that passes through counts as operations in the modules downstream.
TeamWave26

List Task Groups

Search

In Make“Show all tasks for project.”

List Task Groups gathers the tasks of a TeamWave project, giving the scenario a full view of the work before it reports on it, cleans it up or updates it.

When to use it
you want a status digest sent to your team chat after a change in another tool.
Watch out
the module name speaks of task groups while the official description speaks of all tasks for a project, so click Run once and read the bundles to see what it returns.
TeamWave27

Search for Persons

Search

In Make“Searchs for persons.”

Search for Persons looks up the TeamWave contacts that match what your scenario knows, the step that prevents duplicate records before any creation.

When to use it
a new lead arrives and you want to know whether TeamWave already has that person.
Watch out
the result can hold zero, one or several people; decide what happens in each case before you create or update anything.
Need help

Need help automating TeamWave with Make?

A person reads every message.

FAQ

TeamWave and Make: common questions

01Is the TeamWave Make integration free?
Yes, on the Make side. TeamWave is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, scheduled runs no closer than every 15 minutes, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in credits each month. Your TeamWave subscription is a separate matter: you need an active account there to get an API key, and TeamWave sets its own price.
02What do you need to connect TeamWave to Make?
An active TeamWave account and its API key. In TeamWave, open the Profile icon in the top right corner, pick Settings, go to the API Keys section in the left menu and copy the key. In Make, add any TeamWave module, click Create a connection, give it a name if you like, paste the key and save. That single connection then serves all 27 modules, so you never repeat the step for each action or search you add later on the same account.
03Does TeamWave trigger Make scenarios in real time?
No, because TeamWave has no trigger module in Make: all 27 modules are actions or searches. A scenario therefore starts somewhere else. Either another app opens it with its own trigger, such as a form that receives a lead, or Make launches it on a schedule, every 15 minutes by default for a new scenario, with 15 minutes as the shortest interval on the Free plan and 1 minute on paid plans. With a schedule, a search like List Projects or Search for Persons usually comes first to pick what the next action should process.
04What if the TeamWave module you need is missing in Make?
Use Make an API Call. It sends any request the TeamWave API accepts, with the same connection as the other modules, which fills gaps such as reading a single deal: Make lists Create, Update and Delete for deals but no Get. You describe the request yourself, so the TeamWave API documentation becomes your guide. Keep in mind that the Make documentation for TeamWave is marked as AI-generated and may contain mistakes, so confirm anything critical with TeamWave directly before you rely on it.
05Should you use Make or n8n for TeamWave?
It depends on where your other automations already live. On Make, TeamWave comes with 27 ready modules plus Make an API Call, and it runs from the Free plan, so a first scenario costs nothing to try. Many apps also have an n8n node, so check whether TeamWave has one before you decide. Neither tool is ranked here: the comparison page linked above sets out how each one works, and the practical choice usually follows the tool your team already runs and maintains.