Actions35
- Profile Actions
- Passport Actions
- Punch Pass Actions
- Participant Actions
- List Actions
Overview
This node integrates with the OneTap API to manage profiles, including creating, retrieving, updating, and deleting visitor profiles. Specifically, the "Profile Delete" operation allows users to delete a specific profile by its ID. This is useful in scenarios where you need to remove outdated or incorrect visitor information from your system.
Practical examples:
- Automatically removing a visitor's profile after an event ends.
- Cleaning up test or duplicate profiles from your database.
- Managing user data lifecycle in compliance with privacy regulations by deleting profiles on request.
Properties
| Name | Meaning |
|---|---|
| Profile ID | The unique identifier of the profile to delete. This is required to specify which profile should be removed. |
Output
The output JSON contains the response from the OneTap API after attempting to delete the specified profile. Typically, this will include confirmation of deletion or any error messages returned by the API. The structure depends on the API's response but generally confirms success or failure of the delete operation.
No binary data output is involved in this operation.
Example output JSON snippet:
{
"success": true,
"message": "Profile deleted successfully"
}
or in case of failure:
{
"error": "Profile not found"
}
Dependencies
- Requires an active connection to the OneTap API.
- Requires an API key credential configured in n8n for authentication with OneTap.
- The node uses HTTP DELETE requests to the endpoint:
https://api-beta.onetapcheckin.com/api/profiles/{profileId}.
Troubleshooting
Common issues:
- Invalid or missing Profile ID: Ensure the Profile ID is correctly provided and exists.
- Authentication errors: Verify that the API key credential is valid and has necessary permissions.
- Network issues: Confirm connectivity to the OneTap API endpoint.
Error messages:
"Failed to execute profile operation from OneTap API: <error message>"indicates an issue during the API call. Check the error message for details."Profile not found"means the specified Profile ID does not exist; verify the ID.- Authentication errors typically indicate invalid or expired credentials.
Resolution tips:
- Double-check the Profile ID input.
- Re-authenticate or update the API key credential if needed.
- Review API rate limits or service status if calls fail repeatedly.
Links and References
- OneTap API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes.