[Components] zenventory

[pipedream-component-development]

zenventory

URLs

• https://docs.zenventory.com

Polling Sources

new-customer-order

Prompt

Emit new event every time a customer order is created. The main prop to set is the order ID. Other good optional props can be order status and the customer ID.

URLs

• https://docs.zenventory.com/#tag/customer_order/paths/~1customer-orders/get

new-purchase-order

Prompt

Emit new event when a purchase order is created. This involves configuring the purchase order ID and can optionally include the vendor ID and order status.

URLs

• https://docs.zenventory.com/#tag/purchase_order/paths/~1purchase-orders/get

new-item-created

Prompt

Emit new event when a new item is created. The only required prop is the item ID. Optional props can be item category and the supplier ID.

URLs

• https://docs.zenventory.com/#tag/items/paths/~1items/get

Actions

create-item

Prompt

Creates a new inventory item in Zenventory. Props consists of item data: name, quantity, etc.

URLs

• https://docs.zenventory.com/#tag/items/paths/~1items/post

create-customer-order

Prompt

Creates a new customer order in Zenventory. Props include customer information and order details.

URLs

• https://docs.zenventory.com/#tag/customer_order/paths/~1customer-orders/post

[sergio-eliot-rodriguez]

Btw Allocadance #13950 and Zenventory are meant to have the same components

[sergio-eliot-rodriguez]

From the conversation with Allocadance, Zenventory app developers:
...

I am the product manager for both Allocadence & Zenventory (sister applications serving different verticals but both for warehouse operations, lots of shared code). It would make sense for you guys to approach both integrations at once: The API URLs are different, but the endpoints and API functionality are otherwise exactly the same (you'll get two integrations for the development work of 1).