Jotform

Jotform is a cloud-based form builder and data collection platform. This connector uses the Jotform REST API to read forms, submissions, reports, files, and account metadata, and to write data back by creating submissions, registering webhooks, cloning forms, and updating form properties.

Power end-to-end data operations for your Jotform API with Nexla. Our bi-directional Jotform connector is purpose-built for Jotform, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Jotform or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Jotform workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Jotform credential, you need an API key from your Jotform account. Jotform authenticates every API request with this key, which can be sent in the APIKEY request header (the method this connector uses).

To obtain your Jotform API key, follow these steps:

1. Sign in to your Jotform account.

2. Navigate to the API section of My Account, or go to My Account > API.

3. Click Create New Key to generate an API key.

4. Choose the access level for the key. Jotform supports read-only or full access; select Full Access if you intend to use this connector as a destination to write data back to Jotform.

5. Copy the generated API key and store it securely. You will enter it when creating your Nexla credential.

Your account's data center determines the base URL. Standard US accounts use https://api.jotform.com. If your account is hosted in the EU data center use https://api.eu.jotform.com, and HIPAA-compliant accounts use https://api.hipaa.jotform.com. For more details on authentication and available endpoints, see the Jotform API documentation.

Authenticate

Credentials required

Authenticate using your Jotform API key. Obtain your API key from your Jotform account settings.

Field	Required	Secret	Description
API Key Value	Yes	Yes	An encoded string value used as a secret token to authenticate API requests
Base URL	Yes	No	The base URL for the Jotform API.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Jotform API key in the API Key Value field. This key is sent in the APIKEY request header to authenticate every call to the Jotform API and must be kept confidential.

4. Enter the Base URL for your Jotform data center. This defaults to https://api.jotform.com for standard US accounts; use https://api.eu.jotform.com for EU-hosted accounts or https://api.hipaa.jotform.com for HIPAA accounts.

   Your API key grants access to your Jotform account data. If it is compromised, revoke it from the API section of My Account and generate a new one.

   For detailed information about authentication and available endpoints, see the Jotform API documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Jotform connector tile, then select the credential that will be used to connect to Jotform, and click Next; or, create a new Jotform credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Jotform endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List User Submissions

Returns a list of all submissions received across user's forms.

• This endpoint pages through account-wide submissions using an incrementing offset, so Nexla automatically retrieves all available records.

[Rest API] List User Reports

Returns a list of all reports created by the user.

[Rest API] List User Forms

Returns a list of all forms owned by the user.

[Rest API] Get Form Questions

Returns all questions contained in a specific form.

• Provide the Form ID of the form whose questions you want to retrieve.

[Rest API] Get Form Properties

Returns the properties and settings of a specific form.

• Provide the Form ID of the form whose properties you want to retrieve.

[Rest API] Get Form Files

Returns a list of all files uploaded to a specific form.

• Provide the Form ID of the form to retrieve files from.

[Rest API] Get Form by ID

Retrieve metadata and settings for a single form by ID.

• Provide the Form ID of the form to retrieve.

[Rest API] List Form Submissions

List submissions for a specific form with filtering and paging — far more targeted than the account-wide /user/submissions endpoint.

• Provide the Form ID of the form whose submissions you want to ingest. This endpoint pages through results using an incrementing offset.

[Rest API] List Form Webhooks

List all webhooks registered on a specific form.

• Provide the Form ID of the form whose webhooks you want to list.

[Rest API] Get User

Get account details for the authenticated user — useful as a connection-test / metadata source.

[Rest API] Get User Usage

Get number of form submissions received this month, SSL submissions, payment submissions, and upload space used by user.

[Rest API] Get User Settings

Get user's settings for this account including timezone, language, and notification preferences.

[Rest API] List User Folders

Get a list of form folders for this account including folder names, IDs, and contained forms.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Jotform data sources can also be manually configured to ingest data from any valid Jotform API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Jotform data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Jotform destination, and select the Send to Destination option from the menu. Select the Jotform connector from the list of available destination connectors, then select the credential that will be used to connect to Jotform, and click Next; or, create a new Jotform credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Jotform endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Form Submission

Create a new submission for a given form — the primary way to programmatically write form data into Jotform.

• Provide the Form ID of the form to submit to. Each record from your Nexset is sent as a separate submission request.

[Rest API] Register Form Webhook

Register a webhook URL on a form to receive real-time submission notifications.

• Provide the Form ID of the form on which to register the webhook.

[Rest API] Clone Form

Clone an existing form to create a new one with the same structure.

• Provide the Form ID of the form to clone.

[Rest API] Update Form Properties

Update a form's properties (title, status, settings, theme, etc.).

• Provide the Form ID of the form to update.

[Rest API] Update Submission

Update an existing submission (e.g., mark as read/unread, change answer values).

• Provide the Submission ID of the submission to update.

[Rest API] Delete Form Webhook

Remove a previously registered webhook from a form.

• Provide the Form ID and the Webhook ID of the webhook to remove.

[Rest API] Delete Submission

Delete a single submission — required for data-retention and GDPR compliance workflows.

• Provide the Submission ID of the submission to delete.

Manual configuration

Jotform destinations can also be manually configured to send data to any valid Jotform API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Jotform endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Jotform endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.