Resources · Make integration

Teamwork CRM Make integrationAutomate Teamwork CRM with Make.

Can your deals, contacts and activities move on their own? The Teamwork CRM Make integration gives you 57 modules, all 9 triggers instant. This guide is for sales and ops teams: link your API key, then build a first scenario around a new deal.

Try the Teamwork CRM integration on MakeSee the 57 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Teamwork CRM Make integration automate?

The Teamwork CRM Make integration links your CRM account to Make so that companies, contacts, deals, activities and notes can be created, read, updated or removed by a scenario, the automation you build in Make, without any code. Every trigger is instant: Teamwork CRM warns Make the moment something changes.

Never lose a follow-up. Watch Created Deals fires when an opportunity appears, and Create an Activity puts the next call on it right away, so every new deal leaves the scenario with an owner and a next step.

Feed the CRM from your forms. A signup form or a spreadsheet row goes through Search Contacts first, then Create a Contact or Update a Contact, which keeps one record per person instead of three.

Keep other tools honest. Watch Updated Deals and Watch Deleted Deals tell a shared sheet or a team channel what changed on the pipeline, including what disappeared.

What the app does not cover: there is no scheduled trigger, and the Make documentation lists no limits of its own for Teamwork CRM, only a note that its content is AI-generated and worth checking with the vendor. When a listed module is missing, Make an API Call reaches the rest of the API with the same connection.

Weighing Make against another tool? The n8n vs Make comparison sets out the criteria, Make pricing explains how operations are counted, and Make training helps if this is your first scenario.

Connect

How do you connect Teamwork CRM to Make?

  1. 01

    Generate an API key in Teamwork CRM

    In Teamwork CRM, click your profile icon, then Settings, then Personal. Scroll to API keys, click Generate API key, give it a name, set a valid-until date if you want one, click Save and copy the key.

  2. 02

    Open a Teamwork CRM module in Make

    In your Make account, add any Teamwork CRM module to a scenario and click Create a connection. The connection is your CRM account linked to Make once, then reused by every Teamwork CRM module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the instructions Make shows on screen, and confirm. From then on, Make can list the pipelines, stages and other objects it reads in your account when you fill a module.

First scenario

Your first scenario: a follow-up for every new deal

GoalWhen a deal is created in Teamwork CRM, Make adds a follow-up activity to it so the owner knows what to do next.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for Teamwork CRM and pick Watch Created Deals, the module that will start everything.

  2. 02

    Set up the webhook and the connection

    Click Create a webhook, then Create a connection and paste your API key. Teamwork CRM can now call Make each time a deal appears.

  3. 03

    Add the follow-up activity

    Click the + on the right of the trigger and choose Create an Activity. Map the deal coming from the first module into its fields so the activity is attached to the right opportunity.

  4. 04

    Test with Run once

    Click Run once, then create a test deal in Teamwork CRM. Open the bubbles above each module to read the bundle, the item passed along, and check the activity in the CRM.

  5. 05

    Switch it on

    Turn the scenario on. Because the trigger is instant, there is no 15-minute wait to plan: it starts when Teamwork CRM calls Make, and each module run counts as one operation on your plan.

Triggers

What starts a Teamwork CRM scenario?

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

Teamwork CRM1Watch Created Activities

Watch Created Activities

Instant trigger

In Make“Triggered when you add a new activity.”

Each new activity logged in Teamwork CRM becomes the starting point of your scenario, handed to the next module as one bundle you can map.

How it fires
instant: the app calls Make through a webhook as soon as the activity is added, which is why the module shows a lightning badge.
When to use it
a rep logs a call and the team channel or a shared sheet should hear about it without anyone copying it over.
Watch out
on this module Make asks for Create a webhook before Create a connection; follow that order.
Teamwork CRM2Watch Created Companies

Watch Created Companies

Instant trigger

In Make“Triggered when you add a new company.”

You get every new company the moment it lands in Teamwork CRM, ready to be copied into billing, a project tool or a client folder.

How it fires
instant: Teamwork CRM warns Make through a webhook as soon as the company is added, with no interval to wait for.
When to use it
a new account should open a matching customer record in your accounting app.
Watch out
a company created by Make itself, through Create a Company in another scenario, is still a new company and should fire this trigger too, so two scenarios can end up feeding each other if you are not careful.
Teamwork CRM3Watch Created Contacts

Watch Created Contacts

Instant trigger

In Make“Triggered when you add a new contact.”

Hands your scenario each person added to the CRM, so a new contact can join a mailing list or a welcome sequence without a manual export.

How it fires
instant: the app calls Make by webhook as soon as the contact exists, and the run starts on its own.
When to use it
contacts are entered by hand at events, and your email tool must receive them too.
Watch out
a bulk import in Teamwork CRM means one bundle per contact, and every module after the trigger spends an operation on each of them.
Teamwork CRM4Watch Created Deals

Watch Created Deals

Instant trigger

In Make“Triggered when you add a new deal.”

Your scenario learns about each new opportunity as soon as a rep opens it, which is the natural starting point for follow-ups and alerts.

How it fires
instant: Teamwork CRM calls Make through a webhook the moment the deal is created.
When to use it
every new deal should get a first activity, a message to the manager or a row in a forecast sheet.
Watch out
when you test with Run once, nothing happens until you actually create a deal in the CRM; keep a test deal ready to delete afterwards.
Teamwork CRM5Watch Created Notes

Watch Created Notes

Instant trigger

In Make“Triggered when you add a new note.”

Catches every note written in Teamwork CRM so its text can travel elsewhere, to a support ticket, a shared document or a colleague's inbox.

How it fires
instant: the app warns Make by webhook as soon as the note is saved.
When to use it
account managers write call notes in the CRM and the delivery team, who never opens it, needs them.
Watch out
a note alone gives little context; add Get a Deal or Get a Contact after the trigger when the message should say who the note is about.
Teamwork CRM6Watch Deleted Activities

Watch Deleted Activities

Instant trigger

In Make“Triggered when an activity is deleted.”

Tells your scenario that an activity has been removed, so the copy of it in a calendar or a task list can go too.

How it fires
instant: Teamwork CRM calls Make through a webhook as soon as the activity is deleted.
When to use it
activities are mirrored in another planning tool and a cancelled call should not stay there.
Watch out
the record no longer exists in the CRM, so a Get an Activity placed after this trigger has nothing to read; rely on what the trigger's bundle brings, and check it with Run once.
Teamwork CRM7Watch Deleted Deals

Watch Deleted Deals

Instant trigger

In Make“Triggered when a deal is deleted.”

Gives you a trace of every opportunity removed from the pipeline, the kind of event that otherwise goes unnoticed.

How it fires
instant: the app calls Make by webhook right when the deal is deleted.
When to use it
a sales manager wants a line in a log sheet, or a message, each time a deal vanishes from the board.
Watch out
run a test deletion with Run once and read the bundle before building on it; once the deal is gone, fetching it again from Teamwork CRM will not work.
Teamwork CRM8Watch Updated Activities

Watch Updated Activities

Instant trigger

In Make“Triggered when an activity is updated.”

Reacts whenever an existing activity is edited, so a rescheduled meeting or a changed task reaches the other tools that track it.

How it fires
instant: Teamwork CRM warns Make through a webhook as soon as the activity changes.
When to use it
activities are copied to a shared calendar and the copy must follow each change.
Watch out
an Update an Activity module in another scenario is still an edit and should fire this trigger too; if that scenario starts from this trigger, it can wake itself again and again.
Teamwork CRM9Watch Updated Deals

Watch Updated Deals

Instant trigger

In Make“Triggered when a deal is updated.”

Brings every change made to a deal into your scenario, the base of any alert on the pipeline.

