ActionFlowLuUpdated September 2026

How do I list FlowLu tasks?

Short answer: You can list flowlu tasks in FlowLu by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the FlowLu List FlowLu Tasks action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List FlowLu Tasks in FlowLu — start free All 4 FlowLu actions

List FlowLu Tasks in FlowLu — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Page page	string	Optional	Page number for pagination
Project ID project_id	string	Optional	Filter tasks by project ID

Sample request

{
  "page": "1",
  "project_id": "e.g. 10"
}

Returns

{
  "items": [
    {
      "id": 101,
      "name": "Design mockups",
      "status": 1,
      "due_date": "2025-04-01",
      "priority": 2,
      "project_id": 10,
      "assignee_id": 5,
      "description": "Create UI mockups for the landing page",
      "created_date": "2025-03-01 09:00:00"
    }
  ],
  "total": 25
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List FlowLu Tasks.

Any of these apps can fire this action as part of a workflow.

Google Sheets → FlowLu

2 Google Sheets triggers

HubSpot → FlowLu

18 HubSpot triggers

FAQ

Questions about List FlowLu Tasks.

What does the List FlowLu Tasks action do in FlowLu?

Paginated tasks across projects with filters by assignee, status, project. Useful for "what's on my plate today" or "all overdue tasks" reporting workflows.

What inputs does List FlowLu Tasks require?

List FlowLu Tasks has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if FlowLu returns an error?

The run history shows the failed step with its input and the error message FlowLu returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List FlowLu Tasks support batch operations?

Run List FlowLu Tasks inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within FlowLu's rate limits.

More actions

Other FlowLu actions.

Action

Create FlowLu Contact

Adds a new contact to the FlowLu CRM with name, email, organisation reference, custom fields. For "form submission → push to FlowLu" sync workflows.

Action

Create FlowLu Task

Creates a task with assignee, due date, project link. For "external event → create task in FlowLu" workflows tying external systems to FlowLu's project management.

Action

List FlowLu Contacts

Paginated contacts with filters. For sync workflows that mirror FlowLu CRM data to external reporting or warehouse systems.

List FlowLu Tasks in FlowLu — start free