Create Hardware Asset with Snipe-IT API on Ticket Closed (Instant) from Zendesk API

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

Trigger workflow on

Ticket Closed (Instant) from the Zendesk API

Next, do this

Create 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 Zendesk 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 Ticket Closed (Instant) trigger
1. Connect your Zendesk account
2. Optional- Select a Trigger Category ID
3. Optional- Configure Custom Subdomain
4. Optional- Select one or more Fields
5. Optional- Configure JSON Body
Configure the Create Hardware Asset action
1. Connect your Snipe-IT account
2. Select a Model
3. Select a Status
4. Optional- Configure Asset Tag
5. Optional- Configure Asset Name
6. Optional- Configure Image
7. Optional- Configure Serial Number
8. Optional- Configure Purchase Date
9. Optional- Configure Purchase Cost
10. Optional- Configure Order Number
11. Optional- Configure Notes
12. Optional- Configure Archived
13. Optional- Configure Warranty Months
14. Optional- Configure Depreciate
15. Optional- Select a Supplier
16. Optional- Configure Requestable
17. Optional- Select a RTD Location
18. Optional- Configure Last Audit Date
19. Optional- Select a Location
20. Optional- Configure BYOD
21. 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#

Ticket Closed (Instant) on Zendesk

Description:Emit new event when a ticket has changed to closed status

Version:0.2.6

Key:zendesk-ticket-closed

View on GitHub

Zendesk Overview#

The Zendesk API enables seamless integration of Zendesk's customer service platform with your existing business processes and third-party applications. By leveraging this API with Pipedream, you can automate ticket tracking, sync customer data, escalate issues, and streamline communication across multiple channels. This can significantly increase efficiency, accelerate response times, and enhance the overall customer experience. Automations can range from simple notifications to complex workflows involving data transformation and multi-step actions across various services.

Trigger Code#

import common from "../common/ticket.mjs";

export default {
  ...common,
  name: "Ticket Closed (Instant)",
  key: "zendesk-ticket-closed",
  type: "source",
  description: "Emit new event when a ticket has changed to closed status",
  version: "0.2.6",
  dedupe: "unique",
  methods: {
    ...common.methods,
    getWebhookName() {
      return "Ticket Closed Webhook";
    },
    getTriggerTitle() {
      return "Ticket Closed Trigger";
    },
    getTriggerConditions() {
      return {
        all: [
          {
            field: "update_type",
            value: "Change",
          },
          {
            field: "status",
            operator: "value",
            value: "closed",
          },
        ],
      };
    },
  },
};

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
Zendesk	`app`	`app`	This component uses the Zendesk app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
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.
Trigger Category ID	`categoryId`	`string`	Select a value from the drop down menu.
Custom Subdomain	`customSubdomain`	`string`	For Enterprise Zendesk accounts: optionally specify the subdomain to use. This will override the subdomain that was provided when connecting your Zendesk account to Pipedream. For example, if you Zendesk URL is https://examplehelp.zendesk.com, your subdomain is `examplehelp`
Fields	`fields`	`string[]`	Select a value from the drop down menu.
JSON Body	`jsonBody`	`string`	Custom JSON Body of the incoming payload. Setting `jsonBody` will overwrite the `fields` prop

Trigger Authentication#

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

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

triggers:writewebhooks:writereadtickets:writetickets:readusers:writeorganizations:readorganizations:write

About Zendesk#

Zendesk is award-winning customer service software trusted by 200K+ customers. Make customers happy via text, mobile, phone, email, live chat, social media.

Action#

Create Hardware Asset on Snipe-IT

Description:Creates a new hardware asset in Snipe-IT. [See the documentation](https://snipe-it.readme.io/reference/hardware-create)

Version:0.0.1

Key:snipe_it-create-hardware

View on GitHub

Action Code#

import app from "../../snipe_it.app.mjs";
import utils from "../../common/utils.mjs";

export default {
  key: "snipe_it-create-hardware",
  name: "Create Hardware Asset",
  description: "Creates a new hardware asset in Snipe-IT. [See the documentation](https://snipe-it.readme.io/reference/hardware-create)",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    modelId: {
      propDefinition: [
        app,
        "modelId",
      ],
    },
    statusId: {
      propDefinition: [
        app,
        "statusId",
      ],
    },
    assetTag: {
      propDefinition: [
        app,
        "assetTag",
      ],
    },
    name: {
      propDefinition: [
        app,
        "name",
      ],
    },
    image: {
      propDefinition: [
        app,
        "image",
      ],
    },
    serial: {
      propDefinition: [
        app,
        "serial",
      ],
    },
    purchaseDate: {
      propDefinition: [
        app,
        "purchaseDate",
      ],
    },
    purchaseCost: {
      propDefinition: [
        app,
        "purchaseCost",
      ],
    },
    orderNumber: {
      propDefinition: [
        app,
        "orderNumber",
      ],
    },
    notes: {
      propDefinition: [
        app,
        "notes",
      ],
    },
    archived: {
      propDefinition: [
        app,
        "archived",
      ],
    },
    warrantyMonths: {
      propDefinition: [
        app,
        "warrantyMonths",
      ],
    },
    depreciate: {
      propDefinition: [
        app,
        "depreciate",
      ],
    },
    supplierId: {
      propDefinition: [
        app,
        "supplierId",
      ],
    },
    requestable: {
      propDefinition: [
        app,
        "requestable",
      ],
    },
    rtdLocationId: {
      label: "RTD Location",
      description: "Select the default location for this asset",
      propDefinition: [
        app,
        "locationId",
      ],
    },
    lastAuditDate: {
      propDefinition: [
        app,
        "lastAuditDate",
      ],
    },
    locationId: {
      propDefinition: [
        app,
        "locationId",
      ],
    },
    byod: {
      propDefinition: [
        app,
        "byod",
      ],
    },
    customFields: {
      propDefinition: [
        app,
        "customFields",
      ],
    },
  },
  async run({ $ }) {
    const {
      app,
      modelId,
      statusId,
      assetTag,
      name,
      image,
      serial,
      purchaseDate,
      purchaseCost,
      orderNumber,
      notes,
      archived,
      warrantyMonths,
      depreciate,
      supplierId,
      requestable,
      rtdLocationId,
      lastAuditDate,
      locationId,
      byod,
      customFields,
    } = this;

    const parsedCustomFields = utils.parseJson(customFields);

    const response = await app.createHardware({
      $,
      data: {
        model_id: modelId,
        status_id: statusId,
        ...(name && {
          name,
        }),
        ...(assetTag && {
          asset_tag: assetTag,
        }),
        ...(image && {
          image,
        }),
        ...(serial && {
          serial,
        }),
        ...(purchaseDate && {
          purchase_date: purchaseDate,
        }),
        ...(purchaseCost && {
          purchase_cost: purchaseCost,
        }),
        ...(orderNumber && {
          order_number: orderNumber,
        }),
        ...(notes && {
          notes,
        }),
        ...(archived !== undefined && {
          archived,
        }),
        ...(warrantyMonths && {
          warranty_months: warrantyMonths,
        }),
        ...(depreciate !== undefined && {
          depreciate,
        }),
        ...(supplierId && {
          supplier_id: supplierId,
        }),
        ...(requestable !== undefined && {
          requestable,
        }),
        ...(rtdLocationId && {
          rtd_location_id: rtdLocationId,
        }),
        ...(lastAuditDate && {
          last_audit_date: lastAuditDate,
        }),
        ...(locationId && {
          location_id: locationId,
        }),
        ...(byod !== undefined && {
          byod,
        }),
        ...(typeof(parsedCustomFields) === "object"
          ? parsedCustomFields
          : {}
        ),
      },
    });

    $.export("$summary", `Successfully created 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.
Model	`modelId`	`integer`	Select a value from the drop down menu.
Status	`statusId`	`integer`	Select a value from the drop down menu.
Asset Tag	`assetTag`	`string`	The asset tag for the asset
Asset Name	`name`	`string`	The name of the asset
Image	`image`	`string`	Base64 encoded image. Eg. `data:@[mime];base64,[base64encodeddata]`.
Serial Number	`serial`	`string`	The serial number of the asset
Purchase Date	`purchaseDate`	`string`	The purchase date of the asset (YYYY-MM-DD format)
Purchase Cost	`purchaseCost`	`string`	The purchase cost of the asset
Order Number	`orderNumber`	`string`	The order number of the asset
Notes	`notes`	`string`	Notes about the asset
Archived	`archived`	`boolean`	Whether the asset is archived
Warranty Months	`warrantyMonths`	`integer`	The warranty period in months
Depreciate	`depreciate`	`boolean`	Whether the asset is depreciated
Supplier	`supplierId`	`integer`	Select a value from the drop down menu.
Requestable	`requestable`	`boolean`	Whether this asset can be requested by users
RTD Location	`rtdLocationId`	`integer`	Select a value from the drop down menu.
Last Audit Date	`lastAuditDate`	`string`	The date of the last audit for this asset (YYYY-MM-DD format)
Location	`locationId`	`integer`	Select a value from the drop down menu.
BYOD	`byod`	`boolean`	Whether this asset is a BYOD device.
Custom Fields	`customFields`	`object`	Custom fields for the asset

Create Hardware Asset with Snipe-IT API on Ticket Closed (Instant) from Zendesk API

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

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

Developers ♥ Pipedream

1-24of2,800+apps by most popular

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