Create Purchase Order with Zenventory API

Pipedream makes it easy to connect APIs for Zenventory and 2,400+ other apps remarkably fast.

Trigger workflow on

HTTP requests, schedules and app events

Next, do this

Create Purchase Order with the Zenventory API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

Create a workflow to Create Purchase Order with the Zenventory API. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Configure the Create Purchase Order action
1. Connect your Zenventory account
2. Optional- Configure Supplier Id
3. Optional- Configure Supplier Name
4. Optional- Configure Warehouse Id
5. Optional- Configure Warehouse Name
6. Optional- Configure Client Id
7. Optional- Configure Client Name
8. Optional- Configure Order Number
9. Optional- Configure Draft
10. Optional- Configure Required By.
11. Optional- Configure Project Number
12. Optional- Configure Notes
13. Optional- Configure Items
Select a trigger to run your workflow on HTTP requests, schedules or app events
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Integrations#

Create Purchase Order with Zenventory API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Zenventory

Try it

Create Purchase Order with Zenventory API on New Submission from Typeform API

Typeform + Zenventory

Try it

Create Purchase Order with Zenventory API on New Submission (Instant) from Jotform API

Jotform + Zenventory

Try it

Create Purchase Order with Zenventory API on New Scheduled Tasks from Pipedream API

Pipedream + Zenventory

Try it

Create Purchase Order with Zenventory API on New Download Counts from npm API

npm + Zenventory

Try it

Details#

This is a pre-built, source-available component from Pipedream's GitHub repo. The component is developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Create Purchase Order on Zenventory

Description:Generates a new purchase order. [See the documentation](https://docs.zenventory.com/)

Version:0.0.1

Key:zenventory-create-purchase-order

View on GitHub

Code#

import { ConfigurationError } from "@pipedream/platform";
import { parseObject } from "../../common/utils.mjs";
import zenventory from "../../zenventory.app.mjs";

export default {
  key: "zenventory-create-purchase-order",
  name: "Create Purchase Order",
  description: "Generates a new purchase order. [See the documentation](https://docs.zenventory.com/)",
  version: "0.0.1",
  type: "action",
  props: {
    zenventory,
    supplierId: {
      type: "integer",
      label: "Supplier Id",
      description: "Id of the supplier that is being ordered from.",
      optional: true,
    },
    supplierName: {
      type: "string",
      label: "Supplier Name",
      description: "Name of the supplier that is being ordered from. Ignored if supplierId is provided.",
      optional: true,
    },
    warehouseId: {
      type: "integer",
      label: "Warehouse Id",
      description: "Id of the warehouse the items will be delivered to. If no warehouse parameters are given, then the user's current warehouse will be used.",
      optional: true,
    },
    warehouseName: {
      type: "string",
      label: "Warehouse Name",
      description: "Name of the warehouse the items will be delivered to. Ignored if warehouseId is provided.",
      optional: true,
    },
    clientId: {
      type: "integer",
      label: "Client Id",
      description: "Id of the client that the purchase order is for. Defaults to the user's client id.",
      optional: true,
    },
    clientName: {
      type: "string",
      label: "Client Name",
      description: "Name of the client that the purchase order is for. Ignored if clientId is provided and is nonzero.",
      optional: true,
    },
    orderNumber: {
      type: "string",
      label: "Order Number",
      description: "Order number for the purchase order. If blank, one will automatically be generated.",
      optional: true,
    },
    draft: {
      type: "boolean",
      label: "Draft",
      description: "True if the purchase order should be created as a draft to allow future editing.",
      optional: true,
    },
    requiredByDate: {
      type: "string",
      label: "Required By.",
      description: "The date of the purchase. **Format: YYYY-MM-DD**",
      optional: true,
    },
    projectNumber: {
      type: "string",
      label: "Project Number",
      description: "The number of the project.",
      optional: true,
    },
    notes: {
      type: "string",
      label: "Notes",
      description: "A note of the purchase.",
      optional: true,
    },
    items: {
      type: "string[]",
      label: "Items",
      description: "A list of object of ordered items. **Example: {\"itemId\": 123, \"sku\": \"SKU123\", \"description\": \"description\", \"quantity\": 1}**. [See the documentation](https://docs.zenventory.com/#tag/purchase_order/paths/~1purchase-orders/post) for further information.",
      optional: true,
    },
  },
  async run({ $ }) {
    if (!this.supplierId && !this.supplierName) {
      throw new ConfigurationError("You must provide at least 'Supplier Id' or 'Supplier Name'.");
    }

    const response = await this.zenventory.createPurchaseOrder({
      $,
      data: {
        supplierId: this.supplierId,
        supplierName: this.supplierName,
        warehouseId: this.warehouseId,
        warehouseName: this.warehouseName,
        clientId: this.clientId,
        clientName: this.clientName,
        orderNumber: this.orderNumber,
        draft: this.draft,
        requiredByDate: this.requiredByDate,
        projectNumber: this.projectNumber,
        notes: this.notes,
        items: parseObject(this.items),
      },
    });

    $.export("$summary", `Successfully created purchase order with ID ${response.id}`);
    return response;
  },
};

Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
Zenventory	`zenventory`	`app`	This component uses the Zenventory app.
Supplier Id	`supplierId`	`integer`	Id of the supplier that is being ordered from.
Supplier Name	`supplierName`	`string`	Name of the supplier that is being ordered from. Ignored if supplierId is provided.
Warehouse Id	`warehouseId`	`integer`	Id of the warehouse the items will be delivered to. If no warehouse parameters are given, then the user's current warehouse will be used.
Warehouse Name	`warehouseName`	`string`	Name of the warehouse the items will be delivered to. Ignored if warehouseId is provided.
Client Id	`clientId`	`integer`	Id of the client that the purchase order is for. Defaults to the user's client id.
Client Name	`clientName`	`string`	Name of the client that the purchase order is for. Ignored if clientId is provided and is nonzero.
Order Number	`orderNumber`	`string`	Order number for the purchase order. If blank, one will automatically be generated.
Draft	`draft`	`boolean`	True if the purchase order should be created as a draft to allow future editing.
Required By.	`requiredByDate`	`string`	The date of the purchase. Format: YYYY-MM-DD
Project Number	`projectNumber`	`string`	The number of the project.
Notes	`notes`	`string`	A note of the purchase.
Items	`items`	`string[]`	A list of object of ordered items. Example: {"itemId": 123, "sku": "SKU123", "description": "description", "quantity": 1}. See the documentation for further information.

Authentication#

Zenventory uses API keys for authentication. When you connect your Zenventory account, Pipedream securely stores the keys so you can easily authenticate to Zenventory APIs in both code and no-code steps.

To generate a API Key and Secret pair for a user, visit the API Keys page under Admin Users.