Short answer: Drop the "Tally → List Submissions" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Form ID form_id | string | Required | The Form ID assigned by Tally. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Page page | string | Optional | — |
{"form_id": "{{trigger.form_id}}","page": "{{trigger.page}}"}
{"page": 1,"items": [{"id": "sub_abc","responses": [{"field": {"label": "Email"},"value": "jane@x.com"}],"submittedAt": "2026-05-11T00:00:00Z"}],"totalNumberOfSubmissionsPerFilter": 42}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.