[Components] allocadence

[pipedream-component-development]

allocadence

URLs

• https://docs.allocadence.com/

Polling Sources

new-customer-order

Prompt

Emit new event when a new customer order is created. Required props: customer ID, product ID. Optional props: order details, delivery mode

URLs

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

new-purchase-order

Prompt

Emit new event when a new purchase order is created. Required props: supplier ID, product ID. Optional props: quantity, delivery date

URLs

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

Actions

create-customer-order

Prompt

Creates a new customer order. Required props: customer information, product details, shipping address. Optional props: special instructions for order.

URLs

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

create-purchase-order

Prompt

Generates a new purchase order. Required props: supplier details, product details, delivery address. Optional props: order deadline, additional instructions.

URLs

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

[sergio-eliot-rodriguez]

Btw Allocadance and Zenventory #13944 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).

[vunguyenhung]

Hi everyone, all test cases are passed! Ready for release!

Test report
https://vunguyenhung.notion.site/Components-allocadence-119bf548bb5e81509cfde870f96f21d7