OneTap

Manage visitors, check-ins, and attendance with OneTap

Actions35

Overview

The "Update Participant" operation in the OneTap node allows you to modify details of an existing participant in the OneTap system. This includes updating check-in/check-out times, notes, methods, location coordinates, time zone, installation ID, and source information related to the participant.

This operation is useful in scenarios where participant attendance or status needs to be corrected or supplemented after initial creation or check-in. For example, if a participant's check-in time was recorded incorrectly or additional notes need to be added post-event, this update operation can be used to amend those details.

Practical examples:

Correcting a participant’s check-out time after the event.
Adding notes about a participant’s special requirements or behavior.
Updating GPS coordinates for a participant’s check-in location.
Changing the method by which a participant checked in (e.g., from manual to QR).

Properties

Name	Meaning
Participant ID	The unique identifier of the participant to update.
Update Fields	A collection of fields that can be updated for the participant:
- Check In Date	The date and time when the participant checked in.
- Check Out Date	The date and time when the participant checked out.
- Notes	General notes about the participant.
- Check In Notes	Specific notes related to the participant’s check-in.
- Check Out Notes	Specific notes related to the participant’s check-out.
- Check In Method	The method used for participant check-in (string).
- Check Out Method	The method used for participant check-out (string).
- Location	GPS coordinates of the participant’s location, consisting of:
Latitude	Latitude coordinate (number).
Longitude	Longitude coordinate (number).
- Time Zone	Time zone identifier string (e.g., "America/Chicago").
- Installation ID	Identifier for the installation related to the participant.
- Source	Source of the update (string describing origin or context).

Output

The output is a JSON object representing the updated participant data as returned by the OneTap API. It contains all participant fields including any changes made during the update operation.

Example structure (simplified):

{
  "id": "participantId",
  "checkInDate": 1680000000,
  "checkOutDate": 1680003600,
  "notes": "Updated notes",
  "checkInNotes": "Checked in via QR",
  "checkOutNotes": "Left early",
  "checkInMethod": "QR",
  "checkOutMethod": "Manual",
  "location": {
    "lat": 40.7128,
    "lng": -74.0060
  },
  "timeZone": "America/New_York",
  "installationId": "install123",
  "source": "API"
}

No binary data output is involved in this operation.

Dependencies

Requires an active connection to the OneTap API with valid API authentication credentials configured in n8n.
The node uses HTTP requests to the OneTap API endpoints.
No additional external dependencies beyond the OneTap API and its authentication are required.

Troubleshooting

Invalid Participant ID: If the provided participant ID does not exist, the API will return an error. Verify the participant ID is correct.
Invalid Date Format: Dates must be valid ISO 8601 strings or timestamps convertible to UNIX epoch seconds. Invalid formats may cause errors.
Missing Required Fields: Although only participant ID is strictly required, ensure that update fields have valid values to avoid partial updates or API rejections.
API Authentication Errors: Ensure the API key or token credential is correctly set up and has sufficient permissions.
Network Issues: Connectivity problems to the OneTap API endpoint will cause failures; verify network access.
Rate Limits: Excessive requests might be throttled by the API; consider adding delays or handling retries.

Common error messages:

"Failed to execute participants operation from OneTap API: <error message>" indicates an issue with the API call; check the error message for specifics.
"Participant not found" means the participant ID does not exist.
"Invalid date format" suggests date/time inputs are malformed.

Links and References

OneTap API Documentation (general reference for API endpoints and data models)
n8n HTTP Request Node Documentation (for understanding how HTTP requests are made)
ISO 8601 Date Format (date/time formatting standard)

This summary is based on static analysis of the OneTap node source code focusing on the "participants" resource and "update" operation.

OneTapInstall