Resources · Make integration

Teamwork Desk Make integrationAutomate Teamwork Desk with Make.

Can Make handle your Teamwork Desk tickets without a line of code? The Teamwork Desk Make integration offers 30 modules, including an instant trigger. This page shows how to connect your account, build a first scenario and pick the right module for each job.

Try the Teamwork Desk integration on MakeSee the 30 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Teamwork Desk Make integration do for you?

The Teamwork Desk Make integration links your help desk to your other tools without code. In Make, you build a scenario (the automation itself, a chain of modules) that reacts to a Teamwork Desk event, creates tickets and customers, or keeps your help center articles up to date.

Tickets from anywhere. A form or a chat tool starts the scenario, Create Customer records the person and Create Ticket opens the request, so no question gets stuck in someone's personal mailbox.

Alerts with context. Watch Events fires as soon as a ticket arrives, Get Ticket and Get Customer add the details, and your team channel receives a message people can act on without opening the help desk.

A help center that follows the product. List Articles walks through a category, then Update Article or Delete Article keeps each page in line with what you actually sell.

The list has gaps: no module creates an article or reads a single category, and the Teamwork Desk documentation on the Make side states that it is AI-generated and may contain mistakes. Make an API Call covers the missing pieces when the Teamwork Desk API offers them. Many apps also have an n8n node, and n8n vs Make sets out how to choose. To learn the editor step by step, open Make training; when a run fails, Make troubleshooting helps you read the error.

Connect

How do you connect Teamwork Desk to Make?

  1. 01

    Create an API key in Teamwork Desk

    Click your profile icon at the top right, choose View Profile, open the API Keys tab and click Create an API key. Pick the key type in the dropdown, then copy the key shown on screen.

  2. 02

    Open a connection in Make

    Add any Teamwork Desk module to your scenario and click Create a connection. A connection is your Teamwork Desk account linked to Make once. The Connection name field is optional, yet a clear name helps if you link several accounts.

  3. 03

    Paste the key and confirm

    Paste the credentials you copied from Teamwork Desk, or follow the on-screen instructions, and save. From now on every Teamwork Desk module in your scenarios reuses this connection, so you never paste the key twice.

First scenario

Your first scenario: turn a form entry into a ticket

GoalWhen a request arrives in your form tool, Make records the customer and opens a ticket in Teamwork Desk.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. This first bubble is the app where requests land, such as your form tool.

  2. 02

    Set up the starting app

    Search that app by name, pick the module that watches new entries and link your account with Create a connection. Each entry then travels as a bundle, one item passed from module to module.

  3. 03

    Add Create Customer

    Click the + on the right, search Teamwork Desk and choose Create Customer. Map the details of the person from the form into the fields Make shows you.

  4. 04

    Add Create Ticket

    Add Create Ticket next, map the message from the form into the fields shown and, where Make offers it, the customer the previous module just created. No need to know values by heart: once connected, Make lists them for you.

  5. 05

    Test with Run once

    Send a test entry through your form and click Run once. Open each bubble to read the bundles it received, then check that the new ticket shows up in Teamwork Desk.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, also the shortest interval on the Free plan) and switch the scenario on. An instant form trigger skips the wait and runs on each entry.

Triggers

What starts a Teamwork Desk scenario

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

Teamwork Desk1Watch Events

Watch Events

Instant trigger

In Make“Triggers when an event related to tickets, customers, agents, threads or inboxes, is occured according to your settings in your Teamwork Desk.”

Watch Events starts your scenario when something happens in Teamwork Desk on a ticket, a customer, an agent, a thread or an inbox, depending on the events you select in its settings. Each event reaches Make as one bundle for the next module.

How it fires
instant. Teamwork Desk calls Make through a webhook as soon as the event happens, so there is no polling interval to wait for.
When to use it
a new ticket should post an alert in your team chat or add a row to a tracking sheet the moment it lands.
Watch out
click Create a webhook before Create a connection, and select only the events you need, since each one that reaches the scenario uses operations on your plan.
Modules

What each Teamwork Desk module does

Teamwork Desk gives you 29 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Teamwork Desk1

Add Reply To Ticket

Action

In Make“Adds a reply to the ticket.”

Customers get an answer on their existing ticket without anyone opening Teamwork Desk: Add Reply To Ticket posts the reply for you, built from data gathered earlier in the scenario.

