Delay by N milliseconds with Helper Functions API on New Folder Created from Wrike API

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

Trigger workflow on

New Folder Created from the Wrike API

Next, do this

Delay by N milliseconds with the Helper Functions 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 Helper Functions 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 Delay by N milliseconds action
1. Connect your Helper Functions account
2. Configure Number of milliseconds to delay workflow execution
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#

Delay by N milliseconds on Helper Functions

Description:Delays the execution of your workflow for the specified number of milliseconds

Version:0.1.1

Key:helper_functions-delay

View on GitHub

Helper Functions Overview#

The Helper Functions app on Pipedream is a set of pre-built functions that streamline common tasks in your workflows. It acts like a Swiss Army knife for developers, providing essential tools such as format conversion, date manipulation, and text processing. By leveraging these functions, you can reduce the boilerplate code needed for routine operations, speeding up the development of intricate automations. The Helper Functions API can be a game changer when it comes to tasks like parsing dates in user-friendly formats, encoding and decoding data, or generating UUIDs, making them more efficient and less error-prone.

Action Code#

// legacy_hash_id: a_m8iXpW
import helper_functions from "../../helper_functions.app.mjs";

export default {
  key: "helper_functions-delay",
  name: "Delay by N milliseconds",
  description: "Delays the execution of your workflow for the specified number of milliseconds",
  version: "0.1.1",
  type: "action",
  props: {
    helper_functions,
    ms: {
      type: "string",
      label: "Number of milliseconds to delay workflow execution",
    },
  },
  async run({ $ }) {
    await new Promise((resolve) => setTimeout(resolve, this.ms || 0));
    $.export("$summary", `Workflow successfully delayed for ${this.ms} ms`);
  },
};