MeisterTask

Connect AI agents to MeisterTask kanban boards. Agents create projects and tasks, move work between sections, update status and checklist items, and read project members to route assignments.

10 actions API key available

MeisterTask website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A client request lands through the intake form with a description and a deadline

List Sections reads the delivery board's columns and finds the Intake column

Create Task opens the task in Intake with the request details written into the notes

The team channel gets the new task with its board link, so nobody discovers it at Thursday standup

A weekly sweep runs List Tasks filtered to Open and List Checklist Items per task, flagging work that has sat in one column with no checklist movement

The project lead reviews the stalled list and rules on each task: push it forward, reassign it, or trash it deliberately

Update Task applies the rulings, moving sections, changing status, renaming where scope changed

What This Integration Enables

A kanban board is a shared picture of reality, and it is only worth having while the picture stays true. MeisterTask keeps the model honest and simple, projects hold sections, sections hold tasks, tasks hold checklists, which is exactly what makes it automatable: every piece of upkeep the board needs is a small, well-defined write. FlowRunner agents do that upkeep continuously, so the humans reading the board are reading the truth. - Create tasks in the right column the moment a form is submitted, a message is posted, or an upstream system fires - Move tasks between sections and mark them Completed as the real work progresses elsewhere - Read checklist progress to distinguish tasks that are moving from tasks that are merely open - Resolve project members and their person IDs so assignment lands on the right human - Export tasks, progress, and membership into spreadsheets and digests for reporting

Without FlowRunner

The board lags reality Work finishes in email and chat, the card stays in Doing, and the board becomes a diplomatic fiction

Intake through the side door Requests arrive by DM and hallway, and the ones that never became cards are the ones that blow up later

Stalled work hides in plain sight A card sits untouched for three weeks and nobody notices, because nobody audits columns by hand

With FlowRunner

Cards move when the work moves Upstream events create tasks and completion events close them, so the columns describe this week, not last month

One intake, everything carded Forms, messages, and system events all land in the intake column with context in the notes

Stalling gets surfaced weekly The sweep names what has not moved, and a person decides what that means

Use Case Scenarios

The intake column that fills itself

New submissions arrive from [Typeform](/integrations/typeform). For each, the agent resolves the right project with List Projects, reads its columns with List Sections, and calls Create Task in the Intake section with the requester, the ask, and the deadline in the notes. List Project Members supplies the person ID for the teammate who owns that request type. A [Slack](/integrations/slack) message announces the card. The request existed for thirty seconds before it had a home on the board.

The daily status report nobody writes

Each morning the agent calls List Tasks filtered to Open for the delivery project, then List Checklist Items for each task to compute subtask progress. The result lands in [Google Sheets](/integrations/google-sheets) as a status snapshot: task, column, assignee, checklist completion. Over a week, those snapshots become a movement history the retro can actually use, which cards flowed, which cards sat, without anyone reconstructing the sprint from memory.

The card that closes itself when the work ships

A deliverable finishes upstream: the pull request merges, the invoice sends, the campaign goes live. The agent finds the corresponding card with List Tasks, confirms it with Get Task, and calls Update Task to move it to the Done section and mark it Completed. A completion note posts to the team channel. The board's Done column stops being aspirational and starts being a log.

Human-in-Loop Highlight

Update Task can set a task's status to Trashed, and that is the write the weekly sweep never performs on its own authority. A trashed card is not just a row removed; it is a request someone made, with context in its notes and history in its checklist, disappearing from the shared picture. The sweep agent flags the candidates, the card untouched for three weeks, the duplicate intake, the request overtaken by events, and presents them with their notes and checklist state attached. The project lead names what actually dies. Cards move to Done at machine speed all week; nothing leaves the board without a person deciding it should.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

10 actions

Projects

List Projects Lists the projects accessible to the authenticated user, optionally filtered by Active, Archived, or Trashed lifecycle status. The starting read for any cross-board workflow.
Get Project Retrieves a single project by numeric ID with its name, status, token, and timestamps. Used to confirm the target before writes.
Create Project Creates a new project with the given name, owned by the authenticated user. The step that gives a new engagement or initiative its own board.
List Project Members Lists a project's members with id, name, email, and role. The lookup that turns "whoever owns onboarding" into the person ID assignment requires.

Sections

List Sections Lists a project's sections, the kanban columns, in board order with id, name, and sequence. Required before creating tasks, since every task lives in a column.

Tasks

List Tasks Lists tasks within a project, optionally filtered by Open, Completed, Trashed, or Archived status. The read behind sweeps, reports, and card lookups.
Get Task Retrieves a single task by numeric ID, including name, notes, section, status, assignee, and timestamps. The confirmation step before any card is moved or closed.
Create Task Creates a task inside a specific section of a project, with a name and optional notes. The write that turns an inbound request into a card.
Update Task Updates a task by ID: rename it, change its status, or move it to a different section, touching only the fields provided. The action this page's human gate governs when the status in question is Trashed.
List Checklist Items Lists a task's checklist items with name and completion state. The signal that separates a task in motion from a task merely marked Open.

Frequently Asked Questions

What can FlowRunner do with MeisterTask?

FlowRunner agents can run List Projects, Get Project, and Create Project in MeisterTask, plus 7 more actions.

Does connecting MeisterTask to FlowRunner require OAuth?

No. MeisterTask connects to FlowRunner with an API key, no OAuth flow required.

Can MeisterTask trigger a FlowRunner workflow automatically?

MeisterTask doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with MeisterTask

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us