import quickbooks from "../../quickbooks.app.mjs";
import { ConfigurationError } from "@pipedream/platform";
export default {
key: "quickbooks-update-item",
name: "Update Item",
description: "Updates an item. [See the documentation](https://developer.intuit.com/app/developer/qbo/docs/api/accounting/all-entities/item#full-update-an-item)",
version: "0.0.1",
type: "action",
props: {
quickbooks,
itemId: {
propDefinition: [
quickbooks,
"itemId",
],
},
name: {
type: "string",
label: "Name",
description: "Name of the item. This value must be unique.",
},
trackQtyOnHand: {
type: "boolean",
label: "Track Quantity on Hand",
description: "True if there is quantity on hand to be tracked. Once this value is true, it cannot be updated to false. Applicable for items of type `Inventory`. Not applicable for `Service` or `NonInventory` item types.",
optional: true,
},
qtyOnHand: {
type: "string",
label: "Quantity on Hand",
description: "Current quantity of the `Inventory` items available for sale. Not used for `Service` or `NonInventory` type items. Required for `Inventory` type items.",
optional: true,
},
incomeAccountRefValue: {
type: "string",
label: "Income Account Ref Value",
description: "Reference to the posting account, that is, the account that records the proceeds from the sale of this item. Must be an account with account type of `Sales of Product Income`. Query the Account name list resource to determine the appropriate Account object for this reference. Use `Account.Id` from that object for `IncomeAccountRef.value`. See specifications for the IncomeAccountRef parameters in the [Create an item page](https://developer.intuit.com/app/developer/qbo/docs/api/accounting/all-entities/item#create-an-item).",
propDefinition: [
quickbooks,
"accountIds",
],
},
type: {
type: "string",
label: "Type",
description: "Classification that specifies the use of this item. See the description at the top of the [Item entity page](https://developer.intuit.com/app/developer/qbo/docs/api/accounting/all-entities/item) for details about supported item types. See specifications for the type parameter in the [Create an item page](https://developer.intuit.com/app/developer/qbo/docs/api/accounting/all-entities/item#create-an-item).",
optional: true,
options: [
"Inventory",
"Group",
"Service",
"NonInventory",
],
},
assetAccountRefValue: {
type: "string",
label: "Asset Account Ref Value",
description: "Required for Inventory item types. Reference to the Inventory Asset account that tracks the current value of the inventory. If the same account is used for all inventory items, the current balance of this account will represent the current total value of the inventory. Must be an account with account type of `Other Current Asset`. Query the Account name list resource to determine the appropriate Account object for this reference. Use `Account.Id` from that object for `AssetAccountRef.value`.",
propDefinition: [
quickbooks,
"accountIds",
],
},
invStartDate: {
type: "string",
label: "Inventory Start Date",
description: "Date of opening balance for the inventory transaction. Required when creating an `Item.Type=Inventory`. Required for `Inventory` item types.",
optional: true,
},
expenseAccountRefValue: {
type: "string",
label: "Expense Account Ref Value",
description: "Reference to the expense account used to pay the vendor for this item. Must be an account with account type of `Cost of Goods Sold`. Query the Account name list resource to determine the appropriate Account object for this reference. Use `Account.Id` from that object for `ExpenseAccountRef.value`. See specifications for the ExpenseAccountRef parameters in the [Create an item page](https://developer.intuit.com/app/developer/qbo/docs/api/accounting/all-entities/item#create-an-item).",
propDefinition: [
quickbooks,
"accountIds",
],
},
sku: {
type: "string",
label: "Sku",
description: "The stock keeping unit (SKU) for this Item. This is a company-defined identifier for an item or product used in tracking inventory.",
optional: true,
},
salesTaxIncluded: {
type: "boolean",
label: "Sales Tax Included",
description: "True if the sales tax is included in the item amount, and therefore is not calculated for the transaction.",
optional: true,
},
salesTaxCodeRefValue: {
label: "Sales Tax Code Ref Value",
description: "ID of the referenced sales tax code for the Sales item. Applicable to Service and Sales item types only. Query the TaxCode name list resource to determine the appropriate TaxCode object for this reference. Use `TaxCode.Id` from that object for `SalesTaxCodeRef.value`.",
propDefinition: [
quickbooks,
"taxCodeId",
],
},
purchaseTaxIncluded: {
type: "boolean",
label: "Purchase Tax Included",
description: "True if the purchase tax is included in the item amount, and therefore is not calculated for the transaction.",
optional: true,
},
description: {
type: "string",
label: "Description",
description: "Description of the item.",
optional: true,
},
abatementRate: {
type: "string",
label: "Abatement Rate",
description: "Sales tax abatement rate for India locales.",
optional: true,
},
reverseChargeRate: {
type: "string",
label: "Reverse Charge Rate",
description: "Sales tax reverse charge rate for India locales.",
optional: true,
},
subItem: {
type: "boolean",
label: "Sub Item",
description: "If true, this is a sub item. If false or null, this is a top-level item. Creating inventory hierarchies with traditional inventory items is being phased out in lieu of using categories and sub categories.",
optional: true,
},
taxable: {
type: "boolean",
label: "Taxable",
description: "If true, transactions for this item are taxable. Applicable to US companies, only.",
optional: true,
},
UqcDisplayText: {
type: "string",
label: "UQC Display Text",
description: "Text to be displayed on customer's invoice to denote the Unit of Measure (instead of the standard code).",
optional: true,
},
reorderPoint: {
type: "string",
label: "Reorder Point",
description: "The minimum quantity of a particular inventory item that you need to restock at any given time. The ReorderPoint value cannot be set to null for sparse updates(sparse=true). It can be set to null only for full updates.",
optional: true,
},
purchaseDesc: {
type: "string",
label: "Purchase Description",
description: "Purchase description for the item.",
optional: true,
},
prefVendorRefValue: {
type: "string",
label: "Pref Vendor Ref Value",
description: "Pref vendor ref value",
propDefinition: [
quickbooks,
"vendorIds",
],
},
active: {
type: "boolean",
label: "Active",
description: "If true, the object is currently enabled for use by QuickBooks.",
optional: true,
},
UqcId: {
type: "string",
label: "UQC ID",
description: "ID of Standard Unit of Measure (UQC:Unique Quantity Code) of the item according to GST rule.",
optional: true,
},
purchaseTaxCodeRefValue: {
label: "Purchase Tax Code Ref Value",
description: "The ID for the referenced purchase tax code object as found in the Id field of the object payload. \n\nReference to the purchase tax code for the item. Applicable to Service, Other Charge, and Product (Non-Inventory) item types. Query the TaxCode name list resource to determine the appropriate TaxCode object for this reference. Use `TaxCode.Id` from that object for `PurchaseTaxCodeRef.value`.",
propDefinition: [
quickbooks,
"taxCodeId",
],
},
serviceType: {
type: "string",
label: "Service Type",
description: "Sales tax service type for India locales.",
optional: true,
},
purchaseCost: {
type: "string",
label: "Purchase Cost",
description: "Amount paid when buying or ordering the item, as expressed in the home currency.",
optional: true,
},
unitPrice: {
type: "string",
label: "Unit Price",
description: "Corresponds to the Price/Rate column on the QuickBooks Online UI to specify either unit price, a discount, or a tax rate for item. If used for unit price, the monetary value of the service or product, as expressed in the home currency. If used for a discount or tax rate, express the percentage as a fraction. For example, specify `0.4` for 40% tax",
optional: true,
},
taxClassificationRefValue: {
description: "The ID for the referenced Tax classification object as found in the Id field of the object payload.\n\nTax classification segregates different items into different classifications and the tax classification is one of the key parameters to determine appropriate tax on transactions involving items. Tax classifications are sourced by either tax governing authorities as in India/Malaysia or externally like Exactor. 'Fuel', 'Garments' and 'Soft drinks' are a few examples of tax classification in layman terms. User can choose a specific tax classification for an item while creating it. A level 1 tax classification cannot be associated to an Item",
propDefinition: [
quickbooks,
"taxClassificationId",
],
},
parentRefValue: {
label: "Parent Ref Value",
description: "The ID for the referenced parent item object as found in the Id field of the object payload. \n\nThe immediate parent of the sub item in the hierarchical Category:Sub-category list. If SubItem is true, then ParenRef is required. Query the Item name list resource to determine the appropriate object for this reference. Use `Item.Id` from that object for `ParentRef.value`.",
optional: true,
propDefinition: [
quickbooks,
"itemId",
],
},
},
methods: {
async getSyncToken($) {
const { Item: item } = await this.quickbooks.getItem({
$,
itemId: this.itemId,
});
return item.SyncToken;
},
},
async run({ $ }) {
if (!this.itemId || !this.name) {
throw new ConfigurationError("Must provide itemId and name parameters.");
}
const data = {
sparse: true,
Id: this.itemId,
Name: this.name,
QtyOnHand: this.qtyOnHand,
SyncToken: await this.getSyncToken($),
IncomeAccountRef: this.incomeAccountRefValue && {
value: this.incomeAccountRefValue,
},
Type: this.type,
AssetAccountRef: this.assetAccountRefValue && {
value: this.assetAccountRefValue,
},
InvStartDate: this.invStartDate,
ExpenseAccountRef: this.expenseAccountRefValue && {
value: this.expenseAccountRefValue,
},
Sku: this.sku,
SalesTaxIncluded: this.salesTaxIncluded,
TrackQtyOnHand: this.trackQtyOnHand,
SalesTaxCodeRef: this.salesTaxCodeRefValue && {
value: this.salesTaxCodeRefValue,
},
PurchaseTaxIncluded: this.purchaseTaxIncluded,
Description: this.description,
AbatementRate: this.abatementRate,
ReverseChargeRate: this.reverseChargeRate,
SubItem: this.subItem,
Taxable: this.taxable,
UQCDisplayText: this.UqcDisplayText,
ReorderPoint: this.reorderPoint,
PurchaseDesc: this.purchaseDesc,
PrefVendorRef: this.prefVendorRefValue && {
value: this.prefVendorRefValue,
},
Active: this.active,
UQCId: this.UqcId,
PurchaseTaxCodeRef: this.purchaseTaxCodeRefValue && {
value: this.purchaseTaxCodeRefValue,
},
ServiceType: this.serviceType,
PurchaseCost: this.purchaseCost,
UnitPrice: this.unitPrice,
TaxClassificationRef: this.taxClassificationRefValue && {
value: this.taxClassificationRefValue,
},
};
if (this.parentRefValue || this.parentRefName) {
data["ParentRef"] = {
value: this.parentRefValue,
};
}
const response = await this.quickbooks.updateItem({
$,
data,
});
if (response) {
$.export("summary", `Successfully updated item with ID ${this.itemId}`);
}
return response;
},
};
Chase Roberts@chsrbrts@benedictevans If you haven’t used @pipedream yet, then you haven’t lived.
✨Ellie Day✨@heyelliedayEvaluation update: @pipedream has quite literally been a dream to work with! I’m excited to leverage this tool for all the various workflows I need to write. I’m currently at 11k invocations a day from the initial workflows I’ve written in the past couple weeks.
Michael Braedley@MBraedleyUpdate: I got it working properly, and it's working so well that I'm dropping IFTTT. @pipedream can do everything that IFTTT basic can, and most (if not all things) IFTTT pro can for free or at a reasonable price if you need it. I am recommending it for basically any power user.
Thomas Cutting@mrthomascuttingWant quick+dirty integrations for a serverless workflow - @pipedream is my new go-to 😃
Matthew Roberts@mattdotrobertsday 013 - finally hit node js. This is the secret sauce of taking #nocode projects that one step further. Pumped about getting deeper into @pipedream now
Kenneth Auchenberg 💭@auchenbergYahoo Pipes is back! Kinda 😍 @pipedream
Raymond Camden 🥑@raymondcamdenAwesome video by the @pipedream folks showing real time twitter sentiment analysis integrated with Google Sheets. This is where Pipedream *really* shines, connecting systems together in easy workflows.
Nacho Caballero@nachocaballeroI couldn't recommend @pipedream more. It's an amazing service to integrate different APIs. Much more powerful than Zapier and more user-friendly than AWS Lambda. I'm very proud to wear this t-shirt #NoCode
Jason Snow@jyksnwDeveloped a working prototype environmental sensor IoT solution with @particle Photon, @pipedream, and @MongoDB with full graphing and alerting in less than a day! All amazing technology, will def. be exploring these more.
Steven Terrana@steven_terrana@burgwyn you've inspired me to finally set up my own blog. I'll make sure my first blog post explains the tech behind the setup. think @obsdmd + @GatsbyJS + @pipedream.
🚄 James Augeri, PhD@DotDotJamesWant to low-code your back end, need more horsepower than @Bubble / @KnackHQ, or just miss Yahoo! Pipes? Check out @PipeDream
Sébastien Chopin@AtinuxGitHub issues should be like @linear_app for maintainers. Looking forward more integrations with GH actions or tools like @pipedream 👀
Raul@raul_predescuIf you're a dev and not using @pipedream, you're missing out. Been using it for months, daily. FREE for devs. Plenty of integrations and good limits. Absolutely love it.
Bruno Skvorc@bitfallsSo @pipedream is pretty amazing. In 3 minutes I just made a flow which adds @rickastley's Never Gonna Give You Up to my @spotify playlist whenever a new pull request arrives in an old repo of mine.
Zach Lanich@ZachLanichUm, wow 🤯 @pipedream
Steven Bell@bellontechI just used @pipedream to build a Shopify App. Wow, they make small backed tasks easy.
Jay Hack 🎩🇺🇸@_jayhack_Very impressed with this bad boi - it reminds me of a @PalantirTech internal tool, but geared towards integrations instead of data analysis and far more customizable. Great expectations here 🚀🤩
Tree Sturgeon 🔥🚴♂️🌳@philsturgeonFor context this is day 2 of a really challenging and stupid migration from Notion to @airtable with disparate/missing data. It's going better than expected and thanks to @pipedream I don't have to bother the iOS dev to add W3W.