Update Hardware Asset with Snipe-IT API on New Download Counts from npm API

Pipedream makes it easy to connect APIs for Snipe-IT, npm and 2,800+ other apps remarkably fast.

Trigger workflow on

New Download Counts from the npm API

Next, do this

Update Hardware Asset with the Snipe-IT 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 npm trigger and Snipe-IT action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Download Counts trigger
1. Connect your npm account
2. Configure timer
3. Select a Period
4. Optional- Configure Package
Configure the Update Hardware Asset action
1. Connect your Snipe-IT account
2. Select a Hardware Asset
3. Optional- Configure Asset Tag
4. Optional- Configure Notes
5. Optional- Select a Status
6. Optional- Select a Model
7. Optional- Configure Last Checkout
8. Optional- Select a Assigned User
9. Optional- Select a Assigned Location
10. Optional- Select a Assigned Asset
11. Optional- Select a Company
12. Optional- Configure Serial Number
13. Optional- Configure Order Number
14. Optional- Configure Warranty Months
15. Optional- Configure Purchase Cost
16. Optional- Configure Purchase Date
17. Optional- Configure Requestable
18. Optional- Configure Archived
19. Optional- Select a Location
20. Optional- Configure Asset Name
21. Optional- Select a Location
22. Optional- Configure BYOD
23. Optional- Configure Custom Fields
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 Download Counts on npm

Description:Emit new event with the latest count of downloads for an npm package. [See the documentation](https://github.com/npm/registry/blob/main/docs/download-counts.md).

Version:0.1.0

Key:npm-download-counts

View on GitHub

Trigger Code#

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

export default {
  key: "npm-download-counts",
  name: "New Download Counts",
  description: "Emit new event with the latest count of downloads for an npm package. [See the documentation](https://github.com/npm/registry/blob/main/docs/download-counts.md).",
  version: "0.1.0",
  type: "source",
  props: {
    app,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      description: "One day interval time is recommended because NPM only update metrics once a day. [See the documentation](https://github.com/npm/registry/blob/main/docs/download-counts.md#data-source).",
      default: {
        intervalSeconds: 60 * 60 * 24,
      },
    },
    period: {
      type: "string",
      label: "Period",
      description: "Select last-day, last-week or last-month.",
      optional: false,
      default: "last-day",
      options: [
        "last-day",
        "last-week",
        "last-month",
      ],
    },
    packageName: {
      type: "string",
      label: "Package",
      description: "Enter an npm package name. Leave blank for all",
      optional: true,
    },
  },
  methods: {
    getDownloadCounts({
      period, packageName, ...args
    } = {}) {
      const basePath = `/downloads/point/${encodeURIComponent(period)}`;
      return this.app.makeRequest({
        path: packageName
          ? `${basePath}/${encodeURIComponent(packageName)}`
          : basePath,
        ...args,
      });
    },
  },
  async run({ timestamp: ts }) {
    const {
      getDownloadCounts,
      period,
      packageName,
    } = this;

    const response = await getDownloadCounts({
      period,
      packageName,
    });

    this.$emit(response, {
      id: ts,
      summary: `New Download Count ${response.downloads}`,
      ts,
    });
  },
};

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
npm	`app`	`app`	This component uses the npm app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`	One day interval time is recommended because NPM only update metrics once a day. See the documentation
Period	`period`	`string`	Select a value from the drop down menu:`last-daylast-weeklast-month`
Package	`packageName`	`string`	Enter an npm package name. Leave blank for all

Trigger Authentication#

The npm API does not require authentication.

About npm#

Node package manager

Action#

Update Hardware Asset on Snipe-IT

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

Key:snipe_it-update-hardware

View on GitHub

Action Code#

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;
  },
};

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
Snipe-IT	`app`	`app`	This component uses the Snipe-IT app.
Hardware Asset	`hardwareId`	`integer`	Select a value from the drop down menu.
Asset Tag	`assetTag`	`string`	Update the asset tag
Notes	`notes`	`string`	Update notes about the asset
Status	`statusId`	`integer`	Select a value from the drop down menu.
Model	`modelId`	`integer`	Select a value from the drop down menu.
Last Checkout	`lastCheckout`	`string`	Update the last checkout date
Assigned User	`assignedUser`	`integer`	Select a value from the drop down menu.
Assigned Location	`assignedLocation`	`integer`	Select a value from the drop down menu.
Assigned Asset	`assignedAsset`	`integer`	Select a value from the drop down menu.
Company	`companyId`	`integer`	Select a value from the drop down menu.
Serial Number	`serial`	`string`	Serial number of the asset
Order Number	`orderNumber`	`string`	Update the order number
Warranty Months	`warrantyMonths`	`integer`	Update the warranty period
Purchase Cost	`purchaseCost`	`string`	Update the purchase cost
Purchase Date	`purchaseDate`	`string`	Update the purchase date
Requestable	`requestable`	`boolean`	Update whether the asset can be requested
Archived	`archived`	`boolean`	Update the archived status
Location	`rtdLocationId`	`integer`	Select a value from the drop down menu.
Asset Name	`name`	`string`	Update the name of the asset
Location	`locationId`	`integer`	Select a value from the drop down menu.
BYOD	`byod`	`boolean`	Update the BYOD
Custom Fields	`customFields`	`object`	Update custom fields using DB field names from Settings > Custom Fields

Action Authentication#

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

About Snipe-IT#

Free open source IT asset management

More Ways to Connect Snipe-IT + npm#

Other Popular Integrations#

Create Hardware Asset with Snipe-IT API on New Download Counts from npm API

npm + Snipe-IT

Try it

Create Hardware Asset with Snipe-IT API on New Package Version from npm API

npm + Snipe-IT

Try it

Create User with Snipe-IT API on New Download Counts from npm API

npm + Snipe-IT

Try it

Create User with Snipe-IT API on New Package Version from npm API

npm + Snipe-IT

Try it

Get User Assets with Snipe-IT API on New Download Counts from npm API

npm + Snipe-IT

Try it

Popular Triggers#

New Download Counts from the npm API

Emit new event with the latest count of downloads for an npm package. See the documentation

Try it

New Package Version from the npm API

Emit new event when a new version of an npm package is published. See the documentation

Try it

Popular Actions#

Create Hardware Asset with the Snipe-IT API

Creates a new hardware asset in Snipe-IT. See the documentation

Try it

Create User with the Snipe-IT API

Creates a new user in Snipe-IT with profile information required for asset or license assignments. See the documentation

Try it

Get Hardware Asset with the Snipe-IT API

Retrieves details of a specific hardware asset by ID. See the documentation

Try it

Get License with the Snipe-IT API

Retrieves license details including seat count, expiration, and current usage metrics. Note: The response returns 'product_key' but uses 'serial' field for POST/PUT/PATCH requests. See the documentation

Try it

Get User Assets with the Snipe-IT API

Retrieves all assets currently assigned to a specific user. Useful for audits and inventory reviews. See the documentation

Try it