ActionFolkUpdated September 2026

What groups exist in Folk?

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

List Folk Groups in Folk — start free
Sample request
{}
Returns
{
"data": [
{
"id": "group_abc",
"name": "Investors"
},
{
"id": "group_xyz",
"name": "Customers"
}
]
}

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

Triggered by

Apps that pair well as the trigger for List Folk Groups.

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

FAQ

Questions about List Folk Groups.

What does the List Folk Groups action do in Folk?
Returns every group (Folk's list/segment construct) with name and member count. Useful for resolving group IDs at workflow setup.
What inputs does List Folk Groups require?
List Folk Groups 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 Folk returns an error?
The run history shows the failed step with its input and the error message Folk 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 Folk Groups support batch operations?
Run List Folk Groups 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 Folk's rate limits.
More actions

Other Folk actions.

List Folk Groups in Folk — start free