OneTapInstall

Overview

This node integrates with the OneTap API to manage digital passports, profiles, participants, punch passes, and lists related to visitor management, check-ins, and attendance tracking. Specifically, the "Passport" resource with the "Get by Participant" operation fetches passport information associated with a specific participant.

Use cases include:

• Retrieving a participant's digital passport for verification or display.
• Automating workflows that require fetching participant-related access credentials.
• Integrating event or venue management systems with OneTap to synchronize participant pass data.

Example: Automatically retrieve a participant’s passport details after they check in to validate their access rights or send them relevant notifications.

Properties

Output

The node outputs JSON data representing the passport(s) associated with the specified participant. The structure corresponds directly to the response from the OneTap API endpoint /api/passports/participants/{participantId}.

• The output JSON contains all passport details linked to the participant.
• No binary data is returned by this operation.

Example output snippet (simplified):

{
  "id": "passport123",
  "participantId": "participant456",
  "type": "event_pass",
  "status": "active",
  "issuedAt": 1680000000,
  "expiresAt": 1682592000,
  ...
}

Dependencies

• Requires an API key credential for authenticating requests to the OneTap API.
• The node uses the base URL https://api-beta.onetapcheckin.com.
• Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

• Common issues:

  • Invalid or missing participant ID will cause the API request to fail.
  • Authentication errors if the API key credential is not set up correctly.
  • Network or connectivity issues may prevent successful API calls.

• Error messages:

  • Errors from the OneTap API are caught and reported with context including the item index.
  • If "Continue On Fail" is disabled, the node execution stops on error; enabling it allows processing subsequent items.

• Resolution tips:

  • Verify the participant ID is correct and exists in OneTap.
  • Ensure the API key credential is valid and has required permissions.
  • Check network connectivity and firewall settings.

Links and References

• OneTap API Documentation (general reference for endpoints)
• n8n documentation on HTTP Request with Authentication