Actions35
- Profile Actions
- Passport Actions
- Punch Pass Actions
- Participant Actions
- List Actions
Overview
This node integrates with the OneTap API to manage "lists" — collections of visitors or attendees for events or locations. Specifically, the Update List operation allows users to modify properties of an existing list such as its name, description, dates, check-in/out options, scheduling, and registration settings.
Use cases include:
- Updating event attendee lists with new details or schedule changes.
- Modifying check-in/check-out methods for a list to reflect operational changes.
- Enabling or disabling open registration or auto-creation of child lists for recurring events.
For example, you might update a list's date and time zone before an event or change the check-in method from manual to QR code scanning.
Properties
| Name | Meaning |
|---|---|
| List ID | The unique identifier of the list to update. |
| Update Fields | A collection of fields to update on the list. These include: |
| - Name | New name of the list. |
| - Description | Updated description text for the list. |
| - Date | The main date/time of the list (event). |
| - End Date | Optional end date/time for the list. |
| - Time Zone | Time zone identifier (e.g., "America/Chicago") for the list's date/time. |
| - Auto Create Child List | Boolean flag indicating whether child lists should be automatically created for recurring lists. |
| - Check In Option | Method used for check-in; options include: TAP, QR, Manual, Kiosk, SMS, Email, Voice, Browser, Mobile App. |
| - Check Out Option | Method used for check-out; same options as Check In Option. |
| - Check Out Enabled | Boolean flag to enable or disable check-out functionality for this list. |
| - Is Open Registration | Boolean flag to enable or disable open registration for the list. |
| - Open Registration Setting | Type of open registration allowed; options are Open, Closed, or Profiles (restricted). |
| - Source | String describing the source of the update (e.g., "API", "Admin Panel"). |
| - Schedule | Recurring schedule configuration specifying which days of the week the list recurs on. Days are booleans for Monday through Sunday. |
Output
The node outputs JSON data representing the updated list object returned by the OneTap API. This typically includes all current properties of the list after the update, such as its ID, name, description, dates (in Unix timestamp format), check-in/out options, registration settings, and schedule.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the OneTap API via an API key credential configured in n8n.
- The node uses HTTP requests authenticated with this credential to perform updates on the OneTap platform.
- No additional external dependencies beyond the OneTap API and n8n's HTTP request helper.
Troubleshooting
- Invalid List ID: If the provided List ID does not exist or is malformed, the API will return an error. Verify the List ID is correct.
- Invalid Field Values: Providing invalid values for fields like dates (non-date strings) or unsupported time zones may cause errors. Ensure date fields are valid ISO date strings and time zones are standard identifiers.
- Permission Errors: Insufficient API permissions or expired credentials will result in authentication errors. Confirm the API key is valid and has appropriate scopes.
- Network Issues: Connectivity problems can cause request failures. Check network access to the OneTap API endpoint.
- Partial Updates: Only fields included in "Update Fields" are changed; omitting required fields or sending empty values may lead to unexpected results.
If the node is set to continue on fail, errors will be returned in the output JSON under an error property for each failed item.
Links and References
- OneTap API Documentation (general reference for API endpoints and data models)
- List Management API Endpoint (specific details about list update operations)
- Time Zone Database (for valid time zone identifiers)
This summary focuses exclusively on the "List" resource and the "Update" operation as requested, based on static analysis of the provided source code and input property definitions.