Actions36
- List Actions
- Participant Actions
- Passport Actions
- Profile Actions
- Punch Pass Actions
Participant → Create
AI-generatedOverview
This node operation creates participant entries in the OneTap system. It supports adding participants to one or multiple lists, associating them with one or multiple profiles, or adding all profiles. Additional optional fields allow specifying check-in and check-out details such as date, location (GPS coordinates), method, notes, and time zone, as well as flags for duplicate prevention and auto-add overrides. This operation is useful for managing event or visitor attendance by programmatically adding participants with detailed metadata.
Use Case Examples
- Adding a participant to a specific list with a single profile ID and check-in details.
- Creating multiple participants by specifying multiple list IDs and profile IDs with check-in and check-out metadata.
Properties
| Name | Meaning |
|---|---|
| List ID | Single list ID to which the participant will be added (required if not using List IDs). |
| List IDs | Comma-separated list of list IDs as an alternative to a single List ID. |
| Profile ID | Single profile ID associated with the participant (required if not using Profile IDs or Add All Profiles). |
| Profile IDs | Comma-separated profile IDs as an alternative to a single Profile ID. |
| Add All Profiles | Boolean flag indicating whether to add all profiles instead of specifying profile IDs. |
| Additional Fields | Collection of optional fields to specify check-in and check-out details, duplicate prevention, search text, and source information. |
Output
JSON
json- The response from the OneTap API representing the created participant(s) with all relevant details.
Dependencies
- OneTap API authentication credential
Troubleshooting
- Ensure that either List ID or List IDs is provided; otherwise, the API may reject the request.
- If specifying profile IDs, ensure they are valid and exist in the OneTap system.
- Date and time fields must be in a valid format; invalid dates may cause errors.
- GPS coordinates must be valid numbers; incorrect values may cause the API to reject the request.
- If the API returns an error, check the error message for details and verify the API credentials and permissions.