Actions24
Overview
This node integrates with the Leanios API to perform various operations on different resources such as transactions, products, productions, workorders, orders, and warehouses. Specifically for the Transaction resource with the PATCH operation, it updates an existing transaction by sending a JSON body with the updated fields to the Leanios API.
Common scenarios where this node is useful include:
- Updating details of a financial or inventory transaction in Leanios.
- Automating transaction modifications based on external triggers or workflows.
- Synchronizing transaction data from other systems into Leanios.
For example, you might use this node to update the status or amount of a transaction after receiving confirmation from a payment gateway.
Properties
| Name | Meaning |
|---|---|
| Subdomain | The Leanios account subdomain to target (e.g., "dummy"). This defines the API endpoint. |
| Request Mode | The format of the request body. For PATCH, only jsonBody is supported, meaning the update data must be provided as JSON. |
| jsonBody | The JSON object containing the fields and values to update in the transaction. |
| id | The unique identifier of the transaction to update. |
Output
The node outputs a JSON array containing the response from the Leanios API after the PATCH request. This response typically includes the updated transaction object reflecting the changes made.
No binary data output is produced by this node.
Dependencies
- Requires an active Leanios API credential with username and password for authentication.
- Needs the correct subdomain of the Leanios account to construct the API URL.
- The node sends HTTP requests to the Leanios REST API endpoint:
https://{Subdomain}.leanios.com/api/v1/transactions/{id}
Troubleshooting
- Invalid Credentials Error: If the API credentials are incorrect or missing, the node will fail authentication. Verify that the API username and password are correctly configured.
- Resource Not Found: If the transaction ID does not exist, the API may return a 404 error. Ensure the
idproperty corresponds to an existing transaction. - Malformed JSON Body: If the
jsonBodyis not valid JSON or contains invalid fields, the API may reject the request. Validate the JSON structure and field names before sending. - Network Issues: Connectivity problems to the Leanios API endpoint can cause timeouts or connection errors. Check network access and firewall settings.
- Unsupported Operation: Only the
jsonBodyrequest mode is supported for PATCH; using other modes will not work.
Links and References
- Leanios API Documentation (Assumed official API docs for reference)
- n8n Documentation on HTTP Request Node (for understanding HTTP request handling)
If you need summaries for other resources or operations, please provide their names.