Authentication and enablement
Requires a workspace Tally integration pointing at the TallyPrime HTTP-XML gateway.base_url, company, and the optional reverse-proxy basic-auth credentials are injected from the integration record. Enable the tool and bind the integration.
The Tally company must be “Maintain Accounts with Inventory” — an accounts-only company has no stock item masters.
Inputs
name_contains(optional): case-insensitive substring to filter item names (e.g.steel). Omit to list every stock item.
Output
{name_contains, total_items, items[], retrieved_at}.
Each entry in items[] carries:
name— the exact name to pass totally_create_purchase_order.parent_group— the item’s stock group.base_unit— the unit symbol (Nos,Kgs) to pass as a purchase-order line’sunit.closing_balance— Tally’s own quantity string (e.g.42 Nos), with its numeric part inclosing_qty.closing_value— closing stock value.
Limits and side effects
- Read-only against Tally. Creates and changes nothing.
- The collection is always exported unfiltered and the name filter is applied afterwards. A Tally TDL string filter that silently matched nothing would be indistinguishable from “the item does not exist”, which is the exact confusion this tool exists to prevent. On a company with a very large item master the export can be slow.
base_unitis the authoritative unit symbol. The unit insideclosing_balanceis not parsed back out.- An empty result is a successful response, not an error.
Expected errors
- Missing Tally credentials.
- Gateway unreachable or an HTTP error from the Tally gateway.
- Unparseable response from Tally.