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 all provision attempts related to a specific provision request. It is useful in scenarios where users need to audit, monitor, or analyze the history of provisioning attempts for a given request, such as tracking success/failure statuses or troubleshooting provisioning issues.
A practical example would be an IT administrator who wants to fetch all attempts made to provision a particular service or resource identified by a provision request ID, optionally filtering by additional parameters like provision detail ID.
Properties
| Name | Meaning |
|---|---|
| Provision Request Id | The unique identifier of the provision request for which all provision attempts are fetched. This is a required string input. |
| Additional Query Parameters | Optional extra query parameters to refine the search. Currently supports: - Provision Detail Id: A string to filter attempts by a specific provision detail ID. |
Output
The node outputs JSON data representing the list of provision attempts associated with the specified provision request. Each item in the output typically contains details about individual attempts, such as timestamps, status, and any relevant metadata returned by the API.
No binary data output is indicated or expected from this operation.
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 credential within n8n is necessary for successful execution.
Troubleshooting
- Missing or invalid Provision Request Id: Since this property is required, omitting it or providing an incorrect ID will likely cause errors or empty results.
- Authentication errors: If the API key credential is missing, expired, or invalid, the node will fail to authenticate with the API.
- API rate limits or connectivity issues: Network problems or API throttling may result in request failures.
- Invalid additional query parameters: Providing unsupported or malformed query parameters could lead to API errors.
To resolve these:
- Ensure the Provision Request Id is correctly provided.
- Verify that the API key credential is valid and properly configured.
- Check network connectivity and API status.
- Use only supported query parameters as defined.
Links and References
- Pax8 API Documentation (general reference for API capabilities)
- AvantGuard Pax8 Vendor Provisioning API documentation (if available internally or via vendor)