Actions24
Overview
This node integrates with the Leanios API to perform various operations on different resources such as products, transactions, productions, workorders, orders, and warehouses. Specifically, for the Warehouse resource with the Get operation, it retrieves a list of warehouses from the Leanios system.
Common scenarios where this node is useful include:
- Fetching warehouse data to synchronize inventory or logistics information.
- Integrating warehouse details into other workflows for reporting or automation.
- Accessing warehouse metadata for decision-making in supply chain processes.
Example: A user wants to get all warehouses from their Leanios account to update an internal database or trigger further processing based on warehouse locations.
Properties
| Name | Meaning |
|---|---|
| Subdomain | The Leanios account subdomain used to build the API URL (e.g., "dummy" in dummy.leanios.com). This identifies the specific Leanios instance to connect to. |
Note: The node also requires selecting the Resource (warehouse) and Operation (get), but these are fixed by your request.
Output
The output is a JSON array containing the response from the Leanios API for the requested resource. For the Warehouse Get operation, this will be an array of warehouse objects with their respective properties as returned by the Leanios API.
The node does not output binary data.
Example output structure (simplified):
[
{
"id": "123",
"name": "Main Warehouse",
"location": "City A",
"capacity": 1000,
...
},
{
"id": "456",
"name": "Secondary Warehouse",
"location": "City B",
"capacity": 500,
...
}
]
Dependencies
- Requires an API key credential for authenticating with the Leanios API (username and password).
- Needs the
Subdomainproperty to construct the correct API endpoint URL. - The node makes HTTP requests to
https://{Subdomain}.leanios.com/api/v1/warehouses.
Troubleshooting
- Authentication errors: If the API credentials are incorrect or missing, the node will fail to authenticate. Verify that the API username and password are correctly configured.
- Invalid Subdomain: If the subdomain is wrong or the Leanios instance is unreachable, the request will fail. Ensure the subdomain matches your Leanios account.
- API errors: The node throws errors with messages returned from the Leanios API. Check the error message for details, such as invalid parameters or permission issues.
- Network issues: Connectivity problems can cause request failures. Confirm network access to the Leanios API endpoint.
Links and References
- Leanios API Documentation (hypothetical link; replace with actual if available)
- n8n documentation on HTTP Request Node for understanding how API calls are made within n8n nodes.