Summary
Customer information collected through Jotform form submissions can be transferred to iPaaS.com as Customer records, with Customer Address and Customer Category child records, through a webhook-triggered sync. Because each Jotform form defines its own fields, the field mappings are created by the subscriber for each form rather than shipped as a fixed set.
ID Format
Manual Sync ID Format
To sync a submission manually, use the Jotform submission id.
Pattern: the numeric submission id
Example:
6295257860227569604
External ID Format
After a sync, the external id stored in iPaaS.com is the submission content id followed by a record index suffix.
Pattern:
{ContentId}|{index}Example:
6295257860227569604|1
Custom Field Support
Because a Jotform form's fields are unique to that form, the values are transferred to iPaaS.com as custom fields. To map them, create matching custom fields in iPaaS.com and reference them in your mapping collection.
Accessing Field Names in Jotform
Once the form is complete, edit the form and, for each field:
Open the settings for that field.
Click Advanced.
Under field details, note the Unique Name. This value is what you map in iPaaS.com.
Some fields contain multiple values under one Unique Name. For a full-name field, for example, the iPaaS.com field for the first name would be
fullname3.first_3; the combined value would befullname3.
Advanced: if values are not transferring using the field IDs, review the debug logs for a manual transfer to determine the field names. In the example answer below:
"3": { "name": "fullName", "order": "3", "sublabels": { "prefix": "Prefix", "first": "First Name", "middle": "Middle Name", "last": "Last Name", "suffix": "Suffix" }, "text": "Full Name", "type": "control_fullname", "answer": { "first": "John", "last": "Smith" }, "prettyFormat": "John Smith" }the field name paths used would be fullName.first and fullName.last.
Adding Custom Fields in the Jotform Subscription in iPaaS.com
Navigate to Subscriptions Management → Subscriptions.
Under your Jotform subscription, open the Custom Fields tab.
Add a custom field:
Name: one of the field names identified above.
Module: Customers, Customer Categories, or Customer Address, depending on where the data should map.
Repeat for each field you want to map. Field names are case sensitive and must match what you see in Jotform exactly.
How values are extracted
Checkbox (multi-select) answers are combined into a single comma-separated value.
Full-name, address, and phone answers are split into their component custom fields and also provided as a combined value.
When a value cannot be extracted for a field, the submission's pretty-formatted value is used.
Mapping Collection Status
Status: Enabled
Trigger Events: Jotform form submission (the
customer/createdwebhook)
Supported Child Collections
Parent Collection: Customer
Child Collections: Customer Address, Customer Category
The same submission populates the parent Customer record and its Customer Address and Customer Category child records.
System Caveats
Jotform Caveats
Field Unique Names are case sensitive and differ from form to form.
Jotform does not support enabling webhooks through its API; the webhook must be added manually (see the Connections and Settings document).
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). See Jotform's API documentation.
iPaaS.com Caveats
Custom fields must be created in iPaaS.com before they can be mapped, and their names must match the Jotform field names exactly (case sensitive).
Mappings are defined by the subscriber for each form; there is no fixed, shipped set of field mappings for this integration.
Integration-Specific Caveats
To map more than one form, filter the Customer mapping collection on the ContentFormId field, which holds the Jotform form id.
Integration Flow
A visitor submits a Jotform form.
Jotform sends the
customer/createdwebhook to iPaaS.com.iPaaS.com retrieves the submission from Jotform.
Each submission answer is written to the mapped iPaaS.com custom field.
The Customer record is created or updated, along with its Customer Address and Customer Category child records. When the email-link option is configured, an existing iPaaS.com customer with a matching email is updated instead of creating a duplicate.
Mappings
This integration does not ship a fixed set of field mappings. Subscribers create a Customer mapping collection (TO iPaaS.com) for each Jotform form and add the custom fields they want to map, then add Customer Address and Customer Category child collections as needed. Map each Jotform field's Unique Name to the corresponding iPaaS.com Customer, Customer Address, or Customer Category field.
To map multiple forms, repeat the process per form and filter each collection on ContentFormId.
Testing & Validation
Test Scenarios
Submit a new Jotform form entry and verify a Customer record is created in iPaaS.com with the mapped values.
Submit an entry for an existing customer (same email) and verify the existing record is updated rather than duplicated.
Submit an entry that includes address and category fields and verify the Customer Address and Customer Category child records are populated.
Submit an entry from a second form and verify the ContentFormId filter routes it correctly.
Validation Checklist
Custom field names in iPaaS.com match the Jotform Unique Names exactly.
The webhook URL uses the
customer/createdscope, URL-encoded.The mapped values appear on the correct module (Customer, Customer Address, or Customer Category).
Additional Notes
If a form's values are not transferring as expected, review the debug logs for a manual transfer to confirm the exact field name paths, as described under Custom Field Support.