MYOB icon

MYOB

Interact with MYOB Business API - Sales Orders, Customers, Items, Invoices, and more
Join our community

Actions12

Overview

This node interacts with the MYOB Business API specifically for managing inventory items. The Item - List operation retrieves a list of inventory items from the MYOB system, allowing users to fetch multiple item records in one request. This is useful for synchronizing inventory data, auditing stock, or integrating MYOB inventory with other systems.

Typical use cases include:

  • Fetching a limited number of inventory items for display or processing.
  • Applying OData filters to retrieve only active or specific subsets of items.
  • Integrating inventory data into e-commerce platforms or ERP workflows.

For example, you might use this node to get the first 100 active inventory items to update your online store's product catalog.

Properties

Name Meaning
Limit Maximum number of inventory item records to return. Default is 100.
Filter Optional OData filter expression to narrow down results. Example: IsActive eq true.

Output

The output JSON contains the response from the MYOB API for the inventory items list request. It typically includes:

  • Items: An array of inventory item objects, each containing details such as UID, SKU (Number), description, name, inventory status, and pricing.
  • Count: Total number of items returned.
  • Additional metadata may be included depending on the API response.

Each inventory item object may have fields like:

  • UID: Unique identifier of the item.
  • Number: SKU or item number.
  • Description / Name: Descriptive text about the item.
  • IsInventoried: Boolean indicating if the item is inventoried.
  • IsActive: Boolean indicating if the item is active.
  • BaseSellingPrice: The base price for selling the item.

If the node supports binary data output (not applicable here), it would summarize the meaning of that binary data.

Dependencies

  • Requires an authenticated connection to the MYOB Business API using OAuth2 credentials.
  • Needs the company file GUID from the credentials to construct API requests.
  • Uses the internal helper function to make HTTP requests to MYOB endpoints.

Troubleshooting

  • Empty or invalid filter expressions: Ensure the OData filter syntax is correct; otherwise, the API may return errors or no results.
  • Limit too high: Setting a very high limit may cause slow responses or timeouts; use pagination or smaller limits.
  • Authentication errors: Verify that the OAuth2 credentials are valid and have access to the specified company file.
  • No input data error: The node expects input data to trigger execution; ensure the workflow provides input or configure accordingly.

Common error messages:

  • "No input data received": The node was executed without any incoming data.
  • API errors related to authentication or permissions should be resolved by checking credential setup.
  • Invalid filter syntax errors require correcting the OData query string.

Links and References

Discussion