Reference · Tools

Flow

Manage tasks in Flow (getflow.com) project management platform

Action Productivity v1

The Flow node connects your BusyBot workflows to your Flow (getflow.com) project management workspace, letting you create, update, retrieve, or list tasks programmatically. Use it to automatically create a Flow task whenever a form is submitted, a deal closes in your CRM, or a trigger fires elsewhere in your workflow. Your organization ID is pulled from credentials automatically, so you don't need to pass it manually on every step.

Node type
Action
Parameters
14
Outputs
Output, Error
Credentials
Flow API

Flow

Manage tasks in Flow (getflow.com) project management platform

Overview

Flow is a project management and task tracking application (getflow.com). This tool provides CRUD operations for tasks: create, update, get, and get many. Uses the Flow REST API v2 with Bearer token authentication. The organization ID is supplied via credentials and injected into every request automatically.

Category: Productivity
Tool Name: flow
Version: 1

Appearance: Icon: lucide-Workflow | Color: #49C7A3

Node Type

Action — processes input items and produces output

Input / Output

DirectionPort(s)
InputInput
OutputOutput, Error

Credentials

This tool requires Flow API credentials. See the Credentials Guide for setup instructions.

Resources

ResourceValue
Tasktask

Operations

Each resource has its own Operation list. Pick the resource first, then the operation.

ResourceOperationValueDescription
TaskCreatecreateCreate a new task
TaskUpdateupdateUpdate a task
TaskGetgetGet a task
TaskGet ManygetAllGet many tasks

Parameters

Task: Create

ParameterTypeRequiredDefaultDescription
Workspace IDstringYesCreate resources under the given workspace. Find this in your Flow workspace URL or settings. Supports expressions.
NamestringYesThe title of the task. Supports expressions.
Additional FieldscollectionNo{}Optional properties to set on the new task.
— Owner IDstringNoThe ID of the account to whom this task will be assigned.
— List IDstringNoPut the new task in a list (“project”). Omit this param to have the task be private.
— Starts OnstringNoThe date on which the task should start (ISO 8601 format, e.g. 2024-01-15).
— Due OnstringNoThe date on which the task should be due (ISO 8601 format, e.g. 2024-01-20).
— Mirror Parent SubscribersbooleanNofalseWhether this task will be a subtask, and this is true, the parent task’s subscribers will be mirrored to this one.
— Mirror Parent TagsbooleanNofalseWhether this task will be a subtask, and this is true, the parent task’s tags will be mirrored to this one.
— Note ContentstringNoProvide the content for the task’s note.
— Note Mime TypeoptionsNotext/plainIdentify which markup language is used to format the given note.
Options: text/plain, text/x-markdown, text/html
— Parent IDstringNoIf provided, this task will become a subtask of the given task.
— Position ListnumberNo0Determines the sort order when showing tasks in, or grouped by, a list.
— Position UpcomingnumberNo0Determines the sort order when showing tasks grouped by their due_date.
— PositionnumberNo0Determines the sort order of tasks.
— Section IDstringNoSpecify which section under which to create this task.
— TagsstringNoA list of tag names to apply to the new task separated by a comma (,).

Task: Update

ParameterTypeRequiredDefaultDescription
Workspace IDstringYesThe workspace the task belongs to. Supports expressions.
Task IDstringYesThe ID of the task to update. Supports expressions.
Update FieldscollectionNo{}Task fields to change. Only the fields you add are sent.
— NamestringNoThe title of the task.
— CompletedbooleanNofalseWhether to complete the task.
— Owner IDstringNoThe ID of the account to whom this task will be assigned.
— List IDstringNoPut the task in a list (“project”). Omit this param to have the task be private.
— Starts OnstringNoThe date on which the task should start (ISO 8601 format).
— Due OnstringNoThe date on which the task should be due (ISO 8601 format).
— Mirror Parent SubscribersbooleanNofalseWhether this task will be a subtask, and this is true, the parent task’s subscribers will be mirrored to this one.
— Mirror Parent TagsbooleanNofalseWhether this task will be a subtask, and this is true, the parent task’s tags will be mirrored to this one.
— Note ContentstringNoProvide the content for the task’s note.
— Note Mime TypeoptionsNotext/plainIdentify which markup language is used to format the given note.
Options: text/plain, text/x-markdown, text/html
— Parent IDstringNoIf provided, this task will become a subtask of the given task.
— Position ListnumberNo0Determines the sort order when showing tasks in, or grouped by, a list.
— Position UpcomingnumberNo0Determines the sort order when showing tasks grouped by their due_date.
— PositionnumberNo0Determines the sort order of tasks.
— Section IDstringNoSpecify which section under which to create this task.
— TagsstringNoA list of tag names to apply to the task separated by a comma (,).

Task: Get

ParameterTypeRequiredDefaultDescription
Task IDstringYesThe ID of the task to retrieve. Supports expressions.
FilterscollectionNo{}Optional settings for the lookup request.
— IncludemultiOptionsNo[]Related data to include in the response.
Options: schedule, files, file_associations, parent

Task: Get Many

ParameterTypeRequiredDefaultDescription
Return AllbooleanNofalseWhether to return all results or only up to a given limit.
LimitnumberNo50Max number of results to return. (shown when Return All is false)
FilterscollectionNo{}Filters and sorting applied to the task list.
— IncludemultiOptionsNo[]Related data to include in the response.
Options: schedule, files, file_associations, parent
— OrderoptionsNocreated_atField to sort results by.
Options: account_id, completed_at, created_at, due_on, list_id, name, owner_id, position, section_id, starts_on, updated_at
— Workspace IDstringNoFilter tasks by workspace.
— Created BeforestringNoSelect resources created before a certain time (ISO 8601 datetime).
— Created AfterstringNoSelect resources created after a certain time (ISO 8601 datetime).
— Updated BeforestringNoSelect resources updated before a certain time (ISO 8601 datetime).
— Updated AfterstringNoSelect resources updated after a certain time (ISO 8601 datetime).
— DeletedbooleanNofalseWhether to select deleted resources.
— ClearedbooleanNofalseWhether to select cleared resources.

