OneTap Trigger icon

OneTap Trigger

Listen for OneTap events like check-ins, check-outs, and new participants
Join our community

Overview

This node listens for events from the OneTap platform, such as participant check-ins, check-outs, new participant creations, and profile creations. It can operate either by polling the OneTap API at regular intervals or by receiving webhook notifications if supported.

Typical use cases include:

  • Automating workflows triggered by attendee check-ins or check-outs at events.
  • Responding to new participant registrations in real-time.
  • Tracking profile creation events for user management or analytics.

For example, you could use this node to automatically send a welcome email when a new participant checks in or update a CRM system when a profile is created.

Properties

Name Meaning
Environment Select which OneTap environment to use: Production (live data) or Staging (development/testing server).
Trigger On The event type that triggers the workflow: Check-In, Check-Out, New Participant, or Profile Created.
Trigger Method How the node listens for events: Polling (regularly checks the API) or Webhook (listens for incoming webhook calls from OneTap).
Poll Interval (Minutes) How often to poll the API for new events, in minutes (only shown if polling is selected). Valid values are 1 to 60.
List ID Optional filter to trigger only on events related to a specific list (applies to Check-In, Check-Out, and New Participant events).
Profile ID Optional filter to trigger only on events related to a specific profile (applies to Check-In and Check-Out events).
Additional Filters Collection of optional filters:
- Method: Filter by check-in/check-out method (e.g., TAP, QR, Manual, Kiosk, SMS, Email, Voice, Browser, Mobile App).
- Source: Filter by source string.

Output

The node outputs an array of items where each item’s json property contains the event data received from OneTap, enriched with additional metadata:

  • All original event fields from OneTap (e.g., participant details, timestamps).
  • triggerType: The type of event that triggered the workflow (checkin, checkout, participant, or profile).
  • environment: The selected OneTap environment (production or staging).
  • triggeredAt: Unix timestamp (seconds) indicating when the event was processed by the node.
  • For webhook mode, HTTP headers and query parameters received with the webhook call are also included under headers and query.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the OneTap API.
  • Supports two environments: production (https://api-beta.onetapcheckin.com) and staging (http://localhost:1337).
  • If using webhook mode, the OneTap service must be configured to send webhook calls to the n8n webhook URL.

Troubleshooting

  • No events received during polling:
    Ensure the poll interval is set appropriately and that there are new events since the last poll. Also verify API credentials and network connectivity.

  • Webhook not triggering:
    Confirm that the OneTap service is correctly configured to send webhooks to the n8n endpoint. Check that the webhook URL path matches the node’s configuration.

  • Filtered events not triggering:
    Double-check filter values such as List ID, Profile ID, Method, and Source. Filters are case-sensitive and must match exactly.

  • API authentication errors:
    Verify that the API key credential is valid and has necessary permissions.

  • Unexpected empty responses:
    The node returns empty output if no new events match the criteria or if an error occurs during the API request.

Links and References

Discussion