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 detailed information about a specific provision result. It is designed to fetch one particular provision result by using identifiers related to the provision request and the provision result itself. This functionality is useful in scenarios where users need to track or audit the outcome of provisioning operations performed via the Pax8 platform, such as verifying the status or details of a cloud service provisioning request.
Practical examples include:
- Retrieving the status and details of a single provisioning operation after it has been initiated.
- Auditing provisioning results for compliance or troubleshooting purposes.
- Integrating provisioning result data into workflows that automate post-provisioning steps.
Properties
| Name | Meaning |
|---|---|
| Provision Request Id | The unique identifier of the provision request associated with the provisioning action. |
| Provision Result Id | The unique identifier of the specific provision result to retrieve details for. |
Output
The node outputs JSON data representing the detailed information of the requested provision result. This typically includes fields describing the status, timestamps, any error messages, and other metadata related to the provisioning operation. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard Pax8 Vendor Provisioning API.
- The node makes HTTP requests to the base URL
https://api.pax8.com/v2. - Proper configuration of the API authentication credentials within n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Invalid or missing Provision Request Id or Provision Result Id will cause the API call to fail.
- Authentication errors if the API key credential is not set up correctly.
- Network connectivity issues preventing access to the Pax8 API endpoint.
Error Messages:
- Unauthorized or 401 errors indicate problems with API credentials; verify and update the API key.
- 404 Not Found errors may occur if the provided IDs do not correspond to existing resources; double-check the IDs.
- Timeout or network errors suggest connectivity problems; ensure the n8n instance can reach the external API.
Links and References
- Pax8 API Documentation (general reference for Pax8 API usage)
- AvantGuard Pax8 Vendor Provisioning API documentation (if available internally or from AvantGuard)