Find Row with PostgreSQL API on New Folder Created from Wrike API

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

Trigger workflow on

New Folder Created from the Wrike API

Next, do this

Find Row with the PostgreSQL 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 PostgreSQL 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 Find Row action
1. Connect your PostgreSQL account
2. Select a Schema
3. Select a Table
4. Select a Lookup Column
5. Select a Lookup Value
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#

Find Row on PostgreSQL

Description:Finds a row in a table via a lookup column. [See the documentation](https://node-postgres.com/features/queries)

Version:2.0.6

Key:postgresql-find-row

View on GitHub

PostgreSQL Overview#

On Pipedream, you can leverage the PostgreSQL app to create workflows that automate database operations, synchronize data across platforms, and react to database events in real-time. Think handling new row entries, updating records from webhooks, or even compiling reports on a set schedule. Pipedream's serverless platform provides a powerful way to connect PostgreSQL with a variety of apps, enabling you to create tailored automation that fits your specific needs.

Action Code#

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

export default {
  name: "Find Row",
  key: "postgresql-find-row",
  description: "Finds a row in a table via a lookup column. [See the documentation](https://node-postgres.com/features/queries)",
  version: "2.0.6",
  type: "action",
  props: {
    postgresql,
    schema: {
      propDefinition: [
        postgresql,
        "schema",
      ],
    },
    table: {
      propDefinition: [
        postgresql,
        "table",
        (c) => ({
          schema: c.schema,
        }),
      ],
    },
    column: {
      propDefinition: [
        postgresql,
        "column",
        (c) => ({
          table: c.table,
          schema: c.schema,
        }),
      ],
      label: "Lookup Column",
      description: "Find row by searching for a value in this column. Returns first row found",
    },
    value: {
      propDefinition: [
        postgresql,
        "value",
        (c) => ({
          table: c.table,
          column: c.column,
          schema: c.schema,
        }),
      ],
    },
  },
  async run({ $ }) {
    const {
      schema,
      table,
      column,
      value,
    } = this;
    try {
      const res = await this.postgresql.findRowByValue(
        schema,
        table,
        column,
        value,
      );
      const summary = res
        ? "Row found"
        : "Row not found";
      $.export("$summary", summary);
      return res;
    } catch (error) {
      let errorMsg = "Row not retrieved due to an error. ";
      errorMsg += `${error}`.includes("SSL verification failed")
        ? "This could be because SSL verification failed. To resolve this, reconnect your account and set SSL Verification Mode: Skip Verification, and try again."
        : `${error}`;
      throw new Error(errorMsg);
    }
  },
};

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
PostgreSQL	`postgresql`	`app`	This component uses the PostgreSQL app.
Schema	`schema`	`string`	Select a value from the drop down menu.
Table	`table`	`string`	Select a value from the drop down menu.
Lookup Column	`column`	`string`	Select a value from the drop down menu.
Lookup Value	`value`	`string`	Select a value from the drop down menu.

Action Authentication#

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

Connecting to Restricted Databases

Either enable the shared static IP for this account below, or configure a VPC to deploy any workflow in your workspace to a private network with a dedicated static IP. Learn more in our docs.

SSL Setup

Configure SSL on your PostgreSQL database by providing the CA (Certificate Authority), and choosing between Full Verification, Verify Certificate Authority (CA), or Skip Verification. Skipping verification is not recommended as this has serious security implications.