Resources · Make integration

Teamwork Make integrationAutomate Teamwork with Make.

Can Make keep Teamwork projects moving without anyone copying data by hand? Yes: the Teamwork Make integration offers 83 modules, including 25 triggers and 50 actions. This guide is for project leads new to Make: connect your account, build a first scenario, then see what each module does.

Try the Teamwork integration on MakeSee the 83 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Teamwork Make integration do for your projects?

The Teamwork Make integration links your Teamwork account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick, such as a trigger that spots a new task or an action that creates a project. You pick modules and fill in fields, nothing to code.

A project that starts ready to work. When Watch projects spots a new project, Create a task list and Create a task lay down the kickoff checklist, and Add a person to a project brings in the usual team.

Logged hours where finance reads them. Watch time entries hands each new entry to the next module as a bundle, one item moving through the scenario, so an agency can copy billable time into its spreadsheet app.

A client space for every new account. Watch companies catches the arrival of a client, Create a project opens its first project and Set project owner hands it to the account lead.

What Make does not do here: most triggers are scheduled, meaning Make checks Teamwork on the scenario's schedule, every 15 minutes by default. Only New event is instant, with Teamwork calling Make through a webhook. Every module run on one bundle is an operation, the unit Make counts on your plan (see Make pricing). When a module is missing, Make an API Call reaches the rest of the Teamwork API.

Weighing n8n as well? The n8n vs Make comparison lays out the criteria, and the Make training helps if you want guided practice.

Connect

How do you connect Teamwork to Make?

  1. 01

    Add a Teamwork module

    In a scenario, click the + and search for Teamwork. Pick any module, Watch tasks for instance, then click Create a connection. A connection is your Teamwork account linked to Make once; every Teamwork module in your scenarios reuses it.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps the day you link a second account. Then follow the window: sign in on the Teamwork page to authorize Make, or paste the key Teamwork gives you, depending on what it asks.

  3. 03

    Save and check the lists

    Click Save. Back in the module, Make can now list the projects and other objects it reads from your account, so you choose from menus instead of typing IDs. Make fills these menus through the connection, so an empty list points to it first.

First scenario

Your first scenario: a starter task list for every new project

GoalWhen a new project appears in Teamwork, Make adds a task list to it and puts a first task inside.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor. Search for Teamwork and choose Watch projects as the first module.

  2. 02

    Connect your account

    Click Create a connection and authorize Make on your Teamwork account. Watch projects is scheduled: Make looks for new projects each time the scenario runs.

  3. 03

    Add the task list

    Click the + on the right of Watch projects and add Create a task list. Point it at the project from the trigger's bundle, then name the list, Kickoff for example.

  4. 04

    Add the first task

    Add Create a task after it and map the list created by the previous module. Write the task a project lead always starts with, such as sending the welcome email to the client.

  5. 05

    Test with Run once

    Create a test project in Teamwork, then click Run once. Open the bubble above each module to read the bundles it received, and check the new list inside the project.

  6. 06

    Schedule and switch on

    Set the schedule on Watch projects, every 15 minutes by default and never below that on the Free plan, then switch the scenario on. New projects now arrive with their list.

Triggers

Which Teamwork triggers can start a scenario?

25 modules start a scenario when something happens in Teamwork. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Teamwork as soon as it happens.

Teamwork1Watch Company Events

Watch Company Events

triggerIn the docs only

Gives you a scenario that starts from company activity in Teamwork, going by the module's name. The Make documentation lists it without a description, so open it in the editor and read what it asks for before you build on it.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
your client records live in Teamwork companies and you need more than the plain arrival of a new one.
Watch out
for new companies alone, Watch companies is the documented module, so try this one with Run once first.
Teamwork2Watch companies

Watch companies

Scheduled trigger

In Make“Triggers when a new company is added.”

Hands your scenario each company added to Teamwork, one bundle per company, so a new client can set off the rest of your setup without anyone retyping its name.

How it fires
scheduled. Make looks for new companies on the scenario's schedule, not at the moment one is saved.
When to use it
a client signs and its first project, or a record in your CRM, should follow automatically.
Watch out
it reacts to additions only, so a company renamed or edited later goes unnoticed by this trigger.
Teamwork3Watch Project Events

Watch Project Events

triggerIn the docs only

Opens a scenario on project activity in Teamwork, as its name suggests. The Make documentation gives that name and nothing more, which makes the editor your only guide to its settings.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
you want to follow projects beyond their creation and have checked in the editor that the event you need is offered.
Watch out
run it once against a test project before switching it on, so you see the exact bundle it returns.
Teamwork4Watch projects

Watch projects

Scheduled trigger

In Make“Triggers when a new project is created.”

Each project created in Teamwork reaches your scenario as its own bundle, which makes this trigger the natural starting point for kickoff automation.

How it fires
scheduled. A project created between two checks arrives at the next one.
When to use it
every new project should receive the same starter task list, owner or team, as in the first scenario above.
Watch out
projects created by Make are picked up too, so never let one scenario create projects while it also watches for them, or it will feed itself.
Teamwork5Watch Task List Events

Watch Task List Events

triggerIn the docs only

Listens for task list activity inside your projects, if the name is a reliable guide, since the documentation lists this module with no description at all.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
your team organizes work in lists, one per sprint or per deliverable, and Make has to follow what happens to them.
Watch out
look at its options in the editor first; for newly added lists, Watch task lists is the documented choice.
Teamwork6Watch task lists

Watch task lists

Scheduled trigger

In Make“Triggers when a new task list is added.”

Brings every newly added task list into your scenario, so a fresh phase of a project can set things in motion in other tools.

How it fires
scheduled. Make collects the lists added since its last check, on the scenario's schedule.
When to use it
adding a list such as Design review should post a note in your team chat or open a matching card elsewhere.
Watch out
to work on the tasks of that list, add Search Tasks after it; as a search, it can return several bundles.
Teamwork7Watch Task Events

Watch Task Events

triggerIn the docs only

Tasks carry most of the daily work in Teamwork, and this module, named for task events, lets a scheduled scenario follow them. The documentation describes nothing beyond that name.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
you track task activity beyond creation and prefer a scheduled flow to the instant New event.
Watch out
a busy workspace sends many bundles, and every module run on each of them is an operation on your plan.
Teamwork8Watch tasks

Watch tasks

Scheduled trigger

In Make“Triggers when a new task is added.”

Picks up each task added to Teamwork and passes it on, one bundle at a time, ready to be copied, announced or enriched by the next module.

How it fires
scheduled. New tasks wait until the scenario's next check before they reach Make.
When to use it
tasks created in Teamwork should also appear in a support queue or a sales tool without a second entry.
Watch out
when several tasks land between two checks, they arrive as separate bundles and each one costs operations further down the scenario.
Teamwork9Watch User Events

Watch User Events

triggerIn the docs only

Follows user activity in Teamwork, if its name is any guide; the documentation lists the module and stops there, with no description of what it returns.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
an access list or staff sheet elsewhere has to stay in line with the people in your workspace.
Watch out
confirm in the editor which events it covers before trusting it with anything as sensitive as offboarding.
Teamwork10Watch people

Watch people

Scheduled trigger

In Make“Triggers when a new person (user or contact) is added.”

Each person added to Teamwork, whether a user or a contact, arrives in your scenario as a bundle you can send anywhere.

How it fires
scheduled. Make finds the people added since its last check, on the scenario's schedule.
When to use it
a new freelancer or client contact joins and should receive an account in another tool or a welcome message.
Watch out
users and contacts come through the same trigger, so read a few bundles with Run once before the next module acts on all of them.
Teamwork11Watch Milestone Event

Watch Milestone Event

triggerIn the docs only

Its name speaks of milestone events, and that is all the documentation says, so treat it as a trigger to explore in the editor before relying on it.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
deadlines drive your client reporting and Make should follow milestones after they are first set.
Watch out
for brand-new milestones only, Watch milestones does the documented job with less guesswork.
Teamwork12Watch milestones

Watch milestones

Scheduled trigger

In Make“Triggers when a new milestone is added.”

Sends each new milestone to your scenario, turning a deadline set in Teamwork into something other tools can see and act on.

How it fires
scheduled. Milestones added between two checks reach Make at the next run of the scenario.
When to use it
a client deadline added in Teamwork should also appear in a shared calendar or a status report.
Watch out
only new milestones come through, so a date moved later will not start the scenario again.
Teamwork13Watch File Events

Watch File Events

