Short answer: Drop the "JotForm → Get JotForm Schema" 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 formId | string | Required | Jotform form ID — an 18–19-digit number from the form URL. Find via List Forms. |
{"formId": "e.g. 240123456789012"}
{"content": {"id": "form123","count": 150,"title": "Contact Form","status": "ENABLED","created_at": "2026-01-01 10:00:00"}}
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.