All Operations

ParameterTypeRequiredDefaultDescription
Max ConcurrencynumberNo10Maximum number of items to process concurrently.

Output Data

The Flow response is merged into the output item’s JSON at the top level — the task’s fields sit alongside the fields the input item already carried, so downstream nodes address them directly ({{ $json.name }}) rather than through a wrapper property. Everything else on the item passes through, and binary data is forwarded unchanged. A response field with the same name as an existing item field overwrites it.

How many items you get back depends on the operation:

OperationOutput
create, update, getOne output item per input item, carrying the returned task’s fields.
getAllOne output item per task in the response — ask for 25 tasks and a single input item produces 25 output items. With Return All on, every page is fanned out the same way.

When Get Many matches nothing, the node still emits one item for that input, carrying _flowResult: null, so an empty result is visible downstream instead of silently dropping the branch.

Usage Examples

  • Create a new task in a Flow workspace
  • Update a task name or mark it as completed in Flow
  • Get a specific task by ID from Flow
  • List all tasks in a Flow workspace
  • Create a subtask under a parent task in Flow

Example Configuration

Create a task in a workspace, assigned and dated:

{
  "type": "flow",
  "parameters": {
    "resource": "task",
    "operation": "create",
    "workspaceId": "12345",
    "name": "{{ $json.title }}",
    "additionalFields": {
      "ownerId": "67890",
      "listId": "4321",
      "startsOn": "2026-03-01",
      "dueOn": "2026-03-15",
      "noteContent": "Raised from {{ $json.source }}",
      "noteMimeType": "text/plain",
      "tags": "intake,priority"
    }
  }
}

Create a subtask under an existing task and inherit its subscribers and tags:

{
  "type": "flow",
  "parameters": {
    "resource": "task",
    "operation": "create",
    "workspaceId": "12345",
    "name": "Sub: {{ $json.step }}",
    "additionalFields": {
      "parentId": "{{ $json.taskId }}",
      "mirrorParentSubscribers": true,
      "mirrorParentTags": true
    }
  }
}

Mark a task completed and leave a markdown note:

{
  "type": "flow",
  "parameters": {
    "resource": "task",
    "operation": "update",
    "workspaceId": "12345",
    "taskId": "{{ $json.taskId }}",
    "updateFields": {
      "completed": true,
      "noteContent": "Closed automatically at {{ $datetime.iso }}",
      "noteMimeType": "text/x-markdown"
    }
  }
}

Fetch one task together with its schedule and parent:

{
  "type": "flow",
  "parameters": {
    "resource": "task",
    "operation": "get",
    "taskId": "{{ $json.taskId }}",
    "filters": {
      "include": ["schedule", "parent"]
    }
  }
}

List the next 25 tasks in a workspace by due date, skipping deleted and cleared ones:

{
  "type": "flow",
  "parameters": {
    "resource": "task",
    "operation": "getAll",
    "returnAll": false,
    "limit": 25,
    "filters": {
      "workspaceId": "12345",
      "order": "due_on",
      "createdAfter": "2026-01-01T00:00:00Z",
      "deleted": false,
      "cleared": false,
      "include": ["files"]
    }
  }
}

Error Handling

ModeBehavior
stopHalts workflow on first error
continueSkips failed items, passes successful ones through
errorPortRoutes failed items to Error output port

Tips

Create, update, get, or list tasks in Flow (getflow.com) project management platform.

Important Notes

  1. Workspace ID: Always required for create and update operations. Find this in your Flow workspace URL or settings.
  2. Task ID: Required for update and get operations. This is returned when creating tasks or can be found in task URLs.
  3. Conditional Logic: The limit parameter only appears when returnAll is set to false.
  4. Resource Limitation: Currently only supports the “task” resource type.

Frequently asked questions

What credentials do I need, and where do I find them?

You need a Flow API credential (type: flowApi), which authenticates using a Bearer token issued by Flow. Once configured, BusyBot injects your organization ID from those credentials into every request automatically — you won't need to supply it manually in your workflow parameters.

When is the Workspace ID required, and how do I find it?

Workspace ID is required whenever you create or update a task — it is not optional for those operations. You can find it in your Flow workspace URL or in your workspace settings. Without it, create and update requests will fail, so grab it before building those steps.

How does the limit parameter work when listing tasks?

The limit parameter only appears in your workflow configuration when you have set 'returnAll' to false. If returnAll is true, the node fetches all available tasks and the limit field is hidden. Switch returnAll to false first if you want to cap the number of results returned.

What resource types does this node support?

Currently the Flow node only supports the 'task' resource type. Operations for projects, lists, workspaces, or other Flow objects are not available through this node. All four operations — create, update, get, and get many — apply specifically to tasks.

What happens if my request fails — how do I handle errors?

The node has two distinct outputs: Output and Error. A failed API call routes to the Error output rather than stopping your workflow entirely, which means you can wire up a separate branch to handle failures, log them, or send an alert without the whole workflow breaking.

Build with the Flow node

Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need Flow API credentials first.

Open BusyBot

Last updated . Spotted something wrong? Tell us.