Actions39
- Contact Actions
- Transaction Actions
- Subscription Actions
- Affiliation Actions
- Checkout Actions
- Country Actions
- Coupon Actions
- Product Actions
- User Actions
- Webhook Actions
Overview
The node interacts with the Guru Digital Manager API to manage transactions among other resources. Specifically, the Update Transaction operation allows users to modify details of an existing transaction by providing its ID and new data fields. This is useful in scenarios where transaction information such as amount, description, or status needs correction or updating after creation.
Practical examples include:
- Correcting the transaction amount if it was entered incorrectly.
- Updating the transaction status to reflect its current state (e.g., from "waiting_payment" to "completed").
- Adding or modifying a description for better record keeping.
Properties
| Name | Meaning |
|---|---|
| Transaction ID | The unique identifier of the transaction to update (e.g., tr_043tzaioaeBMAxAnG). |
| Transaction Data | A collection of fields to update on the transaction: |
| - Amount: Numeric value representing the transaction amount. | |
| - Description: Text describing the transaction. | |
| - Status: Current state of the transaction. Possible values are: | |
| Abandoned, Analysis, Approved, Billet Printed, Blocked, Canceled, Chargeback, Completed, Delayed, | |
| Dispute, Expired, In Recovery, Refunded, Rejected, Scheduled, Started, Trial, Waiting Payment. |
Output
The output is a JSON array containing the updated transaction object returned by the Guru Digital Manager API. This object reflects the new state of the transaction after the update operation.
No binary data is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Guru Digital Manager API.
- The base URL for the API is configurable via credentials but defaults to
https://digitalmanager.guru/api/v2. - The node uses HTTP methods (
PUT) to send update requests to the endpoint/transactions/{transactionId}.
Troubleshooting
- Missing Credentials Error: If no API credentials are provided, the node will throw an error indicating that credentials are required.
- Invalid Transaction ID: If the transaction ID does not exist or is incorrect, the API may return a 404 error. The node attempts multiple alternative endpoints to retrieve the transaction before failing.
- Permission Issues: Ensure the API token has sufficient permissions to update transactions.
- API Endpoint Errors: Verify the base URL in credentials is correct and matches the API version expected.
- Common Error Message:
This indicates the transaction could not be found or accessed.Failed to get transaction with ID "{transactionId}". All endpoints returned 404. Please verify: 1. The transaction ID is correct and exists 2. Your API token has permission to access transactions 3. The base URL is correct in your credentials 4. Check the API documentation: https://docs.digitalmanager.guru/developers/transactions Original error: {error message}
Links and References
- Guru Digital Manager API Documentation: https://docs.digitalmanager.guru/developers/transactions
