Teamleader Make integrationAutomate Teamleader with Make.

You can pull a list of companies from Teamleader, filtered or complete, and feed each one to the next module as its own bundle.

A new company record appears in Teamleader, filled from the data of an earlier module, without anyone typing it in.

Hand it the ID of a company and you receive the full record, which lets later modules use information the trigger did not carry.

Changes made elsewhere flow back into the company record in Teamleader, so the CRM stays the place where the truth lives.

This module removes a company from Teamleader for good, as part of a cleanup driven by rules instead of clicks.

Contacts matching your search, or the whole address book, come out of Teamleader one bundle at a time for the rest of the scenario.

New person, new Teamleader contact: the module writes the record from data collected by another app, a form or an email.

You get the complete record of one contact from its ID, handy when a trigger only gives you part of the picture.

The contact in Teamleader receives the new information coming from another tool, so the sales team always calls the right number.

The module wipes a contact from Teamleader, which is useful when deletions must happen the same way every time.

This ties a person to a company in Teamleader, so the contact shows up in the right account and nobody wonders who they work for.

The module removes the tie between a contact and a company while keeping both records, which fits people who change jobs.

Deals matching your criteria, or all of them, come out of Teamleader so you can report on them or act on each one.

A new deal opens in Teamleader from the information gathered by another app, so no opportunity waits for someone to log it.

Give it a deal ID and it returns the full deal, ready for a message, a document or a decision further down the scenario.

You change a deal in Teamleader from the outside, keeping the pipeline accurate when events happen in other tools.

This one erases a deal from Teamleader, useful for automated cleanups of test data or duplicates.

You receive everything Teamleader holds about one invoice, which the invoice triggers alone may not provide.

A set of invoices, filtered or complete, leaves Teamleader and heads to your reporting or reminder steps.

The module fetches the invoice file itself in the format you pick, so you can store it, attach it or archive it.

Instead of the file, you get a link to the invoice, lighter to pass along in a message or a record.

A new invoice draft appears in Teamleader, prepared from data that already lives in your other tools.

This turns a draft invoice into a booked one, the step that makes it final in Teamleader.

You retrieve one Teamleader user, meaning a member of your team, to know who owns a record or who to notify.

Projects of the V2 edition come out of Teamleader, all or filtered, so you can report on them or act on each one.

A project opens in Teamleader V2 from what happened elsewhere, typically a deal that the customer just accepted.

One V2 project, found by its ID, with its details for the modules that follow.

Changes coming from another tool land on the V2 project in Teamleader, so everyone sees the same state.

The module closes a V2 project, the clean way to mark delivered work as done without opening Teamleader.

A closed V2 project comes back to life, ready for new work or new tasks.

This removes a V2 project from Teamleader entirely, meant for mistakes and test projects.

Groups, tasks and materials of a project, the lines of its structure, come out one bundle each.

You add a group, a task or a material to a project, which lets a scenario lay out a standard project structure.

One project line, whether a group, a task or a material, comes back with its information from its ID.

You adjust a group, a task or a material of a project from another tool, and the project plan stays accurate.

This removes a task, a material or a group from a project, to keep the plan free of lines nobody will use.

A new event lands in the Teamleader calendar, created from a booking or a signal in another tool.

An existing Teamleader event receives new details, by its ID, so the calendar follows what changed elsewhere.

The module cancels a Teamleader event by its ID, keeping calendars in line when plans fall through.

A to-do appears in Teamleader for your team, created by an event somewhere in your tools rather than by memory.

This module changes an existing Teamleader task instead of creating a second one next to it. You point the module at the task by its ID and map the new values from earlier modules.

This module ticks a task off in Teamleader for you, so your team's to-do list stays accurate without anyone clicking through the CRM. It acts on one task, identified by its ID.

This module brings a completed task back to open, keeping its history instead of making you create a fresh one. It is the natural counterpart of Complete a Task.

This module removes a task from Teamleader entirely. Pick it when a task should disappear rather than be marked done, for example a to-do created by mistake by an earlier test run.

This module schedules an existing Teamleader task, turning a loose item on someone's list into planned work your team can see coming.

This module logs time spent in Teamleader from another tool, so hours tracked elsewhere end up where you invoice them. Each run of the module adds one entry.

This module corrects an entry that already exists in Teamleader, for example when the duration or the note attached to it changes at the source. It targets one entry by its ID.

This module erases a time entry from Teamleader. It keeps billable hours honest when a timer was started by accident or a duplicate slipped in from another app.

This module finds quotations in Teamleader, or returns them all, so later modules can work on each one. It is a search module: the result can be zero, one or many bundles.

This module fetches the quotation itself as a file, in the format you choose in the module, ready to attach to an email or save in a cloud folder.

This module gives you a web address pointing to a quotation instead of the file. Handy when the next step only has to share or store a link, not move a document around.

This module reaches any endpoint of the Teamleader API through the connection you already set up, for the cases none of the listed modules cover. You write the request, Make handles the authorization.

This module puts a person on a project in the older Teamleader V1 projects, so they are part of the team working on it.

This module marks a Teamleader V1 project as closed once the work is done, so it drops out of the active projects your team sees.

This module opens a new project in Teamleader V1 from data arriving in the scenario, such as a won deal or a signed order.

This module removes a V1 project from Teamleader. Keep it for cleanup work, like projects opened twice by an earlier version of your scenario.

This module reads the details of one V1 project by its ID and hands them to the next modules, so you can reuse its name or status elsewhere.

This module sets a closed V1 project back to active, with its history intact, when work on it starts again.

This module changes how a person takes part in a V1 project, without removing them and adding them again.

This module edits an existing V1 project with information coming from another step of the scenario, so the project record never lags behind your other tools.

This module looks up V1 projects in Teamleader, or lists them all, and returns each match as a separate bundle for the following modules.