Insert Or Update Purchase Order with Megaventory API on New Submission from Typeform API

Pipedream makes it easy to connect APIs for Megaventory, Typeform and 2,900+ other apps remarkably fast.

Trigger workflow on

New Submission from the Typeform API

Next, do this

Insert Or Update Purchase Order with the Megaventory 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 Typeform trigger and Megaventory action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Submission trigger
1. Connect your Typeform account
2. Select a Form
Configure the Insert Or Update Purchase Order action
1. Connect your Megaventory account
2. Select a Purchase Order Type ID
3. Select a Supplier ID
4. Select a Inventory Location ID
5. Select a Purchase Order Status
6. Select a Product SKU
7. Configure Purchase Order Row Quantity
8. Optional- Select a Purchase Order ID
9. Optional- Configure Purchase Order No
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 Submission on Typeform

Description:Emit new submission

Version:0.0.8

Key:typeform-new-submission

View on GitHub

Typeform Overview#

The Typeform API furnishes you with the means to create dynamic forms and collect user responses in real-time. By leveraging this API within Pipedream's serverless platform, you can automate workflows to process this data, integrate seamlessly with other services, and react to form submissions instantaneously. This empowers you to craft tailored responses, synchronize with databases, trigger email campaigns, or even manage event registrations without manual intervention.

Trigger Code#

import { createHmac } from "crypto";
import sampleEmit from "./test-event.mjs";
import { uuid } from "uuidv4";
import common from "../common/common.mjs";
import constants from "../../constants.mjs";
import utils from "../common/utils.mjs";

const { typeform } = common.props;
const { parseIsoDate } = utils;

