Actions35
- Profile Actions
- Passport Actions
- Punch Pass Actions
- Participant Actions
- List Actions
Overview
The "Check Out" operation for the Participant resource in this node allows you to check out a participant from an event or list using the OneTap API. This operation is useful in scenarios where you need to track attendance and manage visitor flow by marking when participants leave an event or location.
Typical use cases include:
- Event management systems tracking attendee check-outs.
- Visitor management in offices or venues to log exit times.
- Attendance systems that require both check-in and check-out timestamps for participants.
For example, after a participant has checked in to a conference, you can use this operation to mark their check-out time when they leave, optionally including details such as the method of check-out, location coordinates, and source information.
Properties
| Name | Meaning |
|---|---|
| Participant ID | The unique identifier of the participant to check out. |
| Check-in/Check-Out Fields (checkFields) | A collection of optional fields providing additional context about the check-out: - List ID: Identifier of the list associated with the check-out. - Profile ID: Identifier of the profile. - Method: The method used for check-out. Options: TAP, QR, Manual, Kiosk, SMS, Email, Voice, Browser, Mobile App. - Source: Source of the check-out action. - Location: GPS coordinates (latitude and longitude) where the check-out occurred. - Time Zone: Time zone identifier (e.g., America/Chicago). - Installation ID: Identifier for the installation performing the check-out. - Send Visitor Alert: Boolean flag indicating whether to send a visitor alert upon check-out. |
Output
The output JSON contains the response from the OneTap API after performing the check-out operation on the specified participant. It typically includes updated participant data reflecting the new check-out status and any related metadata returned by the API.
The structure generally mirrors the participant object with fields such as check-out timestamp, method, location, and other participant details.
No binary data output is produced by 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 against the OneTap service endpoint
https://api-beta.onetapcheckin.com. - Proper API credentials must be set up in n8n to authorize requests.
Troubleshooting
Common Issues:
- Invalid or missing Participant ID will cause the API request to fail.
- Incorrect or missing API credentials will result in authentication errors.
- Providing invalid GPS coordinates or unsupported method values may cause validation errors.
- Network connectivity issues can prevent successful API calls.
Error Messages:
- Errors from the OneTap API are propagated and include descriptive messages.
- If the node is set to continue on failure, errors are returned in the output JSON under an
errorfield. - Typical error resolution involves verifying input parameters, ensuring valid participant IDs, and confirming API credentials.
Links and References
- OneTap API Documentation (general reference for API endpoints and payloads)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are made within n8n)
This summary is based solely on static analysis of the provided source code and property definitions for the Participant resource's Check Out operation.