How it fires
instant: the app calls Make through a webhook as soon as the deal is modified.
When to use it
finance wants to know when an opportunity is edited so the forecast sheet stays current.
Watch out
each edit is one run, even a small one, so a busy pipeline spends operations fast; the operation is Make's count of one module run on one bundle, and your plan has a quota of them.
Modules

What can Make do in Teamwork CRM?

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

Teamwork CRM1

Create a Company

Action

In Make“Creates a new company.”

Adds a new company to Teamwork CRM from the data another module hands over, so the account exists before anyone opens the CRM.

When to use it
a signup form or a spreadsheet row names a new client business and the sales team should find it ready.
Watch out
run Search Companies first when the name may already be there, or you end up with two records for one client.
Teamwork CRM2

Create a Contact

Action

In Make“Creates a new contact.”

Your new lead lands in Teamwork CRM as a contact, with the details mapped from the module before it, and nobody has to retype a thing.

When to use it
someone fills in a web form or books a call, and the person needs a CRM record as soon as it happens.
Watch out
a contact created twice splits its history; put Search Contacts just before this module to check first.
Teamwork CRM3

Create a Deal

Action

In Make“Creates a new deal.”

Opens an opportunity in one of your pipelines, so a quote request becomes something the sales team tracks rather than an email lost in a mailbox.

When to use it
a qualified lead or a request for a quote arrives from another app.
Watch out
a deal lives in a pipeline and a stage; create those first if they do not exist, then pick them from the lists Make shows once the connection works.
Teamwork CRM4

Create an Activity

Action

In Make“Creates a new activity.”

Puts a follow-up on the record, so the next action is written in the CRM instead of living in someone's head.

When to use it
right after a deal or a contact is created, to give its owner a clear next step.
Watch out
placed after a search, it creates one activity per result, and each one costs an operation; check the count with Run once before switching the scenario on.
Teamwork CRM5

Create a Note

Action

In Make“Creates a new note.”

Writes context from other tools, such as an email summary or a form answer, straight onto a deal or contact where the sales team will read it.

When to use it
a support ticket or a meeting tool produces text a rep should see before calling back.
Watch out
test with Run once and read the note in Teamwork CRM, so you see exactly which text your mapping sends.
Teamwork CRM6

Create a Pipeline

Action

In Make“Creates a new pipeline.”

Builds a whole new sales pipeline, handy when a product line or a region needs its own board.

When to use it
you roll out the same pipeline model for a new team from a list kept in a spreadsheet.
Watch out
a pipeline is structure, not data; placed in a scenario that fires on every new record, it would build one pipeline per record, so keep it in a scenario you start on purpose.
Teamwork CRM7

Create a Product

Action

In Make“Creates a new product.”

Adds an item to the product catalog of Teamwork CRM, so reps can pick it when they build a deal.

When to use it
your catalog lives in an online shop or a stock sheet, and new items should show up in the CRM as well.
Watch out
pair it with Search Products to make sure the item is not already listed; two identical products make the catalog confusing for everyone.
Teamwork CRM8

Create a Stage

Action

In Make“Creates a new stage.”

Adds a step to a pipeline, a new negotiation phase for example, without clicking through the pipeline settings.

When to use it
you rebuild several pipelines from one model and each needs the same list of steps.
Watch out
a stage belongs to one pipeline, so run Get a Pipeline or Search Pipelines first and map the result into this module.
Teamwork CRM9

Delete a Company

Action

In Make“Deletes a company.”

Removes a company from Teamwork CRM, which keeps the account list clean when a business closes or was entered by mistake.

When to use it
another system marks a client as closed, or as a test entry that should never have reached the CRM.
Watch out
a delete cannot be undone from Make; try the scenario with Run once on a dummy company before pointing it at real accounts.
Teamwork CRM10

Delete a Contact

Action

In Make“Deletes a contact.”

Erases a person from the CRM, so a removal request reaches Teamwork CRM without someone doing it by hand.

When to use it
a deletion request comes in through a form and the contact has to go.
Watch out
there is no undo, and a search by name can return several people; find the exact contact with Search Contacts and check the result before this module runs.
Teamwork CRM11

