Delete Ticket with Zendesk API on New Folder Created from Wrike API

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

Trigger workflow on

New Folder Created from the Wrike 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 Wrike 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 Folder Created trigger
1. Connect your Wrike account
2. Optional- Select a Folder ID
3. Optional- Select a Space ID
4. Optional- Configure Recursive
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 Folder Created on Wrike

Description:Emit new event when a folder is created

Version:0.0.2

Key:wrike-new-folder-created

View on GitHub

Wrike Overview#

Wrike API on Pipedream exposes the robust task and project management features of Wrike, enabling you to automate workflows across various apps and services. With it, you can programmatically access and manipulate tasks, folders, projects, and users within Wrike. This API lends itself to a multitude of automation possibilities, like synchronizing project updates across platforms, streamlining notifications and reporting, or even managing resource allocation based on project workload.

Trigger Code#

import base from "../common/webhooks.mjs";
import constants from "../common/constants.mjs";

export default {
  ...base,
  key: "wrike-new-folder-created",
  name: "New Folder Created",
  description: "Emit new event when a folder is created",
  type: "source",
  version: "0.0.2",
  props: {
    ...base.props,
    folderId: {
      propDefinition: [
        base.props.wrike,
        "folderId",
      ],
      description: "Receive notifications for folders in a folder and, optionally, in its subfolders. Leave blank to receive notifications for all folders in the account",
      optional: true,
    },
    spaceId: {
      propDefinition: [
        base.props.wrike,
        "spaceId",
      ],
      description: "Receive notifications for changes to folders within a space. Leave blank to receive notifications for all folders in the account",
      optional: true,
    },
    recursive: {
      type: "boolean",
      label: "Recursive",
      description: "Specifies whether hook should listen to events for subfolders or tasks anywhere in the hierarchy. Defaults to `false`",
      optional: true,
    },
  },
  hooks: {
    ...base.hooks,
    async deploy() {
      console.log("Retrieving historical events...");
      const folders = await this.wrike.listFolders({
        folderId: this.folderId,
        spaceId: this.spaceId,
      });
      for (const folder of folders.slice(-constants.DEPLOY_LIMIT)) {
        this.emitEvent(folder);
      }
    },
  },
  methods: {
    ...base.methods,
    eventTypes() {
      return [
        "FolderCreated",
      ];
    },
    async emitEvent(folder) {
      this.$emit(folder, {
        id: folder.id,
        summary: `New folder: ${folder.title}`,
        ts: folder.createdDate,
      });
    },
  },
  async run(event) {
    console.log("Webhook received");
    for (const data of event.body) {
      const folder = await this.wrike.getFolder({
        folderId: data.folderId,
      });
      this.emitEvent(folder);
    }
  },
};

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
Wrike	`wrike`	`app`	This component uses the Wrike 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.
Folder ID	`folderId`	`string`	Select a value from the drop down menu.
Space ID	`spaceId`	`string`	Select a value from the drop down menu.
Recursive	`recursive`	`boolean`	Specifies whether hook should listen to events for subfolders or tasks anywhere in the hierarchy. Defaults to `false`

Trigger Authentication#

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

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

About Wrike#

Online project management software

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

Delete Ticket with Zendesk API on New Folder Created from Wrike API

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

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

Developers ♥ Pipedream

1-24of2,400+apps by most popular

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