Skip to main content

Wufoo Online Forms Data Source

Follow the instructions below to create a new data flow that ingests data from a Wufoo source in Nexla.
wufoo_api.png

Wufoo Online Forms

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Wufoo Online Forms connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Wufoo instance, and click Next; or, create a new Wufoo credential for use in this flow.

  3. In Nexla, Wufoo data sources can be created using pre-built endpoint templates, which expedite source setup for common Wufoo endpoints. Each template is designed specifically for the corresponding Wufoo endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

Wufoo sources can also be configured manually, allowing you to ingest data from Wufoo endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
• To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Wufoo endpoints. Each template is designed specifically for the corresponding Wufoo endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    Get Forms from Wufoo

    This endpoint template returns details on all the forms you have permission to access from your Wufoo account. Use this template when you need to access form information, form metadata, or form structures for analysis, reporting, or integration purposes.

    • Select whether to include today's count from the includeTodayCount pulldown menu. If set to Yes, includes the number of entries received today. If set to No, does not include today's count. The default value is No. The includeTodayCount determines whether today's entry count will be included in the response.

    This endpoint returns details on all the forms you have permission to access from your Wufoo account, including form IDs, names, entry counts, and other form metadata. The endpoint uses offset-based pagination to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of form data.

    For detailed information about forms, API response structures, pagination, and available form data, see the Wufoo API documentation.

    Get fields for specific form

    This endpoint template returns the field structure for a specific form from your Wufoo account. Use this template when you need to access form field information, field definitions, or field metadata for analysis, reporting, or integration purposes.

    • Enter the Form identifier in the Form identifier field. This should be the unique identifier of the form whose fields you want to retrieve. The Form identifier determines which form's fields will be retrieved.

    This endpoint returns the field structure for a specific form from your Wufoo account, including field IDs, names, types, validation rules, and other field metadata. The endpoint uses offset-based pagination to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of field data.

    For detailed information about form fields, API response structures, pagination, and available field data, see the Wufoo API documentation.

    Get entries for specific form

    This endpoint template returns the entries that have been submitted to a specific form from your Wufoo account. This is the equivalent of viewing your stored entries in the Entry Manager in Wufoo. Use this template when you need to access form entry data, submission information, or entry details for analysis, reporting, or integration purposes.

    • Enter the Form identifier in the Form identifier field. This should be the unique identifier of the form whose entries you want to retrieve. The Form identifier determines which form's entries will be retrieved.
    • Enter the system in the system field. This should be the system parameter that determines how entries are returned. The system parameter determines the format or system used for returning entries.

    This endpoint returns the entries that have been submitted to a specific form from your Wufoo account, including entry IDs, field values, submission dates, and other entry metadata. This is the equivalent of viewing your stored entries in the Entry Manager in Wufoo. The endpoint uses offset-based pagination to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of entry data.

    For detailed information about form entries, API response structures, pagination, and available entry data, see the Wufoo API documentation.

    Get reports

    This endpoint template returns details on all the reports you have permission to access from your Wufoo account. Use this template when you need to access report information, report metadata, or report structures for analysis, reporting, or integration purposes.

    • This endpoint automatically returns details on all the reports you have permission to access from your Wufoo account. No additional configuration is required beyond selecting this endpoint template. The endpoint uses offset-based pagination to handle large result sets efficiently.

    This endpoint returns details on all the reports you have permission to access from your Wufoo account, including report IDs, names, descriptions, and other report metadata. The endpoint uses offset-based pagination to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of report data.

    For detailed information about reports, API response structures, pagination, and available report data, see the Wufoo API documentation.

    Get entries from specific reports

    This endpoint template returns the entries that make up a specific report from your Wufoo account. Use this template when you need to access report entry data, filtered entry information, or report-specific entry details for analysis, reporting, or integration purposes.

    • Enter the Report identifier in the Report identifier field. This should be the unique identifier of the report whose entries you want to retrieve. The Report identifier determines which report's entries will be retrieved.

    This endpoint returns the entries that make up a specific report from your Wufoo account, including entry IDs, field values, submission dates, and other entry metadata. The endpoint uses offset-based pagination to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of entry data.

    For detailed information about report entries, API response structures, pagination, and available entry data, see the Wufoo API documentation.

    Get Users

    This endpoint template returns details of your account's sub-users, including the API Key for each user, from your Wufoo account. Use this template when you need to access user information, user metadata, or user API keys for analysis, reporting, or integration purposes.

    • This endpoint automatically returns details of your account's sub-users, including the API Key for each user, from your Wufoo account. No additional configuration is required beyond selecting this endpoint template. The endpoint uses offset-based pagination to handle large result sets efficiently.

    This endpoint returns details of your account's sub-users, including the API Key for each user, from your Wufoo account, including user IDs, names, email addresses, API keys, and other user metadata. The endpoint uses offset-based pagination to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of user data.

    For detailed information about users, API response structures, pagination, and available user data, see the Wufoo API documentation.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Wufoo data sources can be manually configured to ingest data from any valid Wufoo API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Wufoo sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom authentication headers or request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Wufoo API from the Method pulldown menu. The most common methods are:

    • GET: For retrieving data from the API (most common for Wufoo data sources)

API Endpoint URL​

  1. Enter the URL of the Wufoo API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Wufoo API endpoints typically follow the pattern https://{base_url}/api/v3/{endpoint_path} where {base_url} is your Wufoo subdomain (e.g., yourcompany.wufoo.com).

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires Basic Authentication (API Key as username), which is handled automatically by your credential configuration.

Path to Data​

If only a subset of the data that will be returned by API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful when API responses contain metadata, pagination information, or other data that you don't need for your analysis.

For example, when a request call is used to fetch a list of forms, the API will typically return an array of form records, along with metadata, in the response. By entering the path to the relevant data, you can configure Nexla to treat each element of the returned array as a record.

Path to Data is essential when Wufoo API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.Forms[*] to access an array of forms within a response object).

    • For responses in XML format, enter the XPath that points to the object/array containing relevant data. XPath uses slash notation (e.g., /response/forms/form to access form elements within a forms element).

    Path to Data Example:

    If the Wufoo API response is in JSON format and includes a nested array named Forms that contains the relevant data, the path to the response would be entered as $.Forms[*].

Autogenerate Path Suggestions​

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

  • To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

  • Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

    PathSuggestions.png

Endpoint Testing (Manual Configuration)​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Wufoo 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.