Short answer: Drop the "JotForm → JotForm Form Submitted" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in JotForm, not on a polling schedule.
Drop it on the canvas. Configure a couple of fields. Publish.
You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"ip": "127.0.0.1","pretty": "Name: John Doe\nEmail: john@example.com","answers": {"q1_name": {"last": "Doe","first": "John"},"q2_email": "john@example.com"},"form_id": "12345","form_title": "Contact Form","submission_id": "67890","submission_source": "WEB"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| ip | string | "127.0.0.1" |
| pretty | string | "Name: John Doe Email: john@example.com" |
| answers | object | { … } |
| answers.q1_name | object | { … } |
| answers.q1_name.last | string | "Doe" |
| answers.q1_name.first | string | "John" |
| answers.q2_email | string | "john@example.com" |
| form_id | string | "12345" |
| form_title | string | "Contact Form" |
| submission_id | string | "67890" |
| submission_source | string | "WEB" |
One trigger. 4+ downstream actions. Zero glue.