Actions18
- Provisioning Simulations Actions
- Provision Details Actions
- Provisioners Actions
- Provision Attempts Actions
- Provision Results Actions
- Provision Requests Actions
Overview
This node interacts with the AvantGuard Pax8 Vendor Provisioning API to retrieve provisioning details. Specifically, the "Get All Provision Details" operation fetches all provision details associated with a given Provision Request Id. This is useful in scenarios where users need to track or audit provisioning requests made through the Pax8 platform, such as verifying the status of software licenses or cloud service activations.
Practical examples include:
- Retrieving all provisioning details for a specific request to monitor its progress.
- Auditing provisioning history for compliance or troubleshooting purposes.
Properties
| Name | Meaning |
|---|---|
| Provision Request Id | The unique identifier of the provisioning request for which all provision details are retrieved. This is a required string input. |
Output
The node outputs JSON data containing the full set of provision details related to the specified Provision Request Id. The structure typically includes information about each provisioned item, status, timestamps, and any relevant metadata returned by the Pax8 Vendor Provisioning API.
If the API supports binary data (not evident from the provided code), it would be included accordingly, but based on the static analysis, output is primarily JSON.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard Pax8 Vendor Provisioning API.
- The base URL for API requests is
https://api.pax8.com/v2. - The node depends on the
@avantguardllc/n8n-openapi-nodepackage and a local OpenAPI specification file (openapi-pax8-vendorprovisioning.json) to build its properties and handle requests.
Troubleshooting
- Missing or invalid Provision Request Id: Since this property is required, omitting it or providing an incorrect ID will likely cause the API call to fail or return no results.
- Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Network issues or API downtime: Connectivity problems or Pax8 API outages can result in request failures.
- Unexpected response format: If the API changes, the node might not parse responses correctly; updating the OpenAPI spec or node version may be necessary.
Links and References
- Pax8 API Documentation (general reference for Pax8 APIs)
- AvantGuard Pax8 Vendor Provisioning API Spec (repository for the OpenAPI integration used)