OneTap icon

OneTap

Manage visitors, check-ins, and attendance with OneTap
Join our community

Actions35

Overview

This node integrates with the OneTap API to manage participants within event or visitor lists. Specifically, the Participant Create operation allows users to add one or more participants to specified lists by associating profiles with those lists. It supports adding individual profiles, multiple profiles, or all profiles at once, along with various optional participant attributes such as check-in/out status, methods, timestamps, locations, and notes.

Common scenarios where this node is beneficial include:

  • Adding attendees to an event list programmatically.
  • Bulk importing participants into multiple lists.
  • Automating participant registration workflows with detailed metadata like check-in times and locations.
  • Managing visitor attendance and tracking via automated systems.

Practical example:

  • Automatically add a set of user profiles to an event's participant list when a new event is created in your system.
  • Add all profiles from a CRM segment to a participant list for a marketing campaign.
  • Record participant check-in details including GPS location and method used (e.g., QR scan).

Properties

Name Meaning
List ID Single list identifier to which the participant(s) will be added. Required if not using List IDs.
List IDs Comma-separated list of list identifiers as an alternative to a single List ID.
Profile ID Single profile identifier representing the participant to add. Required if not using Profile IDs or Add All Profiles option.
Profile IDs Comma-separated profile identifiers as an alternative to a single Profile ID.
Add All Profiles Boolean flag indicating whether to add all profiles instead of specifying individual profile IDs.
Additional Fields Collection of optional fields to customize participant creation:
- Not Allow Duplicate Prevents adding duplicate participants.
- Override Parent Auto Add Overrides the parent list's auto-add setting.
- Search Text Text filter for searching participants.
- Checked In Boolean indicating if the participant is checked in.
- Checked Out Boolean indicating if the participant is checked out.
- Check In Date Timestamp for participant check-in date and time.
- Check Out Date Timestamp for participant check-out date and time.
- Check In Method Method used for check-in; options include TAP, QR, MANUAL, KIOSK, SMS, EMAIL, VOICE, BROWSER, MOBILE_APP.
- Check Out Method Method used for check-out; same options as Check In Method.
- Check In Time Zone Time zone string for check-in time (e.g., America/Chicago).
- Check Out Time Zone Time zone string for check-out time (e.g., America/Chicago).
- Check In Installation ID Installation identifier related to check-in.
- Check In Location GPS coordinates (latitude and longitude) for check-in location.
- Check Out Location GPS coordinates (latitude and longitude) for check-out location.
- Check In IP Address IP address recorded during check-in.
- Check In Notes Notes related to check-in.
- Check Out Notes Notes related to check-out.
- Source Source string describing origin of participant creation (e.g., API, manual entry).

Output

The node outputs JSON objects representing the response from the OneTap API after creating participants. The output typically includes details about the newly created participant(s), such as their IDs, associated list/profile IDs, check-in/out statuses, timestamps, and any other metadata returned by the API.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "participant123",
  "listId": "list456",
  "profileId": "profile789",
  "checkedIn": false,
  "checkedOut": false,
  "checkInDate": null,
  "checkOutDate": null,
  "source": "API",
  ...
}

Dependencies

  • Requires an active connection to the OneTap API with valid authentication credentials (an API key or token).
  • The node uses HTTP requests to the OneTap API endpoints under https://api-beta.onetapcheckin.com/api/participants.
  • Proper configuration of the OneTap API credential in n8n is necessary before use.

Troubleshooting

  • Missing required IDs: If neither List ID(s) nor Profile ID(s) are provided, the API call will fail. Ensure you specify at least one list and one profile identifier or enable "Add All Profiles".
  • Invalid date/time formats: Dates must be valid ISO strings or timestamps convertible to UNIX epoch seconds. Invalid dates may cause errors.
  • Duplicate participants: If duplicates are not allowed but duplicates exist, the API may reject the request. Use the "Not Allow Duplicate" option accordingly.
  • API authentication errors: Ensure the API key/token is correctly configured and has sufficient permissions.
  • Network issues: Verify network connectivity to the OneTap API endpoint.
  • Error messages: The node surfaces error messages from the OneTap API. Review these messages for specific causes (e.g., invalid parameters, unauthorized access).

To resolve errors:

  • Double-check input parameters for correctness.
  • Confirm API credentials and permissions.
  • Validate date/time and location formats.
  • Enable "Continue on Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion