import app from "../../snipe_it.app.mjs";
import utils from "../../common/utils.mjs";
export default {
key: "snipe_it-update-hardware",
name: "Update Hardware Asset",
description: "Partially updates information about an existing hardware asset. [See the documentation](https://snipe-it.readme.io/reference/hardware-partial-update)",
version: "0.0.1",
type: "action",
props: {
app,
hardwareId: {
propDefinition: [
app,
"hardwareId",
],
description: "Select the hardware asset to update",
},
assetTag: {
propDefinition: [
app,
"assetTag",
],
description: "Update the asset tag",
},
notes: {
propDefinition: [
app,
"notes",
],
description: "Update notes about the asset",
},
statusId: {
optional: true,
propDefinition: [
app,
"statusId",
],
description: "Update the status of the asset",
},
modelId: {
optional: true,
propDefinition: [
app,
"modelId",
],
description: "Update the model of the asset",
},
lastCheckout: {
propDefinition: [
app,
"lastCheckout",
],
description: "Update the last checkout date",
},
assignedUser: {
optional: true,
propDefinition: [
app,
"userId",
],
label: "Assigned User",
description: "The ID of the user the asset should be checked out to",
},
assignedLocation: {
optional: true,
propDefinition: [
app,
"userId",
],
label: "Assigned Location",
description: "The ID of the user the location should be checked out to",
},
assignedAsset: {
optional: true,
propDefinition: [
app,
"hardwareId",
],
label: "Assigned Asset",
description: "The ID of the asset the asset should be checked out to",
},
companyId: {
propDefinition: [
app,
"companyId",
],
description: "The ID of an associated company id",
},
serial: {
propDefinition: [
app,
"serial",
],
description: "Serial number of the asset",
},
orderNumber: {
propDefinition: [
app,
"orderNumber",
],
description: "Update the order number",
},
warrantyMonths: {
propDefinition: [
app,
"warrantyMonths",
],
description: "Update the warranty period",
},
purchaseCost: {
propDefinition: [
app,
"purchaseCost",
],
description: "Update the purchase cost",
},
purchaseDate: {
propDefinition: [
app,
"purchaseDate",
],
description: "Update the purchase date",
},
requestable: {
propDefinition: [
app,
"requestable",
],
description: "Update whether the asset can be requested",
},
archived: {
propDefinition: [
app,
"archived",
],
description: "Update the archived status",
},
rtdLocationId: {
propDefinition: [
app,
"locationId",
],
description: "Update the RTD location",
},
name: {
propDefinition: [
app,
"name",
],
description: "Update the name of the asset",
},
locationId: {
propDefinition: [
app,
"locationId",
],
description: "Update the location of the asset",
},
byod: {
propDefinition: [
app,
"byod",
],
description: "Update the BYOD",
},
customFields: {
propDefinition: [
app,
"customFields",
],
description: "Update custom fields using DB field names from Settings > Custom Fields",
},
},
async run({ $ }) {
const {
app,
hardwareId,
assetTag,
notes,
statusId,
modelId,
lastCheckout,
assignedUser,
assignedLocation,
assignedAsset,
companyId,
serial,
orderNumber,
warrantyMonths,
purchaseCost,
purchaseDate,
requestable,
archived,
rtdLocationId,
name,
locationId,
byod,
customFields,
} = this;
const parsedCustomFields = utils.parseJson(customFields);
const data = {
...(assetTag && {
asset_tag: assetTag,
}),
...(notes && {
notes,
}),
...(statusId && {
status_id: statusId,
}),
...(modelId && {
model_id: modelId,
}),
...(lastCheckout && {
last_checkout: lastCheckout,
}),
...(assignedUser && {
assigned_user_id: assignedUser,
}),
...(assignedLocation && {
assigned_location_id: assignedLocation,
}),
...(assignedAsset && {
assigned_asset_id: assignedAsset,
}),
...(companyId && {
company_id: companyId,
}),
...(serial && {
serial,
}),
...(orderNumber && {
order_number: orderNumber,
}),
...(warrantyMonths && {
warranty_months: warrantyMonths,
}),
...(purchaseCost && {
purchase_cost: purchaseCost,
}),
...(purchaseDate && {
purchase_date: purchaseDate,
}),
...(requestable && {
requestable,
}),
...(archived && {
archived,
}),
...(rtdLocationId && {
rtd_location_id: rtdLocationId,
}),
...(name && {
name,
}),
...(locationId && {
location_id: locationId,
}),
...(byod && {
byod,
}),
...(typeof(parsedCustomFields) === "object"
? parsedCustomFields
: {}
),
};
if (Object.keys(data).length === 0) {
throw new Error("At least one field must be provided to update");
}
const response = await app.updateHardware({
$,
hardwareId,
data,
});
$.export("$summary", `Successfully updated hardware asset with ID \`${response.payload.id}\``);
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.
