New Task Created from Wrike API

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

Trigger workflow on

New Task Created from the Wrike API

Next, do this

Connect to 2,400+ APIs using code and no-code building blocks

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#

Trigger a workflow on New Task Created with Wrike API. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Configure the New Task Created trigger
1. Connect your Wrike account
2. Optional- Select a Folder ID
3. Optional- Select a Space ID
4. Optional- Configure Recursive
Add steps to connect to 2,400+ APIs using code and no-code building blocks
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Integrations#

Send Message with Discord Webhook API on New Task Created from Wrike API

Wrike + Discord Webhook

Try it

Get Film with SWAPI - Star Wars API on New Task Created from Wrike API

Wrike + SWAPI - Star Wars

Try it

Create Multiple Records with Airtable API on New Task Created from Wrike API

Wrike + Airtable (API Key)

Try it

Send any HTTP Request with HTTP / Webhook API on New Task Created from Wrike API

Wrike + HTTP / Webhook

Try it

Get Backlinks with Ahrefs API on New Task Created from Wrike API

Wrike + Ahrefs

Try it

Details#

This is a pre-built, source-available component from Pipedream's GitHub repo. The component is 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.

New Task Created on Wrike

Description:Emit new event when a task is created

Version:0.0.2

Key:wrike-new-task-created

View on GitHub

Code#

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

export default {
  ...base,
  key: "wrike-new-task-created",
  name: "New Task Created",
  description: "Emit new event when a task is created",
  type: "source",
  version: "0.0.2",
  props: {
    ...base.props,
    folderId: {
      propDefinition: [
        base.props.wrike,
        "folderId",
      ],
      description: "Receive notifications for tasks in a folder and, optionally, in its subfolders. Leave blank to receive notifications for all tasks in the account",
      optional: true,
    },
    spaceId: {
      propDefinition: [
        base.props.wrike,
        "spaceId",
      ],
      description: "Receive notifications for changes to tasks, folders, and projects within a space. Leave blank to receive notifications for all tasks 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 tasks = await this.wrike.listTasks({
        folderId: this.folder,
        spaceId: this.spaceId,
        params: {
          sortOrder: "desc",
          limit: constants.DEPLOY_LIMIT,
        },
      });
      for (const task of tasks.reverse()) {
        this.emitEvent(task);
      }
    },
  },
  methods: {
    ...base.methods,
    eventTypes() {
      return [
        "TaskCreated",
      ];
    },
    async emitEvent(task) {
      this.$emit(task, {
        id: task.id,
        summary: `New task: ${task.title}`,
        ts: task.createdDate,
      });
    },
  },
  async run(event) {
    console.log("Webhook received");
    for (const data of event.body) {
      const task = await this.wrike.getTask({
        taskId: data.taskId,
      });
      this.emitEvent(task);
    }
  },
};

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`

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: