JotForm Integration
JotForm offers the ability to create professional-looking for with no coding. You can style the form with your own logo, fonts and colors. You can use the forms to do things like collect payments. Once you have your JotForm, you can integrate it with your system to add the contacts and trigger Workflows.
1. Create a Workflow in AllClients
Create a Workflow in AllClients, enable the Trigger and copy the URL Trigger URL.
2. Create a JotForm Form
When adding the Form Elements, do not use the Address field. Use text fields and map each element to the database individually.
Don't Use
These form elements don't integrate and we do not recommend you use them in your form:
- Multiple Choice
- Input Table
- Signature
- File Upload
- Product List
- Star Rating
3. Map Fields to the database.
Name and Email will automatically map.
For other fields, you will need to set a parameter to tell us where to put the data.
While on the field you want to map, click the cog icon to go to Field Settings for the Mapping.
4. Go to ADVANCED.
5. Open Field Details and enter the matching database field from the Field Names.
Form Fields
These are the fields you can map to. Use the Field Name as the Unique Name.
| Field | Max Length* | Required | Notes |
| 75 | Recommended | Duplicates will be determined by PRIMARY email address. If a duplicate is found, the OLDEST record with the matching PRIMARY email will be used. What occurs when a duplicate is encounterd is defined in the Trigger. Email address will be automatically opted in. | |
| firstname | 50 | Conditional | Recommended. A period charcter will be put in place if empty field is submitted |
| lastname | 50 | No | Recommended. A period charcter will be put in place if empty field is submitted |
| fullname | 50 | Conditional | Special Field: If submitted, we will override firstname and lastname and attempt to automatically split the fullname into the firstname and lastname fields |
| birthday | 10 | No | Birthday year is optional. Use only formats MM/DD or MM/DD/YYYY. Zero pad leading digits, so month and day are always 2 digits. January 5th is 01/05. |
| otherfirstname | 50 | No | |
| otherlastname | 50 | No | |
| otherbirthday | 10 | No | Birthday year is optional. Use only formats MM/DD or MM/DD/YYYY. Zero pad leading digits, so month and day are always 2 digits. January 5th is 01/05. |
| company | 50 | No | |
| address | 50 | No | |
| city | 50 | No | |
| state | 20 | No | Recommended that this be the 2 digit state code for US addresses |
| postalcode | 20 | No | |
| phone1 | 20 | No | Will automatically be formatted to (xxx) xxx-xxxx |
| phone1note | 20 | No | Recommended that description is used if known (work, home, mobile, etc…) |
| phone1textoptin | 1 | No | Use value of "1" to opt in Phone 1 for texting |
| phone2 | 20 | No | Will automatically be formatted to (xxx) xxx-xxxx |
| phone2note | 20 | No | |
| phone2textoptin | 1 | No | Use value of "1" to opt in Phone 2 for texting |
| phone3 | 20 | No | Will automatically be formatted to (xxx) xxx-xxxx |
| phone3textoptin | 1 | No | Use value of "1" to opt in Phone 3 for texting |
| phone3note | 20 | No | |
| phone4 | 20 | No | Will automatically be formatted to (xxx) xxx-xxxx |
| phone4note | 20 | No | |
| phone4textoptin | 1 | No | Use value of "1" to opt in Phone 4 for texting |
| fax | 20 | No | Will automatically be formatted to (xxx) xxx-xxxx |
| otheremail | 75 | No | |
| custom1 | 50 | No | Recommended that you only use custom fields when user’s exact custom field mapping is known |
| … | … | … | Custom 1 through 40 |
| custom40 | 50 | No | |
| memo | 50 | No | Brief memo for contact. This is not a note, but a brief memo that shows up on the contact’s page. Recommended less than 100 characters. |
| category | 50 | No | Must match the name of an existing Category exactly. Any mismatch will result in the category not being assigned. |
| category2 | 50 | No | Must match the name of an existing Category2 exactly. Any mismatch will result in the category2 not being assigned. (This is the customizable category) |
| source | 50 | No | Must match the name of an existing Source exactly. Any mismatch will result in the source not being assigned. |
| othersystemid | 32 | No | For tracking the ID of this contact in another system |
| teammemberid | No | Must be the internal ID for a team member that owns a database inside of the matching account for the trigger. (Advanced use only) | |
| addednote | No | When a contact is ADDED via the API, a note is added to the contact record. The default is “Contact Added via API”. You can override the default note with this field. | |
| updatednote | No | When a contact is UPDATED, this note is added to the contact record. |
* An error will not result if Max Length is exceeded. Data will be trimmed to this length.
Set Up Integration.
6. Once all the fields are mapped properly, go to the JOTFORM FORM SETTINGS and INTEGRATIONS.
7.Search for WebHooks and select it.
8. Add your Workflow Trigger URL and click COMPLETE INTEGRATION.
Test your Integration.
9. Test Results
When the contact is added to AllClients successfully, you will see notes including the raw JotForm data so you can see all the data.
If you are editing your JotForm, you will want to test all aspects of the integration again. In some cases, changing your JotForm will cause the integration to stop triggering the Workflow. You will need to turn the Workflow Trigger off and turn it back on to get the link and reintegrate with the above steps.