Actions35
- Profile Actions
- Passport Actions
- Punch Pass Actions
- Participant Actions
- List Actions
Overview
This node integrates with the OneTap API to manage visitor profiles, allowing users to retrieve multiple profiles with flexible filtering and pagination options. The "Get Many" operation under the "Profile" resource fetches a list of profiles from the OneTap system.
Common scenarios where this node is beneficial include:
- Retrieving all visitor profiles for reporting or analysis.
- Fetching a paginated subset of profiles based on search criteria or sorting preferences.
- Filtering profiles by favorite status or searching by name, email, or phone number.
Practical example:
- A marketing team wants to export all profiles marked as favorites, sorted by creation date descending, to target them with a special campaign.
- An event organizer needs to fetch profiles page-by-page to display in an internal dashboard with search functionality.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching profiles or limit the results to a specific page size. |
| Page | The page number to retrieve when not returning all results (zero-based). |
| Page Size | Number of profiles to retrieve per page (between 1 and 100). |
| Additional Fields | Optional filters and sorting options: |
| - Search | Search term to filter profiles by name, email, or phone number. |
| - Sort By | Field to sort the results by: Name, Email, or Created At. |
| - Sort Order | Sort direction: Ascending or Descending. |
| - Favorite | Boolean filter to return only profiles marked as favorite. |
Output
The output is an array of JSON objects, each representing a profile retrieved from the OneTap API. Each profile object contains fields as defined by the OneTap service, typically including identifiers, contact information, metadata, and custom fields.
If "Return All" is enabled, the node will paginate internally to collect all matching profiles before outputting them.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the OneTap API.
- The node makes HTTP GET requests to
https://api-beta.onetapcheckin.com/api/profileswith query parameters based on input properties.
Troubleshooting
- Empty Results: If no profiles are returned, verify that the search filters and favorite flag match existing profiles.
- API Authentication Errors: Ensure the API key credential is correctly set up and has necessary permissions.
- Pagination Issues: When "Return All" is false, ensure the "Page" and "Page Size" values are within valid ranges; otherwise, the API may return unexpected results.
- Rate Limits: Fetching all profiles with "Return All" enabled may hit API rate limits if the dataset is large; consider using pagination instead.
Common error messages:
- Authentication failures due to invalid or missing API keys.
- Validation errors if query parameters are out of allowed bounds.
- Network or timeout errors if the API endpoint is unreachable.
Links and References
- OneTap API Documentation (for detailed API endpoints and data schema)
- n8n documentation on HTTP Request Node for understanding how HTTP calls are made
- n8n community forums for troubleshooting API integrations
This summary focuses exclusively on the "Profile" resource with the "Get Many" operation as requested.