triggerIn the docs only

Aimed at file activity in Teamwork projects, judging by its name; the documentation offers no description to go further than that.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
documents go through review in Teamwork and another system has to follow each change.
Watch out
the Free plan handles files up to 5 MB, so test with a real document of the size your team usually shares.
Teamwork14Watch files

Watch files

Scheduled trigger

In Make“Triggers when a new file is uploaded.”

Every file uploaded to Teamwork becomes a bundle for your scenario, ready to be copied, filed or announced to the people who need it.

How it fires
scheduled. Uploads made between two checks are collected at the next run.
When to use it
a signed contract dropped into a project should also land in your cloud drive.
Watch out
when the next module needs the content of the file itself, place Download a file after the trigger to fetch it by its ID.
Teamwork15Watch Time Entry Events

Watch Time Entry Events

triggerIn the docs only

Time tracking activity can set off a scenario through this module, whose name is the only documentation it has in Make.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
billing depends on logged hours and you want Make to follow entries after they were first saved.
Watch out
compare its bundles with those of Watch time entries in a Run once test before you pick one of the two.
Teamwork16Watch time entries

Watch time entries

Scheduled trigger

In Make“Triggers when a new time entry is added.”

New time entries reach your scenario one by one, so logged hours can feed a draft invoice or a timesheet in another app.

How it fires
scheduled. Entries saved since the previous check come in at the next run.
When to use it
a finance team works from a spreadsheet and needs every entry there without an export.
Watch out
an entry corrected later does not come back through this trigger, because it reacts only to new ones.
Teamwork17Watch Calendar Events

Watch Calendar Events

triggerIn the docs only

Calendar events in Teamwork can start a scenario with this module, named after them and otherwise undocumented.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
client meetings are booked in the Teamwork calendar and your CRM should know about them.
Watch out
the Calendar Events group has no other trigger, so this is the one to test when you need a scenario that starts from the calendar.
Teamwork18Watch Comment Events

Watch Comment Events

triggerIn the docs only

Comment activity in Teamwork is the target of this trigger, by the look of its name; the documentation lists it without a word of description.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
client feedback arrives as comments and someone outside Teamwork has to see it.
Watch out
comments pile up fast on active projects, so watch your operations and start with a Run once test.
Teamwork20Watch Budget Events

Watch Budget Events

triggerIn the docs only

The Budgets group holds this single module, your one way to react to budgets from Make, and the documentation stops at its name.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
project spend is tracked in Teamwork budgets and finance wants a signal in its own tools.
Watch out
no other budget module exists, so reading or changing a budget from the scenario goes through Make an API Call.
Teamwork21Watch Card Events

Watch Card Events

triggerIn the docs only

Aimed at cards in Teamwork, this trigger is the only module in its group, and its documentation is limited to the name.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
your team moves work across a board and another tool should hear about it.
Watch out
Make lists no action for cards, so any follow-up inside Teamwork runs through task modules or Make an API Call.
Teamwork22Watch Column Events

Watch Column Events

triggerIn the docs only

Columns get their own trigger here, alone in its group and described by nothing but its name.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
a change of board layout, such as a new column for a workflow stage, should be noticed outside Teamwork.
Watch out
keep expectations modest until a Run once test shows you what its bundle actually holds.
Teamwork23Watch Expense Events

Watch Expense Events

triggerIn the docs only

Expense activity in Teamwork is what this trigger follows, going by the name; the Expenses group contains nothing else, so it is your only door to them.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
expenses logged against projects must also reach your accounting tool.
Watch out
Make offers no expense action for Teamwork, so writing anything back into an expense needs Make an API Call.
Teamwork24Watch Form Events

Watch Form Events

triggerIn the docs only

Teamwork forms can open a scenario through this module, the only one in the Forms group and documented by name only.

How it fires
scheduled. Make checks Teamwork on the scenario's schedule, every 15 minutes by default.
When to use it
a request form in Teamwork collects client briefs and each answer should become work somewhere else.
Watch out
send a real submission, then click Run once to see which details actually reach Make.
Teamwork25New event

New event

Instant trigger

In Make“Triggers when a new event occurs (for example, when a new task is added or completed).”

Reacts the moment something happens in Teamwork, such as a task being added or completed, instead of waiting for the next check.

How it fires
instant. Teamwork calls Make through a webhook as soon as it happens; Make creates and attaches that webhook for you, with no extra setup.
When to use it
a completed task must reach a client or a teammate straight away.
Watch out
you select the event type when you add the module, and that choice decides everything the scenario will receive.
Modules

What each Teamwork module does

Teamwork gives you 58 modules in 12 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Companies

4 modules
Teamwork1

Create a company

Action

In Make“Creates a new company.”

Adds a new company to Teamwork, so a client won in another tool gets its record without anyone retyping the name or details.

When to use it
a deal closes in your CRM and the account must exist in Teamwork before its first project is opened.
Watch out
the module creates a company every time it runs, so a scenario that fires twice leaves you with a duplicate.
Teamwork2

Update a Company

ActionIn the docs only

Keeps a company record in Teamwork aligned with the tool where your client details are really maintained, by editing the existing entry.

When to use it
a client changes its name or address in your CRM and Teamwork should follow.
Watch out
the documentation lists this module without a description; you need the company to change, usually from Watch companies or Get a company.
Teamwork3

Get a company

Action

In Make“Retrieves information about a company with a given ID.”

Fetches one company from Teamwork by its ID and hands its details to the next module in a single bundle.

When to use it
a project bundle points to a client and you need that client's full record before writing to your invoicing tool.
Watch out
it works from an ID only and does not search by name, so the ID must come from an earlier module.
Teamwork4

Delete a company

Action

In Make“Deletes a company with a given ID.”

Removes a company from Teamwork by its ID, clearing out a client you no longer work with.

When to use it
an account is closed in your CRM and should disappear from Teamwork at the same time.
Watch out
assume nothing in Make can undo it; try the module on a dummy company before pointing it at real clients.

Projects

9 modules
Teamwork5

Create a project

Action

In Make“Creates a new project.”

Opens a new project in Teamwork from data held elsewhere, such as a signed quote or a company just added.

When to use it
each signed deal deserves a project built the same way, without a project lead copying details across.
Watch out
if Watch projects runs in another scenario, the project created here will set that scenario off too, which is fine as long as it is intended.
Teamwork6

Update a project

Action

In Make“Updates a project with a given ID.”

Edits a project chosen by its ID, so it stays in line with decisions taken outside Teamwork.

When to use it
a contract amendment recorded in your CRM should be reflected on the matching project straight after.
Watch out
the ID must come from an earlier module, Watch projects or Get a project for example; a wrong mapping edits the wrong project.
Teamwork7

Update a Project Health

ActionIn the docs only

Changes the health shown on a Teamwork project, going by the module's name, since the documentation gives nothing more.

When to use it
a score worked out in another tool, from budget use or missed deadlines, should show up on the project for everyone to see.
Watch out
run it once on a test project to see which health values Make proposes before wiring it to real data.
Teamwork8

Set project owner

Action

In Make“Sets a selected person as a project owner.”

Makes a chosen person the owner of a project, so responsibility is clear from the first day.

When to use it
right after Create a project, to hand the new project to the account manager named on the deal.
Watch out
the person has to exist in Teamwork already; for a newcomer, place Create a person earlier in the scenario.
Teamwork9

Add a person to a project

Action

In Make“Adds a selected person to a project.”

Brings a person onto a project team without anyone sending a manual invite from Teamwork.

When to use it
every new project needs the same designer and developer, or the client contact should join as soon as the project exists.
Watch out
one run of the module adds one person, so a whole team means several modules in a row, each costing an operation.
Teamwork10

Remove a person from a project

Action

In Make“Removes a selected person from a project.”

Takes a person off a project, which keeps teams tidy when roles change or a mission ends.

When to use it
a freelancer's contract ends in your HR tool and their project access should end with it.
Watch out
the person stays in Teamwork after this; use Delete a person only if they must leave the account altogether.
Teamwork11

Get a project

Action

In Make“Retrieve information about a project with a given ID.”

Returns the full record of one project from its ID, useful when the next module needs more than the project's name.

When to use it
a time entry or a task arrives and your report needs details about the project it belongs to.
Watch out
no ID, no result; map it from a previous bundle rather than typing it, or the scenario will always read the same project.
Teamwork12

Get Project Templates

ActionIn the docs only

Retrieves the project templates set up in your Teamwork account, judging by the module's name; the documentation adds no description.