export default {
  ...common,
  key: "typeform-new-submission",
  name: "New Submission",
  version: "0.0.8",
  type: "source",
  description: "Emit new submission",
  props: {
    ...common.props,
    http: {
      type: "$.interface.http",
      customResponse: true,
    },
    db: "$.service.db",
    formId: {
      propDefinition: [
        typeform,
        "formId",
      ],
    },
  },
  methods: {
    ...common.methods,
    generateSecret() {
      return "" + Math.random();
    },
  },
  hooks: {
    ...common.hooks,
    async activate() {
      const secret = this.generateSecret();
      this._setSecret(secret);

      let tag = this._getTag();
      if (!tag) {
        tag = uuid();
        this._setTag(tag);
      }

      return await this.typeform.createHook({
        endpoint: this.http.endpoint,
        formId: this.formId,
        tag,
        secret,
      });
    },
    async deactivate() {
      const tag = this._getTag();

      return await this.typeform.deleteHook({
        formId: this.formId,
        tag,
      });
    },
  },
  async run(event) {
    const {
      body,
      headers,
    } = event;

    const { [constants.TYPEFORM_SIGNATURE]: typeformSignature } = headers;

    if (typeformSignature) {
      const secret = this._getSecret();

      const hmac =
        createHmac(constants.ALGORITHM, secret)
          .update(body)
          .digest(constants.ENCODING);

      const signature = `${constants.ALGORITHM}=${hmac}`;

      if (typeformSignature !== signature) {
        throw new Error("signature mismatch");
      }
    }

    let formResponseString = "";
    const data = Object.assign({}, body.form_response);
    data.form_response_parsed = {};

    for (let i = 0; i < body.form_response.answers.length; i++) {
      const field = body.form_response.definition.fields[i];
      const answer = body.form_response.answers[i];

      let parsedAnswer;
      let value = answer[answer.type];

      if (value.label) {
        parsedAnswer = value.label;

      } else if (value.labels) {
        parsedAnswer = value.labels.join();

      } else if (value.choice) {
        parsedAnswer = value.choice;

      } else if (value.choices) {
        parsedAnswer = value.choices.join();

      } else {
        parsedAnswer = value;
      }

      data.form_response_parsed[field.title] = parsedAnswer;
      formResponseString += `### ${field.title}\n${parsedAnswer}\n`;
    }

    data.form_response_string = formResponseString;
    data.raw_webhook_event = body;

    if (data.landed_at) {
      data.landed_at = parseIsoDate(data.landed_at);
    }

    if (data.submitted_at) {
      data.submitted_at = parseIsoDate(data.submitted_at);
    }

    data.form_title = body.form_response.definition.title;
    delete data.answers;
    delete data.definition;

    this.$emit(data, {
      summary: JSON.stringify(data),
      id: data.token,
    });

    this.http.respond({
      status: 200,
    });
  },
  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
Typeform	`typeform`	`app`	This component uses the Typeform app.
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.
Form	`formId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

Typeform uses OAuth authentication. When you connect your Typeform account, Pipedream will open a popup window where you can sign into Typeform and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Typeform API.

Pipedream requests the following authorization scopes when you connect your account:

offlineaccounts:readforms:writeforms:readimages:writeimages:readthemes:writethemes:readresponses:readresponses:writewebhooks:readwebhooks:writeworkspaces:readworkspaces:write

About Typeform#

Typeform lets you build no-code forms, quizzes, and surveys - and get more responses.

Action#

Insert Or Update Purchase Order on Megaventory

Description:Insert or update a purchase order in the database. [See the docs](https://api.megaventory.com/v2017a/documentation/index.html#!/PurchaseOrder/postPurchaseOrderPurchaseOrderUpdate_post_3).

Version:0.0.2

Key:megaventory-insert-or-update-purchase-order

View on GitHub

Megaventory Overview#

Megaventory is a robust inventory management API allowing for detailed tracking of products, orders, and the supply chain. You can automate the updating of stock levels, manage sales and purchase orders, and generate detailed reports. With Megaventory and Pipedream, you can craft automation workflows to streamline inventory operations, synchronize data across platforms, and trigger actions based on inventory changes.

Action Code#

import app from "../../megaventory.app.mjs";
import constants from "../../common/constants.mjs";

export default {
  key: "megaventory-insert-or-update-purchase-order",
  name: "Insert Or Update Purchase Order",
  description: "Insert or update a purchase order in the database. [See the docs](https://api.megaventory.com/v2017a/documentation/index.html#!/PurchaseOrder/postPurchaseOrderPurchaseOrderUpdate_post_3).",
  type: "action",
  version: "0.0.2",
  annotations: {
    destructiveHint: true,
    openWorldHint: true,
    readOnlyHint: false,
  },
  props: {
    app,
    purchaseOrderTypeId: {
      label: "Purchase Order Type ID",
      description: "The ID of the purchase order type.",
      propDefinition: [
        app,
        "documentTypeId",
        () => ({
          args: {
            data: {
              Filters: [
                {
                  FieldName: "DocumentTypeDescription",
                  SearchOperator: "Equals",
                  SearchValue: "Purchase Order",
                },
              ],
            },
          },
        }),
      ],
    },
    supplier: {
      label: "Supplier ID",
      description: "The ID of the supplier.",
      withLabel: true,
      propDefinition: [
        app,
        "supplierClientId",
        () => ({
          args: {
            data: {
              Filters: [
                {
                  FieldName: "SupplierClientType",
                  SearchOperator: "Equals",
                  SearchValue: "Supplier",
                },
              ],
            },
          },
        }),
      ],
    },
    purchaseOrderInventoryLocationId: {
      propDefinition: [
        app,
        "inventoryLocationId",
      ],
    },
    purchaseOrderStatus: {
      type: "string",
      label: "Purchase Order Status",
      description: "The status of the purchase order.",
      options: Object.values(constants.PURCHASE_ORDER_STATUS),
    },
    productSKU: {
      type: "string",
      label: "Product SKU",
      description: "The SKU of the product.",
      propDefinition: [
        app,
        "product",
        () => ({
          mapper: ({
            ProductSKU: value, ProductDescription: label,
          }) => ({
            label,
            value,
          }),
        }),
      ],
    },
    purchaseOrderRowQuantity: {
      type: "integer",
      label: "Purchase Order Row Quantity",
      description: "The quantity of the product.",
    },
    purchaseOrderId: {
      optional: true,
      propDefinition: [
        app,
        "purchaseOrderId",
      ],
    },
    purchaseOrderNo: {
      type: "string",
      label: "Purchase Order No",
      description: "The purchase order number.",
      optional: true,
    },
  },
  methods: {
    insertOrUpdatePurchaseOrder({
      data, ...args
    } = {}) {
      return this.app.post({
        path: "/PurchaseOrder/PurchaseOrderUpdate",
        data: {
          mvRecordAction: constants.MV_RECORD_ACTION.INSERT_OR_UPDATE_NON_EMPTY_FIELDS,
          ...data,
        },
        ...args,
      });
    },
  },
  async run({ $: step }) {
    const {
      purchaseOrderTypeId,
      supplier,
      purchaseOrderInventoryLocationId,
      purchaseOrderStatus,
      productSKU,
      purchaseOrderRowQuantity,
      purchaseOrderId,
      purchaseOrderNo,
    } = this;

    const supplierId = supplier?.value ?? supplier;
    const supplierName = supplier?.label;

    const response = await this.insertOrUpdatePurchaseOrder({
      data: {
        mvPurchaseOrder: {
          PurchaseOrderTypeId: purchaseOrderTypeId,
          PurchaseOrderSupplierID: supplierId || 0,
          PurchaseOrderSupplierName: supplierName,
          PurchaseOrderInventoryLocationID: purchaseOrderInventoryLocationId,
          PurchaseOrderStatus: purchaseOrderStatus,
          PurchaseOrderDetails: [
            {
              PurchaseOrderRowProductSKU: productSKU,
              PurchaseOrderRowQuantity: purchaseOrderRowQuantity,
            },
          ],
          PurchaseOrderId: purchaseOrderId,
          PurchaseOrderNo: purchaseOrderNo,
        },
      },
    });

    step.export("$summary", `Successfully inserted or updated purchase order with ID ${response.mvPurchaseOrder.PurchaseOrderId}.`);

    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
Megaventory	`app`	`app`	This component uses the Megaventory app.
Purchase Order Type ID	`purchaseOrderTypeId`	`integer`	Select a value from the drop down menu.
Supplier ID	`supplier`	`integer`	Select a value from the drop down menu.
Inventory Location ID	`purchaseOrderInventoryLocationId`	`integer`	Select a value from the drop down menu.
Purchase Order Status	`purchaseOrderStatus`	`string`	Select a value from the drop down menu:`{ "label": "Pending", "value": "Pending" }{ "label": "Verified", "value": "Verified" }{ "label": "Closed", "value": "Closed" }{ "label": "Cancelled", "value": "Cancelled" }{ "label": "ReOpened", "value": "ReOpened" }{ "label": "Received", "value": "Received" }`
Product SKU	`productSKU`	`string`	Select a value from the drop down menu.
Purchase Order Row Quantity	`purchaseOrderRowQuantity`	`integer`	The quantity of the product.
Purchase Order ID	`purchaseOrderId`	`integer`	Select a value from the drop down menu.
Purchase Order No	`purchaseOrderNo`	`string`	The purchase order number.

Action Authentication#

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

You can generate an API key for each user of your Megaventory account from Admin -> Users -> Display all -> Click on the user name. You can also copy-paste this link -https://[YOURDOMAIN].megaventory.com/inventory/default.aspx?data=editUser&id=[YOURID]&name=[YOURNAME]

Important: Megaventory user access permissions do apply, i.e. each API key carries the permissions of the user who created it.