Actions35
- Profile Actions
- Passport Actions
- Punch Pass Actions
- Participant Actions
- List Actions
Overview
This node allows you to create a new visitor profile in the OneTap system, which manages visitors, check-ins, and attendance. Creating profiles is useful for registering individuals who will be tracked or managed within an event, venue, or organization using OneTap.
Typical use cases include:
- Adding new visitors or members to a database.
- Registering attendees before an event.
- Creating profiles with custom fields for detailed tracking (e.g., employee IDs, membership status).
- Automating profile creation from other systems via API integration.
For example, you can create a profile named "John Doe" with email, phone number, and a unique check-in code, optionally marking them as a favorite or sending a confirmation email upon creation.
Properties
| Name | Meaning |
|---|---|
| Profile Name | The full name of the profile to create. |
| Create Fields | A collection of optional additional fields to set on the profile: |
| Email address of the profile (must be valid email format). | |
| - Phone | Phone number (digits only; automatically formatted). |
| - Address | Physical address of the profile. |
| - Notes | Additional notes about the profile (e.g., "VIP member"). |
| - Favorite | Boolean flag indicating whether to mark the profile as a favorite. |
| - Check-in Code | Unique alphanumeric code used for check-in identification. |
| - Allow Duplicate | Whether to allow duplicate profiles with the same details. |
| - Duplicate Phone Allowed | Whether to allow duplicate phone numbers across profiles. |
| - Send Confirmation Email | Whether to send a confirmation email after profile creation. |
| - Time Zone | Timezone identifier string (e.g., "America/Chicago") associated with the profile. |
| - Source | String indicating the source of profile creation (e.g., "API"). |
| - Custom Fields | Multiple custom fields with user-defined names, types, and values. Supported types include String, Number, Boolean, Date, and Array. These allow storing additional structured data per profile. |
Output
The node outputs JSON objects representing the created profile(s) returned by the OneTap API. The output JSON includes all standard and custom fields of the newly created profile as confirmed by the API response.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the OneTap API service.
- Requires an API key credential configured in n8n for authenticating requests to OneTap.
- The node uses the base URL
https://api-beta.onetapcheckin.comfor API calls. - Proper network access to the OneTap API endpoint is necessary.
Troubleshooting
- Invalid Email Format: If the email field is provided but not in a valid format, the API may reject the request. Ensure emails conform to standard formats.
- Duplicate Profiles Not Allowed: If duplicates are disallowed but a similar profile exists, creation may fail. Use the "Allow Duplicate" option if duplicates are acceptable.
- Missing Required Fields: The "Profile Name" is required. Omitting it will cause an error.
- API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Date Parsing Issues in Custom Fields: For custom fields of type "date", ensure the value is a valid date string parseable by JavaScript's
Dateconstructor. - Malformed Custom Field Values: Arrays should be either valid JSON arrays or comma-separated strings; invalid formats may cause errors.
- Network or API Downtime: Network issues or OneTap API downtime will cause request failures; verify connectivity and API status.
Error messages from the node typically include the HTTP error message from the OneTap API and indicate which item index failed, aiding debugging.
Links and References
- OneTap API Documentation (general reference for API endpoints and data models)
- n8n Documentation (for configuring credentials and using nodes)
If you need summaries for other operations or resources, feel free to ask!