Resources · Make integration

MeisterTask Make integrationAutomate MeisterTask with Make.

Tasks, comments and labels in MeisterTask can move on their own. The MeisterTask Make integration gives you 16 modules: 3 triggers, 8 actions and 5 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Try the MeisterTask integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the MeisterTask Make integration do?

The MeisterTask Make integration links your MeisterTask account to Make so tasks, comments, labels and attachments follow rules you set once. You build a scenario, which is the automation itself: a chain of modules, each one a brick that watches, creates, updates or looks something up. No code is involved.

Sort incoming work without touching it. A support lead can start from Watch New Tasks In A Section and send each new card straight to Add a Label To a Task, so the board shows its category the moment someone opens it.

Turn another app's event into a task. A form entry, a new deal or a row in a sheet can end in Create a Task, then Create an Attachment adds the file that came with it. Our Airtable Make integration guide shows the kind of source that fits this pattern.

Keep a written trail. Watch Comments picks up the discussion on a task, and Create a Comment lets another scenario post a status note back, so developers and account managers read the same thread.

What Make does not give you here: an instant trigger. All three MeisterTask triggers are scheduled, which means Make checks for news on the scenario's schedule. Anything the listed modules leave out goes through Make an API Call. The same app often has an n8n node too; the n8n vs Make comparison lays out the criteria, and the Make training is there if you want guided practice.

Connect

How do you connect MeisterTask to Make?

  1. 01

    Open a MeisterTask module

    In your scenario, add any MeisterTask module and click Create a connection. A connection is your MeisterTask account linked to Make once; every other MeisterTask module in your scenarios reuses it.

  2. 02

    Give the connection a name

    This step is optional, but a clear name such as your workspace or team helps later, when you have several accounts linked and need to pick the right one from the list.

  3. 03

    Authorize and save

    Grant Make access on the MeisterTask page that opens, or paste the key MeisterTask gives you if Make asks for one. Then click Save, and the module can read your projects.

First scenario

Your first scenario with MeisterTask

GoalWhen a new task lands in a MeisterTask section, Make adds a label to it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Pick the trigger

    Search for MeisterTask, choose Watch New Tasks In A Section and click Create a connection to link your account, or select the connection you already made.

  3. 03

    Tell it which section to watch

    Fill the module fields. Once the connection exists, Make lists what it can read in your account, so you choose the section from the list instead of typing it.

  4. 04

    Add the label

    Click the + on the right of the trigger, add Add a Label To a Task and map the task from the first module, so each new card gets the label you pick.

  5. 05

    Test with Run once

    Drop a test task in the section and click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one task.

  6. 06

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; keep that or change it, then switch the scenario on.

Triggers

What can start a MeisterTask scenario?

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

MeisterTask1Watch Comments

Watch Comments

Scheduled trigger

In Make“Get all comments of a task.”

Watch Comments brings the comments of a task into your scenario, so the discussion around a card can feed a report, a chat message or a follow-up task somewhere else.

How it fires
scheduled, which means Make checks MeisterTask on the scenario's schedule and picks up what was written since the last check.
When to use it
a client project where comments hold decisions that account managers outside MeisterTask also need to see.
Watch out
this trigger looks at one task's comments, so choose a task that really carries the conversation you care about.
MeisterTask2Watch New Tasks In A Section

Watch New Tasks In A Section

Scheduled trigger

In Make“Triggers when a new task added to a section.”

Here the scenario starts whenever a new task shows up in one section of a project, which makes a column of your board act like an inbox that Make keeps an eye on.

How it fires
scheduled, so Make asks MeisterTask for new tasks on the scenario's schedule, every 15 minutes on a new scenario unless you change it.
When to use it
a To Do or Incoming column where requests arrive and need a label, an owner or a notification.
Watch out
it only watches the one section you pick, so a request filed in another column never starts this scenario.
MeisterTask3Watch Tasks

Watch Tasks

Scheduled trigger

In Make“Triggers when a task is created or updated.”

Watch Tasks is the wider net: it reacts when a task is created and also when one is updated, so changes across your work reach Make without you pointing at a single section.

How it fires
scheduled; Make checks MeisterTask on the scenario's schedule and passes each new or changed task as a bundle.
When to use it
syncing tasks to a sheet or a CRM, where every edit should follow.
Watch out
if the same scenario later runs Update a Task, that edit counts as an update too and can come back on the next check, so keep writing and watching in separate flows.
Modules

What can Make do in MeisterTask?

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

MeisterTask1

Add a Label To a Task

Action

In Make“Adds a label/tag to a task.”

Tags an existing task with one of your labels, so filters and board views show at a glance which client, priority or type of work it belongs to.

When to use it
right after a trigger, to sort incoming tasks by the form or channel they came from.
Watch out
the label has to exist; pair it with Create a Tag/Label when it might not.
MeisterTask2

Create a Comment

Action

In Make“Creates a comment.”

Posts a comment on a task, which lets another tool leave a trace where your team already reads: a payment received, a file approved, a ticket closed.

When to use it
the task should tell its own story, so nobody has to copy updates over from email.
Watch out
each run writes a new comment, so filter the flow if the source can send the same event twice.
MeisterTask3

Create an Attachment

Action

In Make“Creates an attachment for a task.”

Adds a file to a task, so the contract, brief or screenshot sits next to the work instead of in someone's inbox.

When to use it
after Create a Task, to attach the document that arrived with a form entry or an email.
Watch out
on the Free plan, Make handles files up to 5 MB, so large design files may need a paid plan or a link in a comment.
MeisterTask4

