Short answer: Drop the "JotForm → List JotForms" 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 |
|---|---|---|---|
Limit limit | string | Optional | Limit. e.g. "20" |
Offset offset | string | Optional | Offset. e.g. "0" |
Filter filter | string | Optional | Filter by status |
{"limit": "20","offset": "0","filter": "e.g. {\"status:eq\":\"ENABLED\"}"}
{"content": [{"id": "240123456789","count": "42","title": "Contact Form","status": "ENABLED"}],"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.