Delete Ticket with Zendesk API on New Issue Event from Sifter API

Pipedream makes it easy to connect APIs for Zendesk, Sifter and 2,400+ other apps remarkably fast.

Trigger workflow on

New Issue Event from the Sifter API

Next, do this

Delete Ticket with the Zendesk 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 Sifter trigger and Zendesk action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Issue Event trigger
1. Connect your Sifter account
2. Configure timer
3. Select a Project Id
Configure the Delete Ticket action
1. Connect your Zendesk account
2. Select a Ticket ID
3. Optional- Configure Custom Subdomain
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 Issue Event on Sifter

Description:Emit new events when a new issue is created. [See the docs here](https://sifterapp.com/developer/documentation/issues/#listing)

Version:0.0.1

Key:sifter-new-issue

View on GitHub

Sifter Overview#

The Sifter API enables developers to craft workflows for tracking and managing customer interactions and support inquiries efficiently. By leveraging the Sifter API on Pipedream, users can automate issue tracking, streamline customer communication, and ensure quick resolution of support tickets. With Pipedream's ability to connect to hundreds of apps, you can create multi-step workflows that trigger actions in other tools, leading to increased productivity and a better support experience.

Trigger Code#

import app from "../../sifter.app.mjs";
import common from "../common.mjs";

export default {
  key: "sifter-new-issue",
  name: "New Issue Event",
  description: "Emit new events when a new issue is created. [See the docs here](https://sifterapp.com/developer/documentation/issues/#listing)",
  version: "0.0.1",
  type: "source",
  ...common,
  props: {
    app,
    ...common.props,
    projectId: {
      propDefinition: [
        app,
        "projectId",
      ],
    },
  },
  methods: {
    ...common.methods,
    getResourceFn() {
      return this.app.getIssues;
    },
    getResourceFnArgs() {
      return {
        projectId: this.projectId,
      };
    },
    getSummary(item) {
      return `New issue is created with number(${item.number}) and subject(${item.subject})`;
    },
    getResourceKey() {
      return "issues";
    },
    compareFn(item) {
      return new Date(item.created_at).getTime() > this.getLastFetchTime();
    },
    getDateKey() {
      return "created_at";
    },
  },
};

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
Sifter	`app`	`app`	This component uses the Sifter app.
	`timer`	`$.interface.timer`
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Project Id	`projectId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

To get your Access Key, first sign into your account, then:

Click the “My Profile” link along the top of the page
Click the "Account" tab
Click the “API and Access Keys” link in the right sidebar of the page
Fill in the “Create New Access Key” form at the bottom of the page and click “Create Access Key”

Account Subdomain is the subdomain that you have created during the registration process.

If you have already logged in, to get your Account Subdomain:
Click the "Projects & Issues" link along the top of the page
Click on any project.
Click gear icon next to the project name.
On the right menu find "Integrations" and click on it.
Find your Account Subdomain on Github section.

About Sifter#

Simple and streamlined. Sifter makes issue tracking convenient for even your least technical team members so that everyone can get involved and help find and resolve issues sooner.

Action#

Delete Ticket on Zendesk

Description:Deletes a ticket. [See the documentation](https://developer.zendesk.com/api-reference/ticketing/tickets/tickets/#delete-ticket).

Version:0.1.2

Key:zendesk-delete-ticket

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.

Action Code#

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

export default {
  key: "zendesk-delete-ticket",
  name: "Delete Ticket",
  description: "Deletes a ticket. [See the documentation](https://developer.zendesk.com/api-reference/ticketing/tickets/tickets/#delete-ticket).",
  type: "action",
  version: "0.1.2",
  props: {
    app,
    ticketId: {
      propDefinition: [
        app,
        "ticketId",
      ],
    },
    customSubdomain: {
      propDefinition: [
        app,
        "customSubdomain",
      ],
    },
  },
  methods: {
    deleteTicket({
      ticketId, ...args
    } = {}) {
      return this.app.delete({
        path: `/tickets/${ticketId}`,
        ...args,
      });
    },
  },
  async run({ $: step }) {
    const {
      ticketId,
      customSubdomain,
    } = this;

    await this.deleteTicket({
      step,
      ticketId,
      customSubdomain,
    });

    step.export("$summary", "Successfully deleted ticket");

    return true;
  },
};

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
Zendesk	`app`	`app`	This component uses the Zendesk app.
Ticket ID	`ticketId`	`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`

Action 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