List Projects: Wistia 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
Per Page per_page	number	Optional	Max projects per page

Sample request

{
  "per_page": "{{trigger.per_page}}"
}

Returns

[
  {
    "id": 1,
    "name": "Marketing",
    "created": "2026-01-15T10:00:00Z",
    "hashed_id": "proj_abc",
    "mediaCount": 12
  }
]

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

FAQ

Questions about List Projects.

What does the List Projects action do in Wistia?

Lists Wistia projects (folders that contain media). Use to populate a project picker before uploading or listing media.

What inputs does List Projects require?

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

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

More actions