ActionTallyUpdated September 2026
How do I list every Tally form in my workspace?
Short answer: You can list forms in Tally by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Tally List Forms action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 | – |
Sample request
{"page": "{{trigger.page}}"}
Returns
{"items": [{"id": "f_abc","name": "Contact Us","status": "PUBLISHED"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Forms.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Forms.
What does the List Forms action do in Tally?
Returns the forms in your Tally workspace with their IDs, names, and live URLs. Use this to populate a form picker before pulling submissions.
What inputs does List Forms require?
List Forms 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 Tally returns an error?
The run history shows the failed step with its input and the error message Tally 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 Forms support batch operations?
Run List Forms 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 Tally's rate limits.
More actions