Create a Tag/Label

Action

In Make“Creates a new label.”

Creates a brand new label, which keeps your label list in step with something outside MeisterTask, such as a list of clients or product lines.

When to use it
when a new client signs in your CRM and every task for that client should carry its own label from day one.
Watch out
a fresh label sits on no task yet, so follow it with Add a Label To a Task to put it to work.
MeisterTask5

Create a Task

Action

In Make“Creates a new task.”

Opens a new task in a project from data coming out of another module, which is the most common way to turn requests from other tools into planned work.

When to use it
a web form, a support ticket or a signed quote that should become a card without anyone retyping it.
Watch out
one bundle makes one task, so a search placed before it can create several cards in a single run.
MeisterTask6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the MeisterTask API with the connection you already set up, for the cases the other modules do not cover.

When to use it
when you need something no listed module offers, such as an operation on another kind of MeisterTask object.
Watch out
you describe the request yourself, so keep the MeisterTask API documentation open while you fill the module.
MeisterTask7

Update a Tag/Label

Action

In Make“Updates a tag/label itself, it means that label will be changed on all tasks/projects where it was used.”

Renames or edits a label itself, and that change shows up on every task and project where the label is already used.

When to use it
a client changes its name in your CRM and the label across the whole board should follow.
Watch out
the change is global by design; if you only want to retag one task, use Add a Label To a Task instead.
MeisterTask8

Update a Task

Action

In Make“Updates a task.”

Changes an existing task, so its state in MeisterTask matches what just happened in another tool, without anyone opening the board to edit the card.

When to use it
an invoice is paid or a pull request is merged, and the related task should reflect it.
Watch out
you need the task first, so place a search or a trigger before it that hands over the right one.
MeisterTask9

Get Project Info

Search

In Make“Get project details by ID.”

Fetches the details of one project from its ID, which gives later modules the project's information to reuse in a message, a report or a record elsewhere.

When to use it
a task arrives from a trigger and you want its project details written next to it in a sheet.
Watch out
it works from an ID, so map the ID from an earlier module rather than typing a project name.
MeisterTask10

Get Task Comments

Search

In Make“Get comments from a task by ID.”

Pulls every comment of one task on demand, in the middle of a scenario, when you need the discussion but it is not what started the run.

When to use it
a task is marked done and you want its full comment history saved in a client folder or sent in a summary.
Watch out
each comment comes out as its own bundle, so later modules run once per comment unless you group them.
MeisterTask11

Get Task Labels

Search

In Make“Get all labels from a particular task.”

Reads the labels already on a task, so the scenario can decide what to do next based on how the card has been tagged.

When to use it
route urgent tasks to one chat channel and the rest to another, or skip tasks that already carry a label.
Watch out
a task with no label returns nothing, and the modules after it do not run for that task.
MeisterTask12

Get Tasks From a Section

Search

In Make“Get tasks from a particular section.”

Returns the tasks sitting in one section right now, a snapshot of a column rather than a watch on what is new.

When to use it
collect everything in a Review column when a release is tagged, then comment on each task or copy them into a report.
Watch out
a busy section can hand back many bundles, and each one costs operations in the modules that follow.
MeisterTask13

List Tasks

Search

In Make“Retrieve all available tasks.”

Retrieves all the tasks your connection can reach, the broadest search of the set, useful when no single project or section is the right scope.

When to use it
an export of the whole workload to a sheet, or a check that looks across every project for one client.
Watch out
the result can be large; add a filter after it so later modules only touch the tasks you need.
Need help

Need help automating MeisterTask with Make?

A person reads every message.

FAQ

MeisterTask and Make: common questions

01Is the MeisterTask Make integration free?
Yes, MeisterTask is a standard app in Make, available from the Free plan. That plan lets you keep 2 active scenarios, runs scheduled scenarios 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) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations: one module running on one bundle is one operation.
02What do you need to connect MeisterTask to Make?
A MeisterTask account that can see the projects you want to automate, and a Make account. The MeisterTask documentation in Make lists no extra prerequisite. You add a MeisterTask module, click Create a connection, optionally name it, authorize Make on the MeisterTask page or paste the key it asks for, then click Save. That single connection then serves every MeisterTask module in your scenarios, so you do this once per account rather than once per module.
03Do MeisterTask triggers in Make fire instantly?
No. The three MeisterTask triggers, Watch Comments, Watch New Tasks In A Section and Watch Tasks, are all scheduled. Make checks MeisterTask on the schedule set on the first module, which is every 15 minutes by default on a new scenario. On the Free plan that is also the shortest interval; paid plans can go down to 1 minute. Anything new since the last check arrives together in the next run, one bundle per task or comment.
04What if a MeisterTask module you need is missing in Make?
Use Make an API Call. It is one of the 16 MeisterTask modules and calls any endpoint of the MeisterTask API with the connection you already have, so you can cover what the other 15 modules leave out. You write the request yourself, which asks for a look at the MeisterTask API documentation. The Make documentation for MeisterTask gives no numbered limits, so there is no documented quota to plan around on the Make side.
05Should you use Make or n8n for MeisterTask?
It depends on the criteria that matter to you. On the Make side, MeisterTask comes with 16 ready modules, three scheduled triggers, and Make an API Call for the rest, all usable from the Free plan with 2 active scenarios. The same app often has an n8n node as well, so check that its node covers the tasks, comments and labels you work with before comparing. Pick the tool whose modules match your scenario and whose editor your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations