Create Item with Zenventory API on New Scheduled Tasks from Pipedream API

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

Trigger workflow on

New Scheduled Tasks from the Pipedream API

Next, do this

Create Item 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#

This integration creates a workflow with a Pipedream trigger and Zenventory action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Scheduled Tasks trigger
1. Connect your Pipedream account
2. Optional- Configure Secret
Configure the Create Item action
1. Connect your Zenventory account
2. Configure SKU
3. Optional- Configure Client Id
4. Optional- Configure Client Name
5. Optional- Configure UPC
6. Optional- Configure Description
7. Optional- Configure Category
8. Optional- Configure Base UOM
9. Optional- Configure Unit Cost
10. Optional- Configure Lead Time
11. Optional- Configure Default Econ Order
12. Optional- Configure Order Limit
13. Optional- Configure RRP
14. Optional- Configure Price
15. Optional- Configure Active
16. Optional- Configure Kit
17. Optional- Configure Assembly
18. Optional- Configure Perishable
19. Optional- Configure Track Lot
20. Optional- Configure Serialized
21. Optional- Configure Non Inventory
22. Optional- Configure Weight
23. Optional- Configure Storage Length
24. Optional- Configure Storage Width
25. Optional- Configure Storage Height
26. Optional- Configure Safety Stock
27. Optional- Configure User Field 1
28. Optional- Configure User Field 2
29. Optional- Configure User Field 3
30. Optional- Configure User Field 4
31. Optional- Configure User Field 5
32. Optional- Configure User Field 6
33. Optional- Configure Notes
34. Optional- Configure Assign To All Warehouses
35. Optional- Configure Assign To Warehouse
36. Optional- Configure Warehouse Id
37. Optional- Configure Warehouse Name
38. Optional- Configure Reorder Level
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are 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.

Trigger#

New Scheduled Tasks on Pipedream

Description:Exposes an HTTP API for scheduling messages to be emitted at a future time

Version:0.3.1

Key:pipedream-new-scheduled-tasks

View on GitHub

Pipedream Overview#

Pipedream is an API that allows you to build applications that can connect to
various data sources and processes them in real-time. You can use Pipedream to
create applications that can perform ETL (Extract, Transform, and Load) tasks,
as well as to create data-driven workflows.

Some examples of applications you can build using the Pipedream API include:

An application that can extract data from a database, transform it, and then
load it into another database.
An application that can monitor a data source for changes, and then trigger a
workflow in response to those changes.
An application that can poll an API for new data, and then process that data
in real-time.

Trigger Code#

import pipedream from "../../pipedream.app.mjs";
import sampleEmit from "./test-event.mjs";
import { uuid } from "uuidv4";

export default {
  key: "pipedream-new-scheduled-tasks",
  name: "New Scheduled Tasks",
  type: "source",
  description:
    "Exposes an HTTP API for scheduling messages to be emitted at a future time",
  version: "0.3.1",
  dedupe: "unique", // Dedupe on a UUID generated for every scheduled task
  props: {
    pipedream,
    secret: {
      type: "string",
      secret: true,
      label: "Secret",
      optional: true,
      description:
        "**Optional but recommended**: if you enter a secret here, you must pass this value in the `x-pd-secret` HTTP header when making requests",
    },
    http: {
      label: "Endpoint",
      description: "The endpoint where you'll send task scheduler requests",
      type: "$.interface.http",
      customResponse: true,
    },
    db: "$.service.db",
  },
  methods: {
    // To schedule future emits, we emit to the selfChannel of the component
    selfChannel() {
      return "self";
    },
    // Queue for future emits that haven't yet been delivered
    queuedEventsChannel() {
      return "$in";
    },
    httpRespond({
      status, body,
    }) {
      this.http.respond({
        headers: {
          "content-type": "application/json",
        },
        status,
        body,
      });
    },
    async selfSubscribe() {
      // Subscribe the component to itself. We do this here because even in
      // the activate hook, the component isn't available to take subscriptions.
      // Scheduled tasks are sent to the self channel, which emits the message at
      // the specified delivery_ts to this component.
      const isSubscribedToSelf = this.db.get("isSubscribedToSelf");
      if (!isSubscribedToSelf) {
        const componentId = process.env.PD_COMPONENT;
        const selfChannel = this.selfChannel();
        console.log(`Subscribing to ${selfChannel} channel for event source`);
        console.log(
          await this.pipedream.subscribe(componentId, componentId, selfChannel),
        );
        this.db.set("isSubscribedToSelf", true);
      }
    },
    validateEventBody(event, operation) {
      const errors = [];

      // Secrets are optional, so we first check if the user configured
      // a secret, then check its value against the prop (validation below)
      if (this.secret && event.headers["x-pd-secret"] !== this.secret) {
        errors.push(
          "Secret on incoming request doesn't match the configured secret",
        );
      }

      if (operation === "schedule") {
        const {
          timestamp,
          message,
        } = event.body;
        // timestamp should be an ISO 8601 string. Parse and check for validity below.
        const epoch = Date.parse(timestamp);

        if (!timestamp) {
          errors.push(
            "No timestamp included in payload. Please provide an ISO8601 timestamp in the 'timestamp' field",
          );
        }
        if (timestamp && !epoch) {
          errors.push("Timestamp isn't a valid ISO 8601 string");
        }
        if (!message) {
          errors.push("No message passed in payload");
        }
      }

      return errors;
    },
    scheduleTask(event) {
      const errors = this.validateEventBody(event, "schedule");
      let status, body;

      if (errors.length) {
        console.log(errors);
        status = 400;
        body = {
          errors,
        };
      } else {
        const id = this.emitScheduleEvent(event.body, event.body.timestamp);
        status = 200;
        body = {
          msg: "Successfully scheduled task",
          id,
        };
      }

      this.httpRespond({
        status,
        body,
      });
    },
    emitScheduleEvent(event, timestamp) {
      const selfChannel = this.selfChannel();
      const epoch = Date.parse(timestamp);
      const $id = uuid();

      console.log(`Scheduled event to emit on: ${new Date(epoch)}`);

      this.$emit(
        {
          ...event,
          $channel: selfChannel,
          $id,
        },
        {
          name: selfChannel,
          id: $id,
          delivery_ts: epoch,
        },
      );

      return $id;
    },
    async cancelTask(event) {
      const errors = this.validateEventBody(event, "cancel");
      let status, msg;

      if (errors.length) {
        console.log(errors);
        status = 400;
        msg = "Secret on incoming request doesn't match the configured secret";
      } else {
        try {
          const id = event.body.id;
          const isCanceled = await this.deleteEvent(event);
          if (isCanceled) {
            status = 200;
            msg = `Cancelled scheduled task for event ${id}`;
          } else {
            status = 404;
            msg = `No event with ${id} found`;
          }
        } catch (error) {
          console.log(error);
          status = 500;
          msg = "Failed to schedule task. Please see the logs";
        }
      }

      this.httpRespond({
        status,
        body: {
          msg,
        },
      });
    },
    async deleteEvent(event) {
      const componentId = process.env.PD_COMPONENT;
      const inChannel = this.queuedEventsChannel();

      // The user must pass a scheduled event UUID they'd like to cancel
      // We lookup the event by ID and delete it
      const { id } = event.body;

      // List events in the $in channel - the queue of scheduled events, to be emitted in the future
      const events = await this.pipedream.listEvents(
        componentId,
        inChannel,
      );
      console.log("Events: ", events);

      // Find the event in the list by id
      const eventToCancel = events.data.find((e) => {
        const { metadata } = e;
        return metadata.id === id;
      });

      console.log("Event to cancel: ", eventToCancel);

      if (!eventToCancel) {
        console.log(`No event with ${id} found`);
        return false;
      }

      // Delete the event
      await this.pipedream.deleteEvent(
        componentId,
        eventToCancel.id,
        inChannel,
      );
      return true;
    },
    emitEvent(event, summary) {
      // Delete the channel name and id from the incoming event, which were used only as metadata
      const id = event.$id;
      delete event.$channel;
      delete event.$id;

      this.$emit(event, {
        summary: summary ?? JSON.stringify(event),
        id,
        ts: +new Date(),
      });
    },
  },
  async run(event) {
    await this.selfSubscribe();

    const { path } = event;
    if (path === "/schedule") {
      this.scheduleTask(event);
    } else if (path === "/cancel") {
      await this.cancelTask(event);
    } else if (event.$channel === this.selfChannel()) {
      this.emitEvent(event);
    }
  },
  sampleEmit,
};

