Resources · Zapier integration

MeisterTask Zapier integrationAutomate MeisterTask with Zapier.

The MeisterTask Zapier integration gives you 9 triggers, 5 actions and 4 searches. Here is what each one does, what it costs on your plan, how to connect your account and the traps to dodge before your first board fills itself.

See the 18 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MeisterTask Zapier integration actually does

Connecting MeisterTask to Zapier means your task boards react to events and get written to without anyone dragging cards by hand. Something happens in MeisterTask (a project, a comment, a label), Zapier notices, and a step you chose runs on its own. It works on the free plan, since MeisterTask is not a premium app.

Three results worth setting up. First, projects that start furnished: New Project fires the second a project exists, and Create Task drops the opening task in it. Second, a comment trail that leaves the board: New Comment picks up what people write on a task so you can pass it on to the tool where your account managers actually read. Third, tasks that move when another tool moves: Find Task locates the card, Update Task changes it, and nobody has to remember to do it.

What Zapier does not do here matters just as much. There is no operation to delete a task, archive a project or remove a person; the editor simply does not offer them. Four triggers out of nine are instant, the five others are checked on a timer, and that split decides how fast your Zap reacts. And a Zap never reaches back into your history: tasks created before you switched it on stay where they are.

If you are still choosing a platform, the MeisterTask Make integration covers the same app on Make, and our Make vs Zapier comparison lays out the criteria side by side.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for it to happen.
Action
What the Zap does once it has started: the step that writes, sends or changes something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully; your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment it happens.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something already in an app (a task, a label) so the next steps can reuse what it found.
Cost

What MeisterTask on Zapier really costs

Zapier bills completed actions, never the waiting. Watching your MeisterTask boards is free however often Zapier checks.

  • Triggernever counted
  • Successful action1 task each
  • Free plan100 tasks a month, two-step Zaps
  • Premium appno

The trigger never costs a task. Each action that succeeds counts once, so a Zap that creates a task and then a label uses two per run; an action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter, a search or a second action and it becomes a multi-step Zap that needs a paid plan. MeisterTask itself is not premium, so the free plan can use it.

Connect

Connect MeisterTask to Zapier in 3 steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. A dialog opens with a search box: type MeisterTask and pick it from the list.

  2. 02

    Sign in to MeisterTask

    Click Add connection. A new tab opens on MeisterTask: sign in with the account whose projects the Zap should read and write. Use the account that will own the automation, not a colleague's.

  3. 03

    Grant access and reuse it

    Allow Zapier to access the account. The connection is now saved once and every MeisterTask step of every Zap can reuse it, so you never sign in again for the next workflow.

First Zap

Your first Zap: every new client project gets its kickoff task

GoalWhen an account manager creates a client project, MeisterTask gets its kickoff task right away, and internal projects are left alone.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose MeisterTask as the app and New Project as the event. It is instant, so the Zap will react as soon as the project exists.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent projects of the connected account. Pick a real one, it will feed the mapping that follows.

  3. 03

    Add the filter

    Add a Filter step and set its three boxes: a field the trigger brought back that tells client projects apart, the rule, and the value to compare with. Projects that do not match stop here. This filter makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Create Task

    Add MeisterTask with Create Task. Task Name is required: write the name of your kickoff task, then map whatever the trigger brought back that you want on the card.

  5. 05

    Test, then publish

    Run the action test once and check in MeisterTask that the kickoff task was created as you expect. Then click Publish to switch the Zap on.

Triggers

MeisterTask triggers on Zapier

9 events start a Zap when something happens in MeisterTask, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Attachment

Instant trigger

In Zapier“Triggers when an attachment is created.”

Starts your Zap whenever a file gets attached somewhere in MeisterTask, so the people waiting for that document hear about it without opening the task.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a designer attaches the final mockup to a task and the account manager should know at once, not at the end of the day.
Watch out
only attachments added after the Zap is published count; files already on your tasks are never picked up.
2

New Checklist Item

Polling trigger

In Zapier“Triggers when a new checklist item is added to a task.”

Fires when someone adds a line to the checklist of a task. Handy when a checklist is where your team breaks a job into smaller steps.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a QA lead keeps adding test steps to a release task and you want each new step logged elsewhere for the audit trail.
Watch out
on the free plan a new item can wait up to a full interval before the Zap notices it.
3

New Person

Polling trigger

In Zapier“Triggers when a new person is added to a project.”

Reacts when a person joins a project. It is the hook for anything that should happen when a newcomer lands on a board.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a freelancer is added to a client project and should get a welcome task assigned without the project lead thinking about it.
Watch out
Project is a required setting, so the Zap watches the project you pick when you set it up.
4

New Project

Instant trigger

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

