List Plutio Projects: Plutio 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
Status status	string	Optional	Filter by project status

Sample request

{
  "status": "active"
}

Returns

{
  "data": [
    {
      "_id": "abc123",
      "title": "Website Redesign",
      "client": "Acme Corp",
      "status": "active",
      "dueDate": "2025-06-30",
      "createdAt": "2025-01-10T10:00:00Z",
      "description": "Redesign the company website"
    }
  ]
}

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

FAQ

Questions about List Plutio Projects.

What does the List Plutio Projects action do in Plutio?

Paginated projects with filters by client and status. For "all active client projects" rollup workflows.

What inputs does List Plutio Projects require?

List Plutio Projects 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 Plutio 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 Plutio Projects support batch operations?

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

More actions