Leanios icon

Leanios

Actions24

Overview

This node integrates with the Leanios API to perform operations on various resources such as Transactions, Products, Productions, Workorders, Orders, and Warehouses. Specifically for the Transaction resource with the getById operation, it retrieves a single transaction by its unique identifier.

Common scenarios include:

  • Fetching detailed information about a specific transaction in Leanios by its ID.
  • Integrating transaction data retrieval into automated workflows for reporting or further processing.
  • Using the node to verify transaction details before performing other actions.

Example: You want to get the details of a transaction with ID 12345 from your Leanios account under the subdomain "dummy". This node will call the Leanios API endpoint for that transaction and return its data.

Properties

Name Meaning
Subdomain The Leanios account subdomain to target (e.g., "dummy"). Required for API URL formation.
id The unique numeric identifier of the transaction to retrieve. Required for getById.

Output

The node outputs a JSON array containing the transaction data returned by the Leanios API. The structure corresponds directly to the API response for a single transaction object.

  • The output is accessible via the json property.
  • No binary data output is produced by this node.

Dependencies

  • Requires an active Leanios API credential with username and password for basic authentication.
  • Needs the user to specify the correct subdomain corresponding to their Leanios account.
  • The node makes HTTP requests to the Leanios REST API at URLs formatted as https://{Subdomain}.leanios.com/api/v1/transactions/{id}.

Troubleshooting

  • Common issues:

    • Incorrect or missing subdomain will cause request failures due to invalid URL.
    • Invalid or expired API credentials will result in authentication errors.
    • Providing an invalid or non-existent transaction ID will likely return a 404 error from the API.

  • Error messages:

    • Errors thrown by the node will contain the message from the underlying HTTP request failure.
    • Typical errors include network issues, authentication failures, or resource not found.

  • Resolution tips:

    • Verify the subdomain is correctly set and matches your Leanios account.
    • Ensure API credentials are valid and have necessary permissions.
    • Confirm the transaction ID exists in your Leanios system.

Links and References

Discussion