OneTap icon

OneTap

Manage visitors, check-ins, and attendance with OneTap

Overview

This node integrates with the OneTap API to manage lists and retrieve survey data associated with those lists. Specifically, the "Get List Survey Data" operation fetches survey responses or related data for a specified list. This is useful in scenarios where you want to analyze feedback or survey results collected from participants of an event or group managed via OneTap.

Practical examples include:

  • Retrieving survey results for a specific event attendance list to analyze participant feedback.
  • Automating report generation based on survey data linked to particular lists.
  • Integrating survey data into other workflows for further processing or notifications.

Properties

Name Meaning
List ID The unique identifier of the list for which to retrieve survey data.
Additional Fields Optional extra parameters; currently supports:
- Profile ID: Template survey data for a specific profile (used to filter or customize).

Output

The node outputs JSON data containing the survey data retrieved from the OneTap API for the specified list. The structure corresponds directly to the API response under the /lists/{listId}/survey endpoint and may include survey questions, answers, metadata, and possibly profile-specific templated data if a Profile ID was provided.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the OneTap API.
  • Requires an API authentication credential configured in n8n to authorize requests.
  • The base URL used is https://api-beta.onetapcheckin.com.
  • The node uses HTTP GET requests to fetch data from the OneTap API.

Troubleshooting

  • Common issues:

    • Invalid or missing List ID will cause the API request to fail.
    • Providing an incorrect Profile ID in additional fields might result in empty or unexpected survey data.
    • Network connectivity or authentication failures can prevent successful API calls.
  • Error messages:

    • Errors returned from the API are caught and reported with context about the failed resource and operation.
    • If the node is set to continue on failure, errors will be included in the output JSON with an error field describing the issue.
    • Typical error resolution involves verifying the List ID, ensuring proper API credentials, and checking network access.

Links and References


Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.

Discussion