When to use it
you want to see which templates exist before building a scenario that should start projects from one of them.
Watch out
the output is undocumented, so click Run once and read the bundles before mapping anything from them.
Teamwork13

Delete a project

Action

In Make“Deletes a project with a given ID.”

Deletes a project by its ID, for flows that clean up tests or work that was cancelled.

When to use it
a deal is lost after its project had already been created automatically.
Watch out
nothing in the scenario can bring the project back, so keep this module behind a clear condition such as a deal marked as lost.

Task Lists

4 modules
Teamwork14

Create a task list

Action

In Make“Creates a new task list in a specified project.”

Creates a task list inside a project you choose, giving a phase or a deliverable its own place to collect tasks.

When to use it
a new project should start with a Kickoff list, exactly as in the first scenario of this guide.
Watch out
the project must exist first; map it from Watch projects or from Create a project placed just before.
Teamwork15

Get a task list

Action

In Make“Retrieves information about a task list with a given ID.”

Reads one task list by its ID and passes its details along, so later modules can quote its name or its project.

When to use it
a new task comes in and the notification you send should say which list it belongs to.
Watch out
when you only know the name of the list, Search Task Lists is the better fit.
Teamwork16

Search Task Lists

SearchIn the docs only

Looks for task lists and can return none, one or many, each as its own bundle for the modules that follow.

When to use it
you know a list's name but not its ID, for example to drop new tasks into Kickoff.
Watch out
the documentation gives no description, so run it once to see how it filters, and remember that every result runs the next modules again.
Teamwork17

Delete a task list

Action

In Make“Deletes a task with a given ID.”

Removes a task list from a project, for layouts that no longer need a given phase.

When to use it
a list created from a standard setup does not apply to a small project and should go.
Watch out
the official description speaks of deleting a task, not a list, so test on a spare list to see exactly what is removed.

Tasks

7 modules
Teamwork18

Create a task

Action

In Make“Adds a new task to a specified task list.”

Adds a task to a task list you pick, turning a request from another tool into work someone can take on.

When to use it
a support ticket or a form answer should become a task in the right list without a copy and paste.
Watch out
the list has to be known first; Search Task Lists finds it by name when no earlier module provides it.
Teamwork19

Create a subtask

Action

In Make“Adds a new subtask to a selected task.”

Breaks a large item into steps by adding a subtask under a task you select.

When to use it
each new onboarding task should carry the same three checks underneath, so nobody forgets them.
Watch out
the parent task must exist; map it from Watch tasks or from Create a task placed just before this module.
Teamwork20

Update a task

Action

In Make“Modifies information about a task with a specified ID.”

Changes a task identified by its ID, keeping Teamwork in step with what moved in another tool.

When to use it
a client edits a request in your form tool and the matching task should show the new version.
Watch out
store the task ID in the other tool when the task is created, or Make will have no way to find it later.
Teamwork21

Complete a task

Action

In Make“Markes the specified task as complete.”

Marks a task as done without anyone opening Teamwork, so boards reflect what really happened elsewhere.

When to use it
an invoice is paid or a document is signed in another app, and the matching task can close itself.
Watch out
it closes whatever task the ID points to; a wrong mapping closes the wrong one, so check it with Run once.
Teamwork22

Get a task

Action

In Make“Retrieves information about a task with a given ID.”

Pulls the full record of a task from its ID, ready for a message, a report or a copy in another app.

When to use it
New event tells you a task changed and you need its current content before acting on it.
Watch out
it reads one task you already know; when you have to find tasks first, Search Tasks returns them as a list.
Teamwork23

Search Tasks

SearchIn the docs only

Finds tasks and returns each match as a separate bundle, whether there are none, one or many.

When to use it
before creating a task, to check that the same request is not already waiting in Teamwork.
Watch out
its settings are undocumented, so test it first, and remember that the modules placed after it run once per result.
Teamwork24

Delete a task

Action

In Make“Deletes a task with a given ID.”

Deletes one task by its ID, for flows that mirror a cancellation made in another tool.

When to use it
a request is withdrawn in the tool that created the task, and the task should not linger in Teamwork.
Watch out
treat the deletion as final; a test task is the safe way to try the module before real data flows through.

People

5 modules
Teamwork25

Create a person

Action

In Make“Creates a new person.”

Creates a person in Teamwork, teammate or client contact, from data held in another tool.

When to use it
a new hire appears in your HR system and needs a Teamwork profile before joining projects.
Watch out
it creates a person even if one already exists, so run Search People first to avoid duplicates.
Teamwork26

Update a person

Action

In Make“Updates a person with a given ID.”

Updates a person picked by ID, so the same details show in Teamwork and in the tool your team treats as the reference.

When to use it
an employee's details change in the HR system and Teamwork should catch up.
Watch out
when you only know the person's name, find the ID with Search People placed before this module.
Teamwork27

Get a person

Action

In Make“Retrieves information about a person with a given ID.”

Returns one person's record from its ID, so a message or report can use their details.

When to use it
a task or time entry points to someone and the next module needs more than an ID to address them.
Watch out
it only works with an ID; for a lookup by name, Search People is the module to add.
Teamwork28

Search People

SearchIn the docs only

Searches the people in your Teamwork account and hands back every match as its own bundle.

When to use it
checking whether a contact already exists before Create a person adds a new one.
Watch out
several matches mean the following modules run several times, each costing operations, so test the search with Run once.
Teamwork29

Delete a person

Action

In Make“Deletes a person with a given ID.”

Deletes a person from Teamwork by ID, closing the loop when someone leaves the organization.

When to use it
offboarding, once a departure is recorded in your HR tool and the account has to go.
Watch out
to take someone off a single project, Remove a person from a project is the gentler choice.

Milestones

5 modules
Teamwork30

Create a milestone

Action

In Make“Creates a new milestone.”

Creates a milestone in Teamwork from an event in another tool, so key dates show up where the team plans its work.

When to use it
a contract sets a delivery date and the project should display it as soon as the contract is signed.
Watch out
a scenario built on Watch milestones will pick this one up too, so avoid chaining the two in the same flow.
Teamwork31

Update a Milestone

ActionIn the docs only

Adjusts an existing milestone, going by its name, since the documentation provides no description.

When to use it
a delivery date moves in the client's contract and the project should show the new one.
Watch out
Watch milestones reacts only to new milestones, so this change will not start a scenario built on that trigger.
Teamwork32

Get a milestone

Action

In Make“Retrieves information about a milestone with a given ID.”

Reads a milestone by ID and passes its details on, ready to be quoted in an email or a report.

When to use it
preparing a client update that names the next deadline of a project.
Watch out
to gather several milestones at once, Search Milestones returns them as separate bundles instead.
Teamwork33

Search Milestones

SearchIn the docs only

Finds milestones and returns zero, one or many results, each one travelling on as a bundle.

When to use it
building a digest of upcoming deadlines across several projects for a steering meeting.
Watch out
the documentation says nothing about its settings, so check them in the editor and test before you rely on the results.
Teamwork34

Delete a milestone

Action

In Make“Deletes a milestone with a given ID.”

Removes a milestone by its ID when a phase no longer belongs in the plan.

When to use it
a phase is dropped from the contract and its deadline should vanish from the project too.
Watch out
run it on a test milestone first, because a wrong ID deletes a real deadline with no way back from Make.

Files

3 modules
Teamwork35

Upload a file

Action

In Make“Uploads a file into a specific project.”

Puts a file into the Teamwork project you choose, straight from a previous module that produced or fetched it.

When to use it
a signed PDF from your e-signature tool belongs in the client's project with the rest of the paperwork.
Watch out
the Free plan handles files up to 5 MB, so check the size of your deliverables before counting on the scenario.
Teamwork36

Download a file

Action

In Make“Downloads a file with a given ID.”

Fetches a Teamwork file by its ID so a later module can store it, attach it or send it on.

When to use it
files added to a project should also be archived in your cloud drive, right after Watch files spots them.
Watch out
each download counts toward your data transfer, which is 512 MB on the Free plan.
Teamwork37

Delete a file

Action

In Make“Deletes a file with a given ID.”

Deletes a file by its ID, keeping projects free of outdated versions.

When to use it
a document was replaced by a newer version and the old one should not confuse the client.
Watch out
keep a copy with Download a file first whenever there is a chance you will need the old version again.

Time Entries

5 modules
Teamwork38

Create a time entry

Action

In Make“Adds a new time entry to a given project or task.”