Delete a Deal

Action

In Make“Deletes a deal.”

Takes a deal off the pipeline for good, which clears duplicates and test opportunities from the board.

When to use it
a form sends the same request twice and the second deal only adds noise.
Watch out
once gone, the deal cannot be brought back from Make; when you only want to change its status, Update a Deal is the safer choice, and it keeps the history.
Teamwork CRM12

Delete a File

Action

In Make“Deletes a file.”

Deletes a file stored in Teamwork CRM, so an outdated document is not sent to a client by mistake.

When to use it
a newer version of a contract has been filed and the old copy has to go.
Watch out
Search Files helps you locate the right file first; a document deleted by mistake has no undo in Make, so test on a dummy file.
Teamwork CRM13

Delete an Activity

Action

In Make“Deletes an activity.”

Clears an activity that no longer makes sense, so each rep's list of things to do reflects what is really planned.

When to use it
a meeting is cancelled in a booking tool and the matching activity should disappear from Teamwork CRM.
Watch out
pair it with Search Activities to target the right one, and expect Watch Deleted Activities to fire in any scenario that listens for it.
Teamwork CRM14

Delete a Note

Action

In Make“Deletes a note.”

Removes a note from a record, useful to purge text that should never have been stored in the CRM.

When to use it
a faulty test left notes on real deals and you want them gone in one pass.
Watch out
Search Notes returns every match, and each match becomes its own delete, one operation apiece; read the list with Run once before you let the scenario delete anything.
Teamwork CRM15

Delete a Pipeline

Action

In Make“Deletes a pipeline.”

Removes an entire pipeline from Teamwork CRM, the broadest delete this app offers.

When to use it
a test pipeline built during setup is no longer needed.
Watch out
the Make documentation does not say what happens to the deals inside, so check with Teamwork CRM before running it on a pipeline that still holds opportunities, and keep this module out of any scenario started by a trigger.
Teamwork CRM16

Delete a Product

Action

In Make“Deletes a product.”

Drops a product from the catalog once it is discontinued, so reps stop adding it to new deals.

When to use it
the item is archived in your shop or inventory tool and the CRM should follow.
Watch out
target the right entry with Search Products, then test on a dummy product; a delete made by Make cannot be reversed.
Teamwork CRM17

Delete a Stage

Action

In Make“Deletes a stage.”

Removes a step from a pipeline, for example a phase your team has stopped using.

When to use it
you simplify several pipelines and want the same change applied to each without clicking through every board.
Watch out
the Make documentation does not say what happens to deals sitting in that stage, so empty it first and test with Run once.
Teamwork CRM18

Delete a User

Action

In Make“Deletes a user.”

Removes a user account from Teamwork CRM, which closes CRM access when someone leaves the company.

When to use it
an HR tool or an offboarding form records a departure and the CRM should follow.
Watch out
make sure you have the right person with Search Users, and ask Teamwork CRM what happens to the records that user owned, since the Make documentation is silent on it.
Teamwork CRM19

Get a Company

Action

In Make“Gets a company.”

Fetches one company with all its details, so later modules can quote them in an email, a sheet or an invoice.

When to use it
a trigger hands you a deal or a contact and you need the full company record behind it.
Watch out
Get reads a record you already point to; when you only know a name, Search Companies is the module to pick.
Teamwork CRM20

Get a Contact

Action

In Make“Gets a contact.”

Pulls up the full record of one person, useful when the incoming bundle, the item passed from module to module, only refers to the contact.

When to use it
a new deal arrives and your welcome email needs the details of the person behind it.
Watch out
it returns one contact, never a list; to find people by criteria, use Search Contacts instead.
Teamwork CRM21

Get a Deal

Action

In Make“Gets a deal.”

Reads everything about a single deal at the moment the scenario runs, so the next modules work with complete data.