When to use it
a request calls for a standard response, like confirming that a return was received.
Watch out
if Watch Events listens to thread events, your own reply can start the scenario again, so keep the two in separate scenarios.
Teamwork Desk2

Create Category

Action

In Make“Creates a new category within a site.”

Your help articles need a section to live in, and Create Category adds one to a helpdocs site, the knowledge base Teamwork Desk hosts for your customers.

When to use it
a feature launches and the help center needs a matching section before writers start.
Watch out
a category always belongs to a site, so choose the right one first; List Helpdocs Sites helps when you manage several.
Teamwork Desk3

Create Customer

Action

In Make“Creates a new customer.”

A person who contacted you through another tool becomes a customer record in Teamwork Desk with Create Customer, ready to be attached to tickets.

When to use it
a lead signs up in your CRM and support should know them before the first question arrives.
Watch out
to avoid duplicates, run List Customers first whenever the same person may already be in Teamwork Desk.
Teamwork Desk4

Create Helpdocs Site

Action

In Make“Creates a new helpdocs site.”

A brand new help center appears in Teamwork Desk when Create Helpdocs Site runs, giving articles and categories a fresh home.

When to use it
a multi-brand company opens a new brand and wants its knowledge base set up by the same scenario that prepares the rest of the account.
Watch out
this is a rare move; test it with Run once on a dummy name before you plug it into a live flow.
Teamwork Desk5

Create Inbox

Action

In Make“Creates a new inbox.”

Need a separate queue for a team, a brand or a channel? Create Inbox opens one in Teamwork Desk, where the matching tickets can be grouped.

When to use it
you onboard a new client and want their queue ready without clicking through the settings by hand.
Watch out
creating the inbox is one step; check in Teamwork Desk how customer messages will reach it before you announce it.
Teamwork Desk6

Create Ticket

Action

In Make“Creates a new ticket.”

Requests that start somewhere else end up in the same queue as everything else: Create Ticket turns them into proper Teamwork Desk tickets your agents can pick up.

When to use it
a contact form, a chat message or a failed payment alert should become work someone owns.
Watch out
tie the ticket to the right customer; Create Customer or List Customers earlier in the flow gives you that record to map.
Teamwork Desk7

Delete Article

Action

In Make“Deletes an article.”

Outdated answers stop confusing customers once Delete Article removes them from your helpdocs site.

When to use it
a product leaves your catalog and every article tied to it should disappear at the same time.
Watch out
plan as if there were no way back: keep a copy with Get Article if you might need the text, and test on a dummy article with Run once.
Teamwork Desk8

Delete Category

Action

In Make“Deletes a category within a site.”

When a part of the help center no longer makes sense, Delete Category clears that section out of the helpdocs site.

When to use it
two product lines merge and one of the sections is left empty after its articles moved.
Watch out
look at what is still inside first; List Articles on that category shows the content before you remove anything.
Teamwork Desk9

Delete Customer

Action

In Make“Deletes a customer.”

A request to remove someone's data can reach support automatically: Delete Customer erases their record from Teamwork Desk.

When to use it
a person asks to be forgotten in your CRM, and the help desk should follow without a manual search.
Watch out
the module needs the exact customer, so find it with List Customers and make sure only one match comes back before deleting.
Teamwork Desk10

Delete Helpdocs Site

Action

In Make“Deletes a helpdocs site.”

The heaviest cleanup in this list, Delete Helpdocs Site takes a whole help center out of Teamwork Desk.

When to use it
a brand closes, or a test site created during setup has to go.
Watch out
nothing here says whether its content can be recovered, so save what matters with List Articles and Get Article first, and keep this module out of automatic flows unless you are certain.
Teamwork Desk11

Delete Inbox

Action

In Make“Deletes an inbox.”

Agents see a shorter list of queues after Delete Inbox closes one you no longer use.

When to use it
a client contract ends and its dedicated queue should vanish as part of your offboarding scenario.
Watch out
tickets may still sit in that queue; check with List Tickets before removing it, and run the scenario by hand the first time.
Teamwork Desk12

Delete Ticket

Action

In Make“Deletes a ticket”

Spam and test tickets leave your help desk for good with Delete Ticket, so they stop cluttering the queue.

