The following are the known limitations of the Jotform integration. They are inherent to the current design and to the capabilities of the Jotform API, and they apply to all subscribers at the time this documentation was written.
Platform Scope and Tested Versions
Platform: Jotform.
API host:
https://api.jotform.com(EU accounts usehttps://eu-api.jotform.com; HIPAA accounts usehttps://hipaa-api.jotform.com; Enterprise accounts may use a custom subdomain).API version: The Jotform API is not versioned in a stable, public way. The integration was built against the documented production endpoints as of 2026-06-30, the date it was last validated.
Not built for: other form, survey, or data-collection products. If Jotform launches a separate product line or a materially different API in the future, this integration will not automatically support it.
1. Data Flows from Jotform to iPaaS.com Only
The integration is one-directional: form submissions captured in Jotform are sent to iPaaS.com. Changes made in iPaaS.com are not written back to Jotform.
What this means for you: Use Jotform as the source of customer submissions and iPaaS.com as the destination. If your workflow needs updates to flow back to Jotform, submit a feature request to your iPaaS.com partner channel describing the requirement.
2. Webhooks Must Be Configured Manually
Jotform does not support enabling webhooks through its API, so the webhook that notifies iPaaS.com of new submissions must be added by hand in each Jotform form.
What this means for you: Follow the Setting up Webhooks in Jotform procedure in the Connections and Settings document after creating the subscription. Each form you want to sync needs its own webhook.
3. Field Mappings Are Defined Per Form
Because every Jotform form defines its own fields, the integration does not ship a fixed set of field mappings. Custom fields and mappings are created by the subscriber for each form, and field names are case sensitive.
What this means for you: Create matching custom fields in iPaaS.com using the exact Jotform field Unique Names, then build a mapping collection per form, as described in the Jotform to iPaaS.com Customer Mapping Documentation document.
4. Only New-Submission Events Are Supported
The integration accepts a single webhook scope, customer/created, which fires when a form is submitted.
What this means for you: New submissions are detected when the form is submitted. Other Jotform events are not used by this integration.
5. Initialization Is Not Supported
The integration does not perform a bulk import of existing Jotform submissions when first connected.
What this means for you: Historical submissions are not back-filled automatically. Data synchronization begins with submissions received after the webhook is configured.
6. Multiple Forms Require a Form Filter
A subscription can map more than one Jotform form, but submissions from different forms share the same Customer flow.
What this means for you: When mapping multiple forms, filter each mapping collection on the ContentFormId field (the Jotform form id) so each form's submissions map to the correct fields.
7. Jotform Daily API Limits Apply
Jotform enforces a daily API request limit that varies by plan (for example, 1,000 requests per day on Starter, up to 100,000 on Gold; Enterprise has no daily limit).
What this means for you: Very high submission volume can reach the Jotform daily limit, after which requests are rejected until the limit resets. Stagger large jobs, or upgrade the Jotform plan if you regularly exceed the limit. See Jotform's API documentation for the current per-plan limits.
There are 7 known limitations described in this document.