Actions35
- Profile Actions
- Passport Actions
- Punch Pass Actions
- Participant Actions
- List Actions
Overview
This node integrates with the OneTap API to manage digital passes called "passports" along with other related resources such as profiles, participants, punch passes, and lists. Specifically for the Passport - Send operation, it allows sending a digital passport to a recipient via SMS or email.
Typical use cases include:
- Sending event or membership passes to users via their phone number or email.
- Automating delivery of digital credentials or tickets after registration or purchase.
- Integrating with marketing or attendance workflows where digital passes need to be distributed programmatically.
For example, after creating a passport for an event attendee, you can use this node to send the passport directly to their mobile phone via SMS or to their email address.
Properties
| Name | Meaning |
|---|---|
| Passport ID | The unique identifier of the passport to send. |
| Channel | The delivery channel to use for sending the passport. Options: SMS, Email. |
| Destination | The recipient's contact information: either a phone number (for SMS) or an email address. |
Output
The output is a JSON object representing the response from the OneTap API after attempting to send the passport. It typically includes status information about the send request, such as success confirmation or error details.
No binary data output is produced by this operation.
Example output snippet (conceptual):
{
"status": "success",
"message": "Passport sent successfully",
"details": {
"passportId": "abc123",
"channel": "sms",
"destination": "+1234567890"
}
}
Dependencies
- Requires an active connection to the OneTap API.
- Needs an API authentication token configured in n8n credentials for OneTap.
- The node uses HTTP requests with authentication to communicate with the OneTap service endpoint at
https://api-beta.onetapcheckin.com.
Troubleshooting
- Invalid Passport ID: If the provided passport ID does not exist or is incorrect, the API will return an error. Verify the passport ID before sending.
- Invalid Destination Format: Ensure the destination matches the selected channel type (valid phone number for SMS, valid email format for Email).
- Authentication Errors: Check that the API key credential is correctly set up and has sufficient permissions.
- API Rate Limits or Network Issues: Temporary failures may occur due to rate limiting or connectivity problems; retrying might help.
- Error Messages: The node throws errors with messages from the OneTap API. Review these messages to identify issues like missing required fields or invalid parameters.
Links and References
- OneTap API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding how authenticated requests work in n8n.
This summary focuses exclusively on the Passport resource's Send operation as requested, based on static analysis of the provided source code and property definitions.