When to use it
a ticket comes from a known spam address, or a test run created junk you want gone.
Watch out
if you only need to change a ticket rather than remove it, Update Ticket leaves it in place and is the safer choice.
Teamwork Desk13

Get Article

Action

In Make“Gets the details of an article.”

One help article, fetched with its content, so the next step of the scenario can reuse it: that is what Get Article gives you.

When to use it
a reply to a customer should quote a help article, or you want a copy in a document tool before editing.
Watch out
you need the article's identifier; List Articles is the usual way to find it when you only know the category.
Teamwork Desk14

Get Customer

Action

In Make“Gets the details of a customer.”

Get Customer reads the record of one customer, which lets an alert or a report show who is asking instead of a bare ID.

When to use it
Watch Events signals a new ticket and your chat message should display the customer details next to it.
Watch out
each lookup is one operation; when you need many records at once, List Customers returns them in a single step.
Teamwork Desk15

Get Helpdocs Site

Action

In Make“Gets the details of a helpdocs site.”

Details of one help center come back with Get Helpdocs Site, useful when a later module needs to know which site it is working on.

When to use it
an audit scenario writes the details of each site into a spreadsheet before you redesign your help centers.
Watch out
most scenarios never need it; reach for it only when the site itself matters, not the articles inside.
Teamwork Desk16

Get Inbox

Action

In Make“Gets the details of an inbox.”

So that a message or a report can name the queue a ticket belongs to, Get Inbox pulls the details of that support inbox.

When to use it
you post new tickets to a team channel and want the inbox name next to each one.
Watch out
if the trigger bundle already carries what you need about the inbox, skip this step and save an operation.
Teamwork Desk17

Get Ticket

Action

In Make“Gets the details of a ticket.”

Complete ticket data for the rest of the flow: Get Ticket loads the details Teamwork Desk holds about one ticket.

When to use it
Watch Events tells you a ticket changed, and you need its full content to decide what happens next.
Watch out
map the ticket identifier from the previous module rather than typing one, or the scenario will read the same ticket on every run.
Teamwork Desk18

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the Teamwork Desk API offers becomes reachable from your scenario through Make an API Call, with the connection you already set up.

When to use it
the list has no module for your need, creating an article for example, and the Teamwork Desk API covers it.
Watch out
you write the request yourself, so keep the Teamwork Desk API documentation open while you build it.
Teamwork Desk19

Update Article

Action

In Make“Updates an article.”

Your knowledge base stays in step with the product when Update Article rewrites an existing help article from fresh data.

When to use it
a price, a link or a product name changes in your source of truth and the matching articles should follow.
Watch out
map only the parts you mean to change, and test on one article with Run once before running it over a whole list.
Teamwork Desk20

Update Category

Action

In Make“Updates a category within a site.”

Update Category edits a section of a helpdocs site, so the structure of your help center tracks how your offer is organized.

When to use it
a product gets a new name and its section in the help center must carry the same wording.
Watch out
you need both the site and the category; List Categories gives you the right one when names look alike.
Teamwork Desk21

Update Customer

Action

In Make“Updates a customer.”

Agents see current details on every ticket when Update Customer aligns a Teamwork Desk record with what your other tools know.

When to use it
a customer changes company or plan in your CRM, and support should see it on the next request.
Watch out
if Watch Events listens to customer events, this update can start another run; keep the sync one way to avoid a loop.
Teamwork Desk22

Update Helpdocs Site

Action

In Make“Updates a helpdocs site.”

Without rebuilding anything, Update Helpdocs Site changes the details of an existing help center.

When to use it
a rebrand touches several sites and you would rather apply the new details from one scenario than site by site.
Watch out
run it on one site with Run once, check the result in Teamwork Desk, then feed it the rest from List Helpdocs Sites.
Teamwork Desk23

Update Ticket

Action

In Make“Updates a ticket.”

Rules your agents would otherwise apply by hand become automatic with Update Ticket, which changes an existing ticket from data elsewhere in the scenario.

When to use it
a customer flagged as a key account in your CRM opens a ticket, and the ticket should reflect it right away.
Watch out
paired with Watch Events on ticket events, each update can trigger the scenario again, so split the logic into two scenarios.
Teamwork Desk24

List Articles

Search

In Make“Retrieves a list of all articles within a category or site.”

List Articles returns the articles of a category or a whole site, each one as its own bundle, ready for the next module.

When to use it
you want an inventory of your help content in a spreadsheet, or you plan to update many articles in one run.
Watch out
a search can bring back zero, one or many items, and every module after it runs once per item, so check the count before a big run.
Teamwork Desk25

List Categories

Search

In Make“Retrieves a list of all categories within a helpdocs site.”

To see the structure of a help center at a glance, List Categories gives you every section of one helpdocs site.

When to use it
before creating a category, you check that a section with the same name does not already exist.
Watch out
it works on one site at a time; combine it with List Helpdocs Sites when you run several help centers.
Teamwork Desk26

List Customers

Search

In Make“Retrieves a list of all customers.”

Pulling your customer records out of Teamwork Desk is the job of List Customers, which sends each one on as a separate bundle.

When to use it
you want to compare support customers with your CRM, or find a person before creating them again.
Watch out
on a large base, every module placed after it runs for each customer; test with Run once and read the bundles before activating.
Teamwork Desk27

List Helpdocs Sites

Search

In Make“Retrieves a list of all helpdocs sites.”

Every help center in your Teamwork Desk account shows up in List Helpdocs Sites, the starting point when a scenario must act on all of them.

When to use it
you manage several brands and want a report of all their help centers, or the same update applied to each.
Watch out
with a single site, you rarely need it; pick the site directly in the module that follows.
Teamwork Desk28

List Inboxes

Search

In Make“Retrieves a list of all inboxes.”

Working across teams instead of one queue starts with List Inboxes, which brings back all your support inboxes.

When to use it
you build a report of open work per queue, or you need the right inbox before calling Create Ticket.
Watch out
inbox names can change, so store the identifier in your scenario rather than matching on the name.
Teamwork Desk29

List Tickets

Search

In Make“Retrieves a list of all tickets.”

With List Tickets, the tickets of your account come out as a stream of bundles you can sort, count or export.

When to use it
a manager wants a spreadsheet of the backlog, or you need to clear test tickets in bulk with Delete Ticket.
Watch out
the list can be long; test with Run once, see how many bundles come back, then decide what the next modules do with each.
Need help

Need help automating Teamwork Desk with Make?

A person reads every message.

FAQ

Teamwork Desk and Make: common questions

01Is the Teamwork Desk Make integration free?
Yes, on the Make side. Teamwork Desk is a standard app, available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes per execution, 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, lift the cap on active scenarios, allow 40 minutes per execution and count usage in credits per month. Teamwork Desk itself is another matter: you need an active Teamwork Desk account, under the terms of its own pricing page.
02What do you need to connect Teamwork Desk to Make?
An active Teamwork Desk account and an API key. You create the key in Teamwork Desk: click your profile icon, choose View Profile, open the API Keys tab, click Create an API key, pick the type and copy it. In Make, add any Teamwork Desk module, click Create a connection, give it a name if you like, and paste the key. The connection is stored once and every Teamwork Desk module in your scenarios reuses it, so this setup happens a single time per account.
03Does the Teamwork Desk trigger in Make react instantly?
Yes. Watch Events is an instant trigger: Teamwork Desk calls Make through a webhook as soon as an event happens, instead of Make checking on a schedule. It covers events on tickets, customers, agents, threads and inboxes, depending on what you select in its settings. When you add it, click Create a webhook first, then Create a connection. Every event that reaches the scenario still uses operations on your plan, so keep the selection to the events your flow really needs.
04What if a Teamwork Desk module is missing in Make?
Use Make an API Call. It sends any request the Teamwork Desk API accepts, with the connection you already have, which can cover gaps such as creating an article or reading a single category, as long as the API offers them. You write the request yourself, so keep the Teamwork Desk API documentation at hand. Also note that the Teamwork Desk documentation on the Make side says it is AI-generated and may contain mistakes; when a detail matters, confirm it with Teamwork Desk directly.
05Make or n8n for Teamwork Desk?
It depends on what your scenario needs. In Make, Teamwork Desk comes with 30 modules: one instant trigger, 23 actions including Make an API Call, and 6 searches, and you can start on the Free plan. Many apps also have an n8n node, so check whether one exists for Teamwork Desk and compare it on the same points: which events it reacts to, which records it can create or edit, and how you would reach the rest of the API. Pick the tool whose list matches your flow.
Same platform

Other docs you might need on this stack.

Browse all integrations