Goes off as soon as a project is created in MeisterTask. This is the starting point for any template you want every project to carry.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new client engagement should open with the same kickoff task, created the moment the project exists.
Watch out
every new project starts the Zap, internal ones included; a filter keeps only the ones you want, and turns the Zap into a paid multi-step one.
5

New Section

Polling trigger

In Zapier“Triggers when a new section is created.”

Notices a new section inside one project. When your sections stand for stages, a new one usually means the way work flows has changed.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
an operations manager adds a Blocked section to a delivery project and wants the team lead warned that the process moved.
Watch out
the project is a required setting, so this trigger never watches your whole workspace at once.
6

New Label

Instant trigger

In Zapier“Triggers when a label is created.”

Fires when a label is created. Labels are how many teams tag priority, client or type of work, so a new one is often worth hearing about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a team lead wants a heads up each time someone invents a new label, before the board fills with near duplicates.
Watch out
this is about creating the label itself, not about putting it on a task; that is New Task Label.
7

New Comment

Polling trigger

In Zapier“Triggers when a new comment is created on a task.”

Picks up each new comment written on a task, so the discussion can reach people who never open MeisterTask.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a client success manager follows one strategic task and wants every reply on it forwarded as it lands.
Watch out
both a project and a task are required, so this trigger listens to one task at a time, not to every conversation on the board.
8

New Task

Polling trigger

In Zapier“Triggers when a Task is created or changed.”

The trigger Zapier puts first for MeisterTask: it starts the Zap on tasks, and a single setting decides whether that means new tasks or updated ones.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a sales team logs each new deal as a task and wants it copied to the reporting tool without retyping.
Watch out
the setting Trigger On Updated Tasks Instead of New Tasks? is either or: set to yes, brand new tasks no longer start the Zap.
9

New Task Label

Instant trigger

In Zapier“Triggers when a Task label is created.”

Reacts the moment a label lands on a task. In practice, that is the moment someone flags a card as urgent, blocked or ready for review.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
tagging a task Urgent should alert the person on call straight away, even on the free plan.
Watch out
a Zap that adds labels to tasks itself can set this trigger off again; keep a filter between the two.
Actions

MeisterTask actions on Zapier

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

1

Create Attachment

Action

In Zapier“Creates a new attachment.”

Hangs a file on an existing task, so the document sits next to the work it belongs to.

When to use it
a signed brief arrives elsewhere and should end up on the production task of that client.
Watch out
both the task and a filename are required, so you need a step earlier in the Zap that tells it which task.
2

Create Label

Action

In Zapier“Creates a new label.”

Creates a new label in MeisterTask, ready to be put on tasks afterwards.

When to use it
each new client in your CRM should get its own label so the team can sort every board by account.
Watch out
Name and Color are both required, so decide on a color rule before the first run, not after.
3

Create Task

Action

In Zapier“Creates a new task.”

Adds a fresh task to MeisterTask from whatever event started the Zap. The action Zapier highlights first for this app.

When to use it
a form request or a signed deal should become a card on the right board without anyone copying it over.
Watch out
Task Name is required; map it from something meaningful in the trigger, or every card the Zap creates carries the same title.
4

Create Task Label

Action

In Zapier“Creates a new task label.”

Puts a label on a task, which is how you tag work from outside MeisterTask without opening the board.

When to use it
a support ticket escalates and the matching task should carry the Escalated label at once.
Watch out
paired with the New Task Label trigger in the same account, this action can make a Zap restart itself.
5

Update Task

Action

In Zapier“Updates an existing task.”

Changes a task that already exists instead of making a new one. It keeps the board in step with what happens in your other tools.

When to use it
an invoice gets paid and the matching delivery task should change to reflect it.
Watch out
Task ID is required, so in practice Find Task usually runs just before it.
Searches

MeisterTask searches on Zapier

4 search steps look for data that already exists in MeisterTask, so a later step can use it.

A search step finds something that already lives in MeisterTask and hands it to the next steps. In the editor, the searches sit at the bottom of the Action event list under the SEARCH heading. Three of them also come as a find or create variant, which is the same search with one box ticked, not an extra operation.

1

Find Attachment

SearchFind or create

In Zapier“Finds an attachment by searching.”

Looks for a file that is already attached in MeisterTask, so a later step can reuse it rather than upload a copy.

When to use it
before attaching a contract, check that it is not on the task already.
Watch out
the editor also shows Find or Create Attachment; it is this same search with the creation box ticked, and it adds the file when nothing matches.
2

Find Person

Search

In Zapier“Find a person based on a person_id. Can be used to match a tasks assignee to a person name.”

Turns a person ID into the person behind it, which is how you match the assignee of a task to a name.

When to use it
a task alert should say who owns the task, readable by a human.
Watch out
Person Id is required, so it only works after a step that carried that ID.
3

Find Label

SearchFind or create

In Zapier“Finds a label by searching.”

Finds a label that already exists, so you tag tasks with the real one instead of creating a twin.

When to use it
a Zap tags tasks by client name and must reuse the existing client label.
Watch out
its Find or Create Label variant is the same search; with the box ticked it creates the label when it is missing, so no duplicate piles up.
4

Find Task

SearchFind or create

In Zapier“Finds a task by searching.”

Locates an existing task so the following steps can change it, label it or attach something to it.

When to use it
it is the step that hands Update Task the Task ID it requires.
Watch out
Find or Create Task is this same search with creation switched on, which avoids a dead end when the task does not exist yet.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Tick it and the search becomes a find or create: it drops the setting above and asks for the fields needed to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on.
When it breaks

When a MeisterTask Zap breaks

Zapier attaches no help article to MeisterTask, so the failures worth knowing are the ones every Zap shares.

  • Old tasks are never picked up

    A Zap only reacts to what happens after it is switched on. The tasks, comments and projects already in MeisterTask stay out of it; moving that backlog is a separate job.

  • The Zap that feeds itself

    A Zap on New Task that runs Create Task in the same project sets itself off again and again, and burns through your task count fast. Put a filter in between.

  • Bulk imports get held back

    After a migration or a big import, a trigger can suddenly return a huge batch. Zapier's flood protection may hold it back instead of running every item.

  • No double runs on polling

    On the five polling triggers, Zapier remembers what it has already seen, so the same task or comment does not start the Zap twice.
Need help

Need help automating MeisterTask with Zapier?

A person reads every message.

FAQ

MeisterTask Zapier integration: your questions

01Is the MeisterTask Zapier integration free?
Yes, on the free plan, because MeisterTask is not a premium app. The free plan gives you 100 tasks a month and as many Zaps as you like, but each Zap stops at two steps: one trigger and one action. As soon as you add a filter, a search such as Find Task, or a second action, the Zap becomes multi-step and needs a paid plan. With MeisterTask it matters early, since Update Task needs a Task ID that Find Task usually supplies.
02How many Zapier tasks does a MeisterTask Zap use?
One per action that succeeds, and nothing for the trigger. A Zap that watches New Project and runs Create Task uses one task each time a project appears. If it also runs Create Task Label, that run costs two. Checking MeisterTask for new items costs nothing, however often Zapier looks, and an action that fails is not counted. A few apps and actions take more than one task, so keep an eye on the history of your first runs.
03Is MeisterTask on Zapier real time?
Four triggers are, five are not. New Attachment, New Project, New Label and New Task Label are instant: MeisterTask tells Zapier the moment the event happens, whatever your plan. New Checklist Item, New Person, New Section, New Comment and New Task are polling triggers, checked every 15 minutes on the free plan, every 2 on Professional and every minute on Team and Enterprise. If speed matters on a free plan, build on one of the four instant triggers.
04What does it take to connect MeisterTask to Zapier?
A MeisterTask account, plus read or write access to the projects you want the Zap to touch, including those you do not own. You add it from the Apps page of Zapier with + Add connection, sign in to MeisterTask in the tab that opens and grant access. The connection is then saved once and reused by every MeisterTask step of every Zap. Connect the account that actually works on those boards, since several triggers ask you to pick a project during setup.
05Why does New Task ignore updated tasks?
Because of one setting. New Task has a choice called Trigger On Updated Tasks Instead of New Tasks? that works either way, never both. Set to no, the Zap fires on newly created tasks only and ignores edits. Set to yes, it fires only when an existing task changes, and fresh tasks no longer start it. If you need both behaviors, build two Zaps on the same trigger with opposite settings, each one with its own action.
06What if the MeisterTask operation you need is not on Zapier?
Then the Zap cannot do it directly. Zapier lists 5 actions and 4 searches for MeisterTask: create a task, an attachment, a label or a task label, update a task, and find attachments, people, labels or tasks. There is nothing to delete a task, archive a project or remove a person. Check the full list first, because a search followed by Update Task covers more cases than it seems, then consider another platform for the missing step.
07Zapier, Make or n8n for MeisterTask?
It depends on your criteria, not on a winner. On Zapier, MeisterTask works on the free plan, within two-step Zaps and 100 tasks a month, and this page lists every operation you get: 9 triggers, 5 actions and 4 searches. Before choosing, write down the job you need done, check that each step exists as an operation on the platform you consider, then compare how each one bills a run of that workflow and who on your team will maintain it. The same app has its own page on Make, so the comparison can be done operation by operation.
Same platform

Other docs you might need on this stack.

Browse all integrations