When to use it
an activity or note trigger fires and you want the related deal before deciding what to send.
Watch out
what you get is a snapshot; if a later module changes the deal, fetch it again before relying on the values.
Teamwork CRM22

Get an Activity

Action

In Make“Gets an activity.”

Loads one activity in full, which helps when the previous module only gives you a pointer to it.

When to use it
you send a reminder by email or chat and the message should carry the activity's details.
Watch out
keep it for an activity you can already identify; Search Activities covers the case where you look for activities by criteria.
Teamwork CRM23

Get a Note

Action

In Make“Gets a note.”

Retrieves one note with its content so the text can be reused somewhere else, in a document or a message.

When to use it
a note is written on a deal and its content should reach a colleague who works outside the CRM.
Watch out
it reads one note per operation; when you need many notes at once, Search Notes returns them as separate bundles.
Teamwork CRM24

Get a Pipeline

Action

In Make“Gets a pipeline.”

Brings back one pipeline and its details, a handy reference before creating stages or deals inside it.

When to use it
a scenario builds deals for several teams and has to confirm which pipeline it is about to fill.
Watch out
if you do not know yet which pipeline you mean, Search Pipelines lets you look it up first.
Teamwork CRM25

Get a Product

Action

In Make“Gets a product.”

Returns one product from your catalog so its details can travel to a quote, an invoicing tool or a spreadsheet.

When to use it
a deal names a product and the next app needs the full description, not just the name.
Watch out
it reads one product per run; to list several, Search Products is the right choice.
Teamwork CRM26

Get a Stage

Action

In Make“Gets a stage.”

Looks up a single stage, the step of a pipeline where a deal sits, so you can quote its name in a message.

When to use it
a deal changes and your team channel should say which stage it has reached.
Watch out
a stage only makes sense with its pipeline; add Get a Pipeline when the message should name both.
Teamwork CRM27

Get a User

Action

In Make“Gets a user.”

Fetches one user of your Teamwork CRM account, typically the person who owns a deal or an activity.

When to use it
you want to notify the right salesperson and need that person's details from the CRM.
Watch out
the module reads the user you point to; Search Users is the one that finds users by criteria.
Teamwork CRM28

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Teamwork CRM API from your scenario, with the same connection as the other modules, which covers what the list on this page leaves out.

When to use it
you need an object or an option that none of the listed modules offers.
Watch out
you write the request yourself, so keep the Teamwork CRM API documentation open and test with Run once.
Teamwork CRM29

Update a Company

Action

In Make“Updates a company.”

Changes the details of an existing company, so the CRM stays in step with your billing or support tool.

When to use it
client information changes in another system and the account in Teamwork CRM should match.
Watch out
the update must land on the right record; chain Search Companies or a trigger in front so the company is identified before you change it.
Teamwork CRM30

Update a Contact

Action

In Make“Updates a company.”

Edits a contact that already exists, so new details reach the CRM without anyone retyping them.

When to use it
a person updates a profile in a form or a newsletter tool and the CRM record should follow.
Watch out
map only the values you really want to change, then read the result with Run once before letting the scenario touch real contacts.
Teamwork CRM31

Update a Deal

Action

In Make“Updates a deal.”

Keeps an opportunity accurate by editing it from another tool, for instance once a contract is signed in an e-signature app.

When to use it
an outside event changes what the sales team should see on the deal.
Watch out
this edit is a deal update like any other, so expect Watch Updated Deals to fire too; a scenario that listens for deal updates and also updates deals can feed itself without end.
Teamwork CRM32

Update a File

Action

In Make“Updates a file.”

Changes a file stored in Teamwork CRM, so the document attached to a client stays current.

When to use it
a document is revised in another tool and its record in the CRM should follow.
Watch out
the Make documentation does not detail what can be changed on a file; open the module once the connection exists and read the fields Make shows before you plan around it.
Teamwork CRM33

Update an Activity

Action

In Make“Updates an activity.”

Adjusts an activity already planned when the plan changes elsewhere, so reps do not show up to a meeting that moved.

When to use it
a call is rescheduled in a booking tool and the CRM should show the new plan.
Watch out
expect the change to fire Watch Updated Activities in any scenario that listens for it; keep two scenarios from reacting to each other.
Teamwork CRM34

Update a Note

Action

In Make“Updates a note.”

Rewrites an existing note, handy when a summary is corrected after the fact and the CRM should show the final version.

When to use it
a meeting transcript or a form answer is revised and the note on the deal must match.
Watch out
find the right note first with Search Notes or Get a Note, then check with Run once how the new text lands.
Teamwork CRM35

Update an User

Action

In Make“Updates a user.”

Edits a user of your Teamwork CRM account, keeping the team directory in line with your HR or identity tool.

When to use it
someone changes team or name, and the CRM should follow without a ticket to the admin.
Watch out
Make spells this module Update an User, so type that exact name when you search for it in the module list.
Teamwork CRM36

Update a Pipeline

Action

In Make“Updates a pipeline.”

Changes the details of a pipeline, for example to align it with a revised sales process.

When to use it
pipelines are described in a central list and edits made there should reach Teamwork CRM.
Watch out
every rep working in that pipeline sees the change at once, so run the scenario with Run once on a test pipeline before the real one.
Teamwork CRM37

Update a Product

Action

In Make“Updates a product.”

Keeps a catalog item in line with your source of truth, such as an online shop or a stock sheet.

When to use it
a product description changes and reps should quote the new version on their deals.
Watch out
when your source only knows the product by name, place Search Products first; this module needs the exact item to change.
Teamwork CRM38

Update a Stage

Action

In Make“Updates a stage.”

Edits a stage of a pipeline, useful when a step changes name or meaning for your team.

When to use it
you standardize the wording of steps across pipelines from a single list.
Watch out
every deal sitting in that stage shows the change, so test with Run once before switching the scenario on.
Teamwork CRM39

Search Activities

Search

In Make“Searches activities by given criteria.”

Finds every activity matching your criteria and passes them on one by one, each as its own bundle, to the modules that follow.

When to use it
you want the follow-ups linked to a client gathered in one digest message.
Watch out
a search can return zero, one or many results, and each result costs an operation in every module placed after it.
Teamwork CRM40

Search Companies

Search

In Make“Searches companies by given criteria.”

Looks for companies by the criteria you set and returns what it finds, the classic check before creating an account.

When to use it
a form sends a business name and you want to know whether that company is already in Teamwork CRM.
Watch out
zero results is a normal answer, not an error; decide what the scenario should do in that case before you switch it on.
Teamwork CRM41

Search Contacts

Search

In Make“Searches contacts by given criteria.”

Finds the Teamwork CRM contacts that match your criteria and hands each one on as its own bundle, so the scenario knows who already exists before it acts.

When to use it
before Create a Contact, to avoid adding a person twice when a form sends a name you may already have.
Watch out
the search can return zero, one or several bundles; plan what happens when nothing matches, or the next module has no contact to work on.
Teamwork CRM42

Search Deals

Search

In Make“Searches deals by given criteria.”

Pulls the deals that match your criteria into the scenario, ready to feed an update, a message or a spreadsheet row, with no manual lookup in Teamwork CRM.

When to use it
you know what the deal looks like but not which one it is; once an earlier module points to the exact deal, Get a Deal is more direct.
Watch out
each deal found becomes its own bundle, and every module placed after the search runs once per bundle, which counts operations on your Make plan.
Teamwork CRM43

Search Files

Search

In Make“Searches files by given criteria.”

Finds the files stored in Teamwork CRM that fit your criteria and hands each one on, ready for Update a File or Delete a File.

When to use it
when a scenario must act on files but only knows what to look for, not which file exactly.
Watch out
an empty result is a normal outcome, not an error; test with Run once and read what came back.
Teamwork CRM44

Search Notes

Search

In Make“Searches notes by given criteria.”

Collects the notes that match your criteria, one bundle each, so what your team wrote can feed a report, a summary or a follow-up.

When to use it
to gather existing notes before adding a new one with Create a Note, or to copy them into another tool.
Watch out
if several notes match, every later module repeats for each of them; check the bundle count after Run once before switching the scenario on.
Teamwork CRM45

Search Pipelines

Search

In Make“Searches pipelines by given criteria.”

Looks up the pipelines of your Teamwork CRM account, so the scenario picks the right one when it creates or moves deals instead of relying on a value typed once and forgotten.

When to use it
when a deal must land in the right pipeline and the scenario has to look that pipeline up first.
Watch out
pipelines rarely match many results, yet the search can still return zero; handle that case so the deal step does not run on an empty value.
Teamwork CRM46

Search Products

Search

In Make“Searches products by given criteria.”

Searches your Teamwork CRM product catalog and returns the items that match your criteria, ready to go into a deal, an email or a row elsewhere.

When to use it
when an incoming order or quote names a product and the scenario needs the matching record, not just its label.
Watch out
a loose criterion can return many products at once, and each one triggers the following modules; narrow the search before going live.
Teamwork CRM47

Search Stages

Search

In Make“Searches stages by given criteria.”

Returns the pipeline stages that match your criteria, so the scenario finds the right step of your sales process before moving a deal there with Update a Deal.

When to use it
when a scenario changes where a deal sits and you prefer to look the stage up rather than hard-code it.
Watch out
after renaming a stage in Teamwork CRM, rerun the scenario with Run once to confirm the search still finds it.
Teamwork CRM48

Search Users

Search

In Make“Searches users by given criteria.”

Finds the Teamwork CRM users that match your criteria, so a deal, an activity or a note goes to the right colleague.

When to use it
when the owner of a new record depends on data coming from another app and must be resolved to a user first.
Watch out
the search runs through your connection, so it can logically only return what your own Teamwork CRM account is allowed to see; test with Run once if a colleague seems missing.
Need help

Need help automating Teamwork CRM with Make?

A person reads every message.

FAQ

Teamwork CRM and Make: common questions

01Is the Teamwork CRM Make integration free?
Yes, on the Make side. Teamwork CRM is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift the interval to 1 minute and count usage in credits, meaning operations, per month. You still need an active Teamwork CRM account with its own subscription, which this page does not price.
02What do you need to connect Teamwork CRM to Make?
An active Teamwork CRM account and an API key. You generate the key in Teamwork CRM from your profile icon, then Settings, Personal and API keys, where Generate API key creates it; you can name it and set a valid-until date. In Make, add a Teamwork CRM module, click Create a connection, and paste the key. On instant modules, Make asks you to click Create a webhook first. The Connection name field is optional.
03Does the Teamwork CRM trigger in Make react in real time?
Yes. All 9 Teamwork CRM triggers are instant: the app calls Make through a webhook as soon as an activity, company, contact, deal or note is created, or a deal or activity is updated or deleted. There is no polling interval to set, unlike scheduled triggers, which Make checks every 15 minutes by default. Each event still starts one run, and each module in that run counts as an operation on your plan.
04What if a Teamwork CRM module is missing in Make?
Use Make an API Call. This module calls any endpoint of the Teamwork CRM API with the same connection as the others, so an object or option absent from the 57 listed modules stays reachable. You write the request yourself with the Teamwork CRM API documentation at hand. The Make documentation for this app lists no specific limits, only a warning that its content is AI-generated, so check important details with Teamwork CRM directly.
05Should you use Make or n8n with Teamwork CRM?
It depends on what you already run and what the automation needs. On Make, Teamwork CRM brings 9 instant triggers, 38 actions and 10 searches, plus Make an API Call for the rest, and it works from the Free plan. Many apps also have an n8n node, so check whether one exists for Teamwork CRM and whether it covers the objects you need. Compare the modules each tool offers for your case rather than the tools in general.
Same platform

Other docs you might need on this stack.

Browse all integrations