Overview
This node integrates with the Vocom API to manage eSim-related operations. Specifically, for the eSim URL - Get operation, it retrieves the QR code URL associated with a given eSim plan. This is useful when you want to programmatically obtain the activation URL for an eSim after verifying inventory or creating an order.
Common scenarios include:
- Fetching the eSim QR code URL to display or send to customers after confirming availability.
- Automating workflows where eSim activation links are needed without manual intervention.
Example: After checking inventory and obtaining a nonce, use this node to get the eSim URL that can be embedded in emails or apps for user activation.
Properties
| Name | Meaning |
|---|---|
| Plan ID | The unique identifier of the Vocom eSim plan for which the URL is requested. |
| Inventory Nonce | A nonce value obtained from a prior inventory check operation, required to validate the request. |
Output
The node outputs JSON data containing the response from the Vocom API for the eSim URL request. Typically, this includes the eSim QR code URL or related metadata necessary for activation.
If the node supports binary data output (not explicitly shown here), it would represent the QR code image or similar binary content. However, based on the static analysis, the output is JSON-formatted data representing the URL and related information.
Dependencies
- Requires an active connection to the Vocom API via an API key credential configured in n8n.
- The node makes HTTP POST requests to Vocom endpoints such as
/esim/v1/productGet. - Proper configuration of credentials and network access to Vocom services is necessary.
Troubleshooting
- Missing or invalid Plan ID: Ensure the Plan ID is correctly provided; otherwise, the API will reject the request.
- Invalid or missing Inventory Nonce: The nonce must come from a successful inventory check; using an incorrect or expired nonce will cause errors.
- API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network issues: Confirm that n8n can reach the Vocom API endpoints without firewall or proxy blocking.
- Error messages from API: Usually returned in the
errorfield of the output JSON; review message details to adjust input parameters accordingly.
Links and References
- Vocom API Documentation (hypothetical link, replace with actual if available)
- n8n documentation on Creating Custom Nodes