Logs time against a project or a task in Teamwork, so hours recorded somewhere else still count in your reports.

When to use it
your team tracks time in a separate timer app and Teamwork should hold the totals for billing.
Watch out
choose between project and task on purpose, since an entry filed on the wrong one skews every report built on it.
Teamwork39

Update a Time Entry

ActionIn the docs only

Corrects an existing time entry, going by the module's name; the documentation stays silent beyond that.

When to use it
a timesheet is fixed in the source tool after review and Teamwork should carry the corrected figure.
Watch out
Watch time entries will not see the correction, because it reacts only to entries that are new.
Teamwork40

Get a time entry

Action

In Make“Returns a time entry by ID.”

Returns one time entry by its ID, with the details a billing or payroll step needs.

When to use it
a report or an invoice line has to show the exact entry behind a charge you already know about.
Watch out
it reads a single entry; to collect many entries, Search Time Entries is the module to reach for.
Teamwork41

Search Time Entries

SearchIn the docs only

Pulls the hours logged in Teamwork into your scenario, so a report, a sheet or an invoice draft can be built from them. As a search, it may return zero, one or many entries, and each one travels as its own bundle.

When to use it
a project closes and you want every hour booked against it gathered in one place.
Watch out
each returned entry makes the following modules run once more, and every run counts as an operation on your plan.
Teamwork42

Delete a Time Entry

ActionIn the docs only

Removes a logged block of hours from Teamwork, which keeps timesheets clean when a booking was made by mistake or duplicated by another tool. Map the entry from an earlier module rather than typing it by hand.

When to use it
a time entry was pushed twice by a sync and the copy has to go.
Watch out
a deletion cannot be undone from Make, so test it with Run once on a dummy entry first.

Calendar Events

5 modules
Teamwork43

Create a calendar event

Action

In Make“Creates a new calendar event.”

Puts a new event on the Teamwork calendar without anyone opening the app, so kickoffs and reviews show up where the team already looks. Fill the event from data that an earlier module in the scenario brought in.

When to use it
a deal is signed in your CRM and the kickoff meeting should appear in Teamwork straight away.
Watch out
if the scenario runs twice on the same record, you get two events, so check the trigger before switching it on.
Teamwork44

Update a Calendar Event

ActionIn the docs only

Changes an event that already sits on the Teamwork calendar, which saves the team from chasing a moved meeting by hand. It edits the existing item instead of adding a second one next to it.

When to use it
a client reschedules in another tool and the Teamwork event has to follow.
Watch out
the module needs to know which event to touch; find it first with Search Calendar Events or map it from the trigger.
Teamwork45

Get a Calendar Event

ActionIn the docs only

Reads one calendar event and hands its details to the next modules, so a reminder email or a message can quote the right title and time. Nothing changes in Teamwork: it only fetches.

When to use it
a trigger only gives you a reference to the event and you need its full content downstream.
Watch out
it returns a single event; to look through several, pick Search Calendar Events instead.
Teamwork46

Search Calendar Events

SearchIn the docs only

Looks through the Teamwork calendar and returns the matching events, ready to be copied, listed or checked by the rest of the scenario. The result can be empty, a single event or a whole batch of bundles.

When to use it
before creating an event, to see whether the same meeting already exists and avoid a duplicate.
Watch out
when nothing matches, no bundle comes out and the modules after it simply do not run for that search.
Teamwork47

Delete a calendar event

Action

In Make“Deletes a calendar event.”

Takes an event off the Teamwork calendar so a cancelled meeting stops cluttering everyone's week. Pair it with a trigger from the tool where cancellations actually happen.

When to use it
a booking is cancelled on the client side and the matching Teamwork event should vanish too.
Watch out
Make has no undo for this, and a wrong mapping removes the wrong event; run it once on a test event before activating the scenario.

Comments

5 modules
Teamwork48

Create a Comment

ActionIn the docs only

Posts a comment in Teamwork from the scenario, so updates coming from other tools land in the conversation the team already follows. The text can mix fixed words with data mapped from earlier modules.

When to use it
a payment is received or a form answered, and the people on the task should read it without leaving Teamwork.
Watch out
a comment is written on every run, so a noisy trigger turns into a noisy thread.
Teamwork49

Update a Comment

ActionIn the docs only

Rewrites a comment that the scenario, or someone, already posted, handy for a status line that should stay single and current instead of stacking up. The thread keeps one message that changes over time.

When to use it
a progress note posted earlier needs its figures refreshed after a new sync.
Watch out
you must point it at the exact comment, so keep track of it from Create a Comment or find it with Search Comments.
Teamwork50

Get a Comment

ActionIn the docs only

Fetches the content of one comment and makes it available to the next modules, for instance to forward it to a chat channel or store it in a sheet. It reads and leaves Teamwork untouched.

When to use it
the comment trigger fires and you want the full text before deciding where it goes.
Watch out
it handles a single comment; for a set of them, Search Comments is the better brick.
Teamwork51

Search Comments

SearchIn the docs only

Gathers the Teamwork comments that match what you ask for, which turns scattered discussion into material for a recap or an archive. Expect zero, one or many bundles, each carrying one comment.

When to use it
a task is closed and its discussion should be copied into the client file.
Watch out
a long thread means many bundles, and each bundle costs an operation in every module that follows.
Teamwork52

Delete a Comment

ActionIn the docs only

Erases a comment in Teamwork, useful when an automated message went out with the wrong content and should disappear from the thread. Map the comment from the module that created or found it.

When to use it
a scenario posted a note by mistake and you want a clean-up step that removes it.
Watch out
once gone, the comment is not recoverable from Make; test the mapping with Run once on a throwaway comment.

Links

5 modules

Other

1 module

This app uses webhooks to trigger a Make when an event occurs instantly. All webhook modules have an instant tag next to their name. When you create a Teamwork webhook in Make, it is attached automatically and requires no additional set up. Select the type of the event that you want to watch and enjoy working with trigger modules.

Teamwork58

Make an API Call

ActionIn the docs only

Opens the whole Teamwork API from inside your scenario, with the connection you already set up. Any endpoint can be called, so a need that none of the listed modules covers still has a way in.

When to use it
you need data about budgets, expenses or forms beyond what the watch triggers deliver.
Watch out
you build the request yourself from the Teamwork API documentation, which asks for more care than a ready-made module.
Need help

Need help automating Teamwork with Make?

A person reads every message.

FAQ

Teamwork and Make: common questions

01Is the Teamwork Make integration free?
Yes, Teamwork is a standard app in Make, so its modules work on the Free plan. That plan allows 2 active scenarios, runs them no more often than every 15 minutes, stops each run after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes per run. Make counts usage in operations, one per module and per bundle. Your Teamwork subscription is a separate matter.
02What do you need to connect Teamwork to Make?
A Teamwork account and a Make account; the Make documentation lists no other prerequisite. Add any Teamwork module, click Create a connection, name it if you wish, then authorize Make on the Teamwork page or paste the key Teamwork provides, and save. The connection is stored once and reused by every Teamwork module in all your scenarios, so the next scenario starts with nothing to repeat. Make fills module menus through that connection, so if they stay empty afterwards, reopen it and authorize again.
03Do Teamwork triggers in Make fire in real time?
Only one of them does. New event is instant: Teamwork calls Make through a webhook as soon as the chosen event happens, and Make attaches that webhook for you. All the other triggers are scheduled, which means Make checks Teamwork on the scenario's schedule, every 15 minutes by default. On the Free plan the interval cannot go below 15 minutes; paid plans allow 1 minute. Build on New event when a change must reach the scenario at once, and on a scheduled watcher when a short delay does no harm.
04What if a Teamwork module is missing in Make?
Use Make an API Call. It calls any endpoint of the Teamwork API from your scenario with the connection you already have, so you are not stuck when the 83 listed modules stop short of your need, for budgets, cards or expenses for instance. You choose the endpoint from the Teamwork API documentation and read the answer in the next module like any other bundle. It asks for more care than a ready module, because you write the request yourself. The Make documentation lists no further limit for Teamwork.
05Make or n8n for Teamwork?
It depends on your team and on the tool your other automations already use. On the Make side the facts are clear: 83 Teamwork modules, 25 triggers of which one is instant, no code to write, and Make an API Call for the gaps. n8n often offers a node for the same app, so look at its catalog before choosing. Neither tool is ranked here; compare how each one handles the triggers you need and how usage is counted. The comparison page linked earlier in this guide walks through those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations