Actions35
- Profile Actions
- Passport Actions
- Punch Pass Actions
- Participant Actions
- List Actions
Overview
The "Update Punch Pass" operation in the OneTap node allows users to modify existing punch passes (also called punch passports) associated with a profile. A punch pass typically represents a prepaid or limited-use access card or ticket that tracks check-ins for events, services, or venues.
This operation is useful when you want to:
- Change the active status of a punch pass (activate or deactivate it).
- Adjust the allowed number of check-ins on the punch pass.
- Associate additional check-in IDs with the punch pass.
Practical examples include:
- Updating a coffee shop loyalty card's remaining punches.
- Reactivating a temporarily suspended gym punch pass.
- Linking new check-in records to an existing punch pass after manual adjustments.
Properties
| Name | Meaning |
|---|---|
| Passport ID | The unique identifier of the punch pass to update. |
| Update Fields | Collection of fields to update: |
| Status | Boolean indicating whether the punch pass is active (true) or inactive (false). |
| Check Ins Limit | Number specifying the new maximum allowed check-ins for the punch pass (minimum 1). |
| Check In IDs | Comma-separated string of check-in IDs to associate with the punch pass. |
Output
The output JSON contains the updated punch pass object returned from the OneTap API. This includes all current properties of the punch pass after the update, such as its ID, status, check-in limits, associated check-ins, timestamps, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an authenticated connection to the OneTap API via an API key credential configured in n8n.
- The node uses HTTP requests to the OneTap API endpoints under
https://api-beta.onetapcheckin.com. - Proper permissions on the API key are necessary to update punch passes.
Troubleshooting
- Invalid Passport ID: If the provided passport ID does not exist or is malformed, the API will return an error. Verify the ID is correct.
- Invalid Field Values: Check that numeric fields like "Check Ins Limit" are positive integers and that boolean fields are properly set.
- API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems can cause request failures; verify network access to the OneTap API.
- Partial Updates: Only provide fields you want to update; omitting fields leaves them unchanged.
- Comma-Separated Check In IDs: When providing multiple check-in IDs, ensure they are comma-separated without extra spaces or invalid characters.
If errors occur, the node returns detailed error messages from the API. Enabling "Continue On Fail" allows processing subsequent items even if one fails.
Links and References
- OneTap API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls
- OneTap official site: https://onetapcheckin.com
This summary is based solely on static analysis of the provided source code and property definitions.