Short answer: Drop the "JotForm → List JotForm 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 | Form ID. Example: 240123456789 |
Limit limit | string | Optional | Max submissions (max 1000) |
Offset offset | string | Optional | Offset. e.g. "0" |
Filter (JSON) filter | string | Optional | Filter submissions, e.g. {"status:eq":"ACTIVE"} |
{"form_id": "e.g. 240123456789","limit": "20","offset": "0","filter": "{{trigger.filter}}"}
{"content": [{"id": "123","answers": {"1": {"text": "Name","answer": "John Doe"},"2": {"text": "Email","answer": "john@example.com"}},"form_id": "240123456789","created_at": "2025-01-15 12:00:00"}],"responseCode": 200}
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.