List FlowLu Tasks: FlowLu action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List FlowLu Tasks support batch operations?

Yes. Run List FlowLu Tasks inside a Loop node to process arrays. Tiny Command handles FlowLu's rate limits automatically so you don't have to throttle manually.

More actions