ChatGPT Plugin

Flying Donut

Plan and track agile work

Brand: Flying Donut

Category: Productivity
Primary Subcategory: Pending

Integration details

Description

Flying Donut is a Scrum and Kanban tool for agile teams. Connect it to ChatGPT to work with your Flying Donut projects in conversation. What ChatGPT can do: - Find projects, their members and labels - Review sprints, the backlog and backlog buckets, and look up cards and tasks by their number (for example WEB-12) - Create cards and tasks, update them, and move them between the backlog, sprints and board lanes - Assign and unassign people, block and unblock cards, add or remove labels, and log time on tasks - Create, update and start sprints - Delete cards, tasks and labels, if you allow it You stay in control. When you connect, you sign in to Flying Donut, choose which projects ChatGPT may use, and choose which permissions to grant: read projects, read work, change work, delete work. ChatGPT can only do what your own Flying Donut role allows in those projects, and projects you join later are not added. ChatGPT asks before it changes anything. You can review or revoke the connection at any time in Flying Donut under Account, Connected apps. Requires a Flying Donut account (flyingdonut.io).

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Productivity
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Flying Donut
Access: Account required
First tracked: 2026-11-04
Tool count: 39
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Flying Donut has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

39 tools agents can invoke

Apply one or more existing labels to a card by label text, matched case-insensitively within the card's project. Never creates labels; unknown, ambiguous, disabled, and runtime labels are rejected, and one invalid label rejects the whole request. Applying an already-applied label is a no-op. The change is limited by the invoking user's Flying Donut token permissions.
Assign a user to a card. Omit username to assign the user the token acts for (for requests like "assign me"); service-account tokens must pass a username. Service-account users cannot be assigned. The user must have write access to the project (read access is enough for followers). Set follower to true to make the user follow the card instead of being assigned to it. When the user names someone by name or nickname rather than an exact username (for example "josh"), first call flying_donut_list_project_members with the project's ID and that name as query. Use the returned username only when there is a single match or one clearly best exact match; otherwise ask the user which member they mean, and never guess. For followers, look the name up with access READ, because read-only members can follow cards. The change is limited by the invoking user's Flying Donut token permissions.
Assign a user to a task. Omit username to assign the user the token acts for (for requests like "assign me"); service-account tokens must pass a username. Tasks do not support followers, and service-account users cannot be assigned. The user must have write access to the project. When the user names someone by name or nickname rather than an exact username (for example "josh"), first call flying_donut_list_project_members with the project's ID and that name as query. Use the returned username only when there is a single match or one clearly best exact match; otherwise ask the user which member they mean, and never guess. The change is limited by the invoking user's Flying Donut token permissions.
Mark a card as blocked. The change is limited by the invoking user's Flying Donut token permissions.
Create a named backlog bucket in a project. The change is limited by the invoking user's Flying Donut token permissions.
Create a card in the specified backlog bucket. The change is limited by the invoking user's Flying Donut token permissions.
Create a project label. Text must be unique case-insensitively among the project's visible labels. The change is limited by the invoking user's Flying Donut token permissions.
Create a sprint in a project. Not supported for KANBAN projects, which have a single permanent board iteration instead of plannable sprints. The change is limited by the invoking user's Flying Donut token permissions.
Create a card in the specified sprint. In KANBAN projects (project method KANBAN) the project has exactly one active board iteration, identified by the project's kanbanBoardId (state DOING, no dates); use it as the sprintId for board work. Any other sprints in a KANBAN project are archived sprints from before the project switched to Kanban. The change is limited by the invoking user's Flying Donut token permissions.
Create a task beneath the specified card with an initial workflow state. The change is limited by the invoking user's Flying Donut token permissions.
Permanently delete the specified card. The change is limited by the invoking user's Flying Donut token permissions.
Permanently delete a project label by label ID. Cards that carried it no longer return its text. Backlog-bucket labels cannot be deleted. The change is limited by the invoking user's Flying Donut token permissions.
Permanently delete the specified task. The change is limited by the invoking user's Flying Donut token permissions.
Get one card by its globally unique Flying Donut ID. Each returned card includes cid, the project-scoped identifier users reference (for example, #1); use the card's opaque id for cardId tool parameters. Responses also include blocked status, assignees as usernames, taskAssignees for task-derived assignments, and task rollups (taskCounters, taskEstimate in hours, taskRemaining in hours, taskTimeTrack in hours), and labels as an array of label text strings ([] when none). rank is the card's board rank: compare ranks as strings, lower comes first among cards in the same sprint lane or backlog bucket (null when never ranked). It is read-only; change it with flying_donut_move_card. Returned data is scoped to the invoking user's Flying Donut token permissions.
Get one card by project ID and project-scoped CID (for example, 42 or FD-42). Each returned card includes cid, the project-scoped identifier users reference (for example, #1); use the card's opaque id for cardId tool parameters. Responses also include blocked status, assignees as usernames, taskAssignees for task-derived assignments, and task rollups (taskCounters, taskEstimate in hours, taskRemaining in hours, taskTimeTrack in hours), and labels as an array of label text strings ([] when none). rank is the card's board rank: compare ranks as strings, lower comes first among cards in the same sprint lane or backlog bucket (null when never ranked). It is read-only; change it with flying_donut_move_card. Returned data is scoped to the invoking user's Flying Donut token permissions.
Get one Flying Donut project, including its lanes, method (SCRUM, SCRUMBAN or KANBAN), and kanbanBoardId. In KANBAN projects (project method KANBAN) the project has exactly one active board iteration, identified by the project's kanbanBoardId (state DOING, no dates); use it as the sprintId for board work. Any other sprints in a KANBAN project are archived sprints from before the project switched to Kanban. Returned data is scoped to the invoking user's Flying Donut token permissions.
Get one sprint by its globally unique Flying Donut ID. Returned data is scoped to the invoking user's Flying Donut token permissions.
Get one task by its globally unique Flying Donut ID. Each returned task includes cid, the project-scoped identifier users reference (for example, #2); use the task's opaque id for taskId tool parameters. Responses also include assignees as usernames. rank is the task's board rank: compare ranks as strings, lower comes first among the card's tasks in the same state (null when never ranked). It is read-only; change it with flying_donut_move_task. Returned data is scoped to the invoking user's Flying Donut token permissions.
Get one task by project ID and project-scoped CID (for example, 43 or FD-43). Each returned task includes cid, the project-scoped identifier users reference (for example, #2); use the task's opaque id for taskId tool parameters. Responses also include assignees as usernames. rank is the task's board rank: compare ranks as strings, lower comes first among the card's tasks in the same state (null when never ranked). It is read-only; change it with flying_donut_move_task. Returned data is scoped to the invoking user's Flying Donut token permissions.
List the documented bounded page of backlog buckets in a Flying Donut project. Returned data is scoped to the invoking user's Flying Donut token permissions.
List a bounded page of tasks under a Flying Donut card. Never fetches additional pages implicitly. Results are returned in board order (ascending rank, then id), so the listing reflects the order shown on the board. Each returned task includes cid, the project-scoped identifier users reference (for example, #2); use the task's opaque id for taskId tool parameters. Responses also include assignees as usernames. rank is the task's board rank: compare ranks as strings, lower comes first among the card's tasks in the same state (null when never ranked). It is read-only; change it with flying_donut_move_task. Returned data is scoped to the invoking user's Flying Donut token permissions.
List a bounded card page from exactly one context: a project's backlog, a backlog bucket, or a sprint. laneId is supported only for sprint cards. Never fetches additional pages implicitly. Results are returned in board order (ascending rank, then id), so the listing reflects the order shown on the board. In KANBAN projects (project method KANBAN) the project has exactly one active board iteration, identified by the project's kanbanBoardId (state DOING, no dates); use it as the sprintId for board work. Any other sprints in a KANBAN project are archived sprints from before the project switched to Kanban. Each returned card includes cid, the project-scoped identifier users reference (for example, #1); use the card's opaque id for cardId tool parameters. Responses also include blocked status, assignees as usernames, taskAssignees for task-derived assignments, and task rollups (taskCounters, taskEstimate in hours, taskRemaining in hours, taskTimeTrack in hours), and labels as an array of label text strings ([] when none). rank is the card's board rank: compare ranks as strings, lower comes first among cards in the same sprint lane or backlog bucket (null when never ranked). It is read-only; change it with flying_donut_move_card. Returned data is scoped to the invoking user's Flying Donut token permissions.
List the labels that can be applied to cards in a Flying Donut project, with id, text, color, and disabled. Backlog-bucket labels appear only when the project shows buckets as labels; runtime labels are never listed. Returned data is scoped to the invoking user's Flying Donut token permissions.
Find people in a Flying Donut project, directly or through a workspace, to turn a name such as "josh" into the username that assign/unassign tools need. Returns username, firstName, lastName, displayName, access (WRITE or READ) and currentUser. Matching is case- and accent-insensitive on username, first, last and full name; every query word must match. Results are ordered best match first: exact username, exact name, name prefix, then substring. By default only WRITE members, who can be assigned to cards and tasks, are returned; pass access READ to include read-only members, who can only follow cards. Service accounts are never listed. Never fetches additional pages implicitly. Returned data is scoped to the invoking user's Flying Donut token permissions.
List a bounded page of Flying Donut projects. Never fetches additional pages implicitly. Returned data is scoped to the invoking user's Flying Donut token permissions.
List a bounded page of sprints in a Flying Donut project. Never fetches additional pages implicitly. In KANBAN projects (project method KANBAN) the project has exactly one active board iteration, identified by the project's kanbanBoardId (state DOING, no dates); use it as the sprintId for board work. Any other sprints in a KANBAN project are archived sprints from before the project switched to Kanban. Returned data is scoped to the invoking user's Flying Donut token permissions.
Move a card to exactly one sprint or backlog bucket with an explicit position. The returned rank reflects the new placement; to confirm it relative to other items, compare ranks or list the collection, which is returned in board order. In KANBAN projects (project method KANBAN) the project has exactly one active board iteration, identified by the project's kanbanBoardId (state DOING, no dates); use it as the sprintId for board work. Any other sprints in a KANBAN project are archived sprints from before the project switched to Kanban. The change is limited by the invoking user's Flying Donut token permissions.
Move a task to a workflow state with an optional explicit placement. The returned rank reflects the new placement; to confirm it relative to other items, compare ranks or list the collection, which is returned in board order. The change is limited by the invoking user's Flying Donut token permissions.
Remove one or more labels from a card by label text, matched case-insensitively within the card's project. Removing a label that is not applied is a no-op; applied disabled labels can be removed. Unknown or ambiguous labels reject the whole request. The change is limited by the invoking user's Flying Donut token permissions.
Start a TODO sprint using its stored start and end dates, transitioning it to DOING. Not supported for KANBAN projects, which have a single permanent board iteration instead of plannable sprints. The change is limited by the invoking user's Flying Donut token permissions.
Remove a card assignment. Omit username to unassign the user the token acts for (for requests like "unassign me"); service-account tokens must pass a username. Service-account users cannot be assigned. Set follower to true to stop the user following the card. When the user names someone by name or nickname rather than an exact username (for example "josh"), first call flying_donut_list_project_members with the project's ID and that name as query. Use the returned username only when there is a single match or one clearly best exact match; otherwise ask the user which member they mean, and never guess. For followers, look the name up with access READ, because read-only members can follow cards. The change is limited by the invoking user's Flying Donut token permissions.
Remove a task assignment. Omit username to unassign the user the token acts for (for requests like "unassign me"); service-account tokens must pass a username. Tasks do not support followers, and service-account users cannot be assigned. When the user names someone by name or nickname rather than an exact username (for example "josh"), first call flying_donut_list_project_members with the project's ID and that name as query. Use the returned username only when there is a single match or one clearly best exact match; otherwise ask the user which member they mean, and never guess. The change is limited by the invoking user's Flying Donut token permissions.
Clear the blocked state for a card. The change is limited by the invoking user's Flying Donut token permissions.
Update supplied card fields; omitted fields remain unchanged. The change is limited by the invoking user's Flying Donut token permissions.
Update a project label's text, color, or disabled state; omitted fields remain unchanged. An empty color clears it. Renaming keeps the label id and its card assignments. Backlog-bucket label text follows the bucket title and cannot be changed. The change is limited by the invoking user's Flying Donut token permissions.
Update supplied sprint fields; omitted fields remain unchanged. The change is limited by the invoking user's Flying Donut token permissions.
Update supplied task fields; omitted fields remain unchanged. The change is limited by the invoking user's Flying Donut token permissions.
Append a non-negative time-remaining entry to a task. The change is limited by the invoking user's Flying Donut token permissions.
Append a non-negative time-spent entry (hours) to a task. The change is limited by the invoking user's Flying Donut token permissions.

FAQs

Flying Donut ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Flying Donut's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.