Actions39
- Account Actions
- Client Actions
- Document Actions
- Product Actions
- Receipt Actions
- Store Actions
- Supplier Actions
Document → Get Payment Methods
AI-generatedOverview
This node integrates with the Vendus API, a platform for invoicing and business management. Specifically, the "Get Payment Methods" operation under the "Document" resource retrieves the list of available payment methods configured in Vendus.
Typical use cases include:
- Fetching payment method options to dynamically populate dropdowns or forms in workflows.
- Synchronizing payment method data from Vendus into other systems.
- Automating invoice creation processes where payment method selection is required.
For example, a user might use this node to get all payment methods before creating an invoice, ensuring the selected payment method is valid and up-to-date.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of optional settings: |
| Enable Debug Logging | Boolean flag to enable detailed debug logging for troubleshooting API calls. When enabled, the node logs detailed information about request construction, responses, and errors. |
Output
The node outputs an array of JSON objects, each representing a payment method retrieved from the Vendus API. The structure typically includes fields such as:
id(or equivalent): Unique identifier of the payment method.titleorname: Human-readable name of the payment method.
Example output JSON snippet:
[
{
"id": "1",
"title": "Cash"
},
{
"id": "2",
"title": "Credit Card"
}
]
If the API call fails and "Continue On Fail" is enabled, the output will contain error details instead.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Vendus API.
- The node expects the base URL of the Vendus API to be configured in the credentials.
- Network access to the Vendus API endpoint
/documents/paymentmethods.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Network connectivity issues can prevent successful API calls.
- If the Vendus API changes its endpoint or response format, the node may fail or return unexpected data.
Error Messages:
"No routing configuration found for Document.Get Payment Methods": Indicates the node could not find the API route for the requested resource-operation pair. This usually means a misconfiguration or unsupported operation.- Parameter substitution errors if required parameters are missing (not applicable here since this operation does not require additional parameters).
- HTTP errors returned by the Vendus API, e.g., 401 Unauthorized, 404 Not Found, or 500 Internal Server Error.
Resolution Tips:
- Verify that the API key credential is correctly set up and has necessary permissions.
- Enable "Enable Debug Logging" option to get detailed logs for diagnosing issues.
- Check network connectivity and Vendus API status.
- Review the Vendus API documentation for any updates or changes.
Links and References
- Vendus Official Website (developer site mentioned in the node description)
- Vendus API Documentation (not provided in source code, but typically available from Vendus support or developer portal)