Overview
The Jotform integration provides a ready-made function you can call when building mappings. It links a Jotform submission to the matching iPaaS.com customer by email, so you do not have to write that logic yourself in a formula.
Where you can use these functions
These functions are available anywhere you write a formula for the Jotform integration:
Dynamic Formula mappings: where a destination field's value is produced by a formula rather than mapped directly from a source field.
Mapping collection filters: where a formula decides whether a record should be processed.
Error filters: a mapping collection's error filter, which sits alongside its collection filter. When the error filter's formula resolves to true, the transfer raises an error that is held in the Error Logs for review and is not retried automatically.
Translation collections: where a translation entry uses a formula as its source value.
How to use them
Call a function by name and pass the values it needs in parentheses, for example:
LinkExternalByEmail(Email, SystemId, SubmissionId).Each function's signature shows its name, the parameters it accepts (with their types), and the type of value it returns. Use it as the reference for exactly how to call the function.
Function names and formula syntax are case-sensitive, so type each name exactly as shown. Whether the values a function matches are treated as case-sensitive varies by function, and is called out in the relevant parameter's description.
This function is synchronous, so you call it directly (no
awaitis required).The function runs at sync time, against the data in your connected Jotform account and your iPaaS.com subscription.
The functions are grouped below by the area of the integration they support.
Customers
LinkExternalByEmail
What it does: Links a Jotform submission to an existing iPaaS.com customer, matched by email, so that the transfer updates that customer instead of creating a duplicate. It looks up the iPaaS.com customer by email and, if the customer does not yet have an external ID for the Jotform system, adds one from the submission. It always returns true so it does not block a mapping collection filter, and it does not raise an error if the customer does not yet exist.
Signature: bool LinkExternalByEmail(string emailAddress, long jotformSystemId, string submissionId)
How to call it: LinkExternalByEmail(emailAddress, jotformSystemId, submissionId)
Parameter | Type | Required | Default | Description |
|
| Yes | N/A | The iPaaS.com customer email address used to look up the customer. |
|
| Yes | N/A | The identifier of the Jotform system where the external ID is stored. |
|
| Yes | N/A | The Jotform submission ID to link to the customer. |
Returns: bool. Always true, so the function never blocks the record when used in a filter.
Example: LinkExternalByEmail("john.doe@example.com", 45, "SUB12345") links submission SUB12345 to the iPaaS.com customer with that email, then returns true.
When to use it: Use this on a customer mapping collection filter so a Jotform submission is matched to the existing iPaaS.com customer by email, letting the transfer update that customer rather than create a new one.