Trigger 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
Pipedream	`pipedream`	`app`	This component uses the Pipedream app.
Secret	`secret`	`string`	Optional but recommended: if you enter a secret here, you must pass this value in the `x-pd-secret` HTTP header when making requests
N/A	`http`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.

Trigger Authentication#

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

About Pipedream#

Integration platform for developers

Action#

Create Item on Zenventory

Description:Generates a new item. [See the documentation](https://docs.zenventory.com/#tag/items/paths/~1items/post)

Version:0.0.1

Key:zenventory-create-item

View on GitHub

Action Code#

import zenventory from "../../zenventory.app.mjs";

export default {
  key: "zenventory-create-item",
  name: "Create Item",
  description: "Generates a new item. [See the documentation](https://docs.zenventory.com/#tag/items/paths/~1items/post)",
  version: "0.0.1",
  type: "action",
  props: {
    zenventory,
    sku: {
      type: "string",
      label: "SKU",
      description: "The item's SKU.",
    },
    clientId: {
      propDefinition: [
        zenventory,
        "clientId",
      ],
      description: "Id of the client that the item belongs to. Defaults to the user's client id.",
      optional: true,
    },
    clientName: {
      propDefinition: [
        zenventory,
        "clientName",
      ],
      description: "Name of the client that the item belongs to. Ignored if clientId is provided and is nonzero.",
      optional: true,
    },
    upc: {
      type: "string",
      label: "UPC",
      description: "The item's UPC.",
      optional: true,
    },
    description: {
      type: "string",
      label: "Description",
      description: "The item's description.",
      optional: true,
    },
    category: {
      type: "string",
      label: "Category",
      description: "The item's category to be grouped by.",
      optional: true,
    },
    baseUom: {
      type: "string",
      label: "Base UOM",
      description: "The item's base unit of measurement.",
      optional: true,
    },
    unitCost: {
      type: "string",
      label: "Unit Cost",
      description: "How much the item costs you to stock.",
      optional: true,
    },
    leadTime: {
      type: "integer",
      label: "Lead Time",
      description: "The item's lead time.",
      optional: true,
    },
    defaultEconOrder: {
      type: "integer",
      label: "Default Econ Order",
      description: "The item's default order quantity for purchase orders.",
      optional: true,
    },
    orderLimit: {
      type: "integer",
      label: "Order Limit",
      description: "The item's order limit.",
      optional: true,
    },
    rrp: {
      type: "string",
      label: "RRP",
      description: "The item's recommended retail price.",
      optional: true,
    },
    price: {
      type: "string",
      label: "Price",
      description: "How much the item is sold for.",
      optional: true,
    },
    active: {
      type: "boolean",
      label: "Active",
      description: "True if the item is active. Inactive items are hidden from most processes.",
      optional: true,
    },
    kit: {
      type: "boolean",
      label: "Kit",
      description: "True if the item is a kit item made up of other items. An item cannot both be a kit and an assembly item.",
      optional: true,
    },
    assembly: {
      type: "boolean",
      label: "Assembly",
      description: "True if the item is stocked by combining other items together. An item cannot both be a kit and an assembly item.",
      optional: true,
    },
    perishable: {
      type: "boolean",
      label: "Perishable",
      description: "True if the item has an expiration date. A non-inventory or serialized item cannot also be this.",
      optional: true,
    },
    trackLot: {
      type: "boolean",
      label: "Track Lot",
      description: "True if the item is tracked by lot numbers. A non-inventory or serialized item cannot also be this.",
      optional: true,
    },
    serialized: {
      type: "boolean",
      label: "Serialized",
      description: "True if the item is tracked by serial numbers. A non-inventory item cannot be serialized.",
      optional: true,
    },
    nonInventory: {
      type: "boolean",
      label: "Non Inventory",
      description: "True if the item does not have inventory. A kit or assembly cannot also be non-inventory.",
      optional: true,
    },
    weight: {
      type: "string",
      label: "Weight",
      description: "The item's weight.",
      optional: true,
    },
    storageLength: {
      type: "string",
      label: "Storage Length",
      description: "Part of the dimensions the item takes to store.",
      optional: true,
    },
    storageWidth: {
      type: "string",
      label: "Storage Width",
      description: "Part of the dimensions the item takes to store.",
      optional: true,
    },
    storageHeight: {
      type: "string",
      label: "Storage Height",
      description: "Part of the dimensions the item takes to store.",
      optional: true,
    },
    safetyStock: {
      type: "integer",
      label: "Safety Stock",
      description: "How much stock should be withheld when reporting stock levels to marketplace integrations.",
      optional: true,
    },
    userField1: {
      type: "string",
      label: "User Field 1",
      description: "User defined field for the item.",
      optional: true,
    },
    userField2: {
      type: "string",
      label: "User Field 2",
      description: "User defined field for the item.",
      optional: true,
    },
    userField3: {
      type: "string",
      label: "User Field 3",
      description: "User defined field for the item.",
      optional: true,
    },
    userField4: {
      type: "string",
      label: "User Field 4",
      description: "User defined field for the item.",
      optional: true,
    },
    userField5: {
      type: "string",
      label: "User Field 5",
      description: "User defined field for the item.",
      optional: true,
    },
    userField6: {
      type: "string",
      label: "User Field 6",
      description: "User defined field for the item.",
      optional: true,
    },
    notes: {
      type: "string",
      label: "Notes",
      description: "Notes for the item.",
      optional: true,
    },
    assignToAllWarehouses: {
      type: "boolean",
      label: "Assign To All Warehouses",
      description: "True to assign to all warehouses on creation.",
      optional: true,
    },
    assignToWarehouse: {
      type: "boolean",
      label: "Assign To Warehouse",
      description: "True to assign the item to a specific warehouse.",
      optional: true,
    },
    warehouseId: {
      type: "integer",
      label: "Warehouse Id",
      description: "Id of the warehouse the item will be assigned 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 item will be assigned to. Ignored if warehouseId is provided.",
      optional: true,
    },
    reorderLevel: {
      type: "integer",
      label: "Reorder Level",
      description: "Reorder level for the item's warehouse assignment.",
      optional: true,
    },
  },
  async run({ $ }) {
    const response = await this.zenventory.createItem({
      $,
      data: {
        sku: this.sku,
        clientId: this.clientId,
        clientName: this.clientName,
        upc: this.upc,
        description: this.description,
        category: this.category,
        baseUom: this.baseUom,
        unitCost: this.unitCost && parseFloat(this.unitCost),
        leadTime: this.leadTime,
        defaultEconOrder: this.defaultEconOrder,
        orderLimit: this.orderLimit,
        rrp: this.rrp && parseFloat(this.rrp),
        price: this.price && parseFloat(this.price),
        active: this.active,
        kit: this.kit,
        assembly: this.assembly,
        perishable: this.perishable,
        trackLot: this.trackLot,
        serialized: this.serialized,
        nonInventory: this.nonInventory,
        weight: this.weight && parseFloat(this.weight),
        storageLength: this.storageLength && parseFloat(this.storageLength),
        storageWidth: this.storageWidth && parseFloat(this.storageWidth),
        storageHeight: this.storageHeight && parseFloat(this.storageHeight),
        safetyStock: this.safetyStock,
        userField1: this.userField1,
        userField2: this.userField2,
        userField3: this.userField3,
        userField4: this.userField4,
        userField5: this.userField5,
        userField6: this.userField6,
        notes: this.notes,
        assignToAllWarehouses: this.assignToAllWarehouses,
        assignToWarehouse: this.assignToWarehouse,
        warehouseId: this.warehouseId,
        warehouseName: this.warehouseName,
        reorderLevel: this.reorderLevel,
      },
    });

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

Action Configuration#

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

Label	Prop	Type	Description
Zenventory	`zenventory`	`app`	This component uses the Zenventory app.
SKU	`sku`	`string`	The item's SKU.
Client Id	`clientId`	`integer`	Id of the client that the item belongs to. Defaults to the user's client id.
Client Name	`clientName`	`string`	Name of the client that the item belongs to. Ignored if clientId is provided and is nonzero.
UPC	`upc`	`string`	The item's UPC.
Description	`description`	`string`	The item's description.
Category	`category`	`string`	The item's category to be grouped by.
Base UOM	`baseUom`	`string`	The item's base unit of measurement.
Unit Cost	`unitCost`	`string`	How much the item costs you to stock.
Lead Time	`leadTime`	`integer`	The item's lead time.
Default Econ Order	`defaultEconOrder`	`integer`	The item's default order quantity for purchase orders.
Order Limit	`orderLimit`	`integer`	The item's order limit.
RRP	`rrp`	`string`	The item's recommended retail price.
Price	`price`	`string`	How much the item is sold for.
Active	`active`	`boolean`	True if the item is active. Inactive items are hidden from most processes.
Kit	`kit`	`boolean`	True if the item is a kit item made up of other items. An item cannot both be a kit and an assembly item.
Assembly	`assembly`	`boolean`	True if the item is stocked by combining other items together. An item cannot both be a kit and an assembly item.
Perishable	`perishable`	`boolean`	True if the item has an expiration date. A non-inventory or serialized item cannot also be this.
Track Lot	`trackLot`	`boolean`	True if the item is tracked by lot numbers. A non-inventory or serialized item cannot also be this.
Serialized	`serialized`	`boolean`	True if the item is tracked by serial numbers. A non-inventory item cannot be serialized.
Non Inventory	`nonInventory`	`boolean`	True if the item does not have inventory. A kit or assembly cannot also be non-inventory.
Weight	`weight`	`string`	The item's weight.
Storage Length	`storageLength`	`string`	Part of the dimensions the item takes to store.
Storage Width	`storageWidth`	`string`	Part of the dimensions the item takes to store.
Storage Height	`storageHeight`	`string`	Part of the dimensions the item takes to store.
Safety Stock	`safetyStock`	`integer`	How much stock should be withheld when reporting stock levels to marketplace integrations.
User Field 1	`userField1`	`string`	User defined field for the item.
User Field 2	`userField2`	`string`	User defined field for the item.
User Field 3	`userField3`	`string`	User defined field for the item.
User Field 4	`userField4`	`string`	User defined field for the item.
User Field 5	`userField5`	`string`	User defined field for the item.
User Field 6	`userField6`	`string`	User defined field for the item.
Notes	`notes`	`string`	Notes for the item.
Assign To All Warehouses	`assignToAllWarehouses`	`boolean`	True to assign to all warehouses on creation.
Assign To Warehouse	`assignToWarehouse`	`boolean`	True to assign the item to a specific warehouse.
Warehouse Id	`warehouseId`	`integer`	Id of the warehouse the item will be assigned 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 item will be assigned to. Ignored if warehouseId is provided.
Reorder Level	`reorderLevel`	`integer`	Reorder level for the item's warehouse assignment.

Action 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.

About Zenventory#

All-In-One Platform for E-Commerce Operations Success

More Ways to Connect Zenventory + Pipedream#

Other Popular Integrations#

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

Pipedream + Zenventory

Create Item with Zenventory API on New Scheduled Tasks from Pipedream API

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

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

Developers ♥ Pipedream

1-24of2,400+apps by most popular

1
-
24
of
2,400+
apps by most popular