Delete Row(s) with PostgreSQL API on New Deploy Failed from DeployHQ API

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

Trigger workflow on

New Deploy Failed from the DeployHQ API

Next, do this

Delete Row(s) 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 DeployHQ 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 Deploy Failed trigger
1. Connect your DeployHQ account
Configure the Delete Row(s) 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 Deploy Failed on DeployHQ

Description:Emit new event when a deploy fails

Version:0.0.2

Key:deployhq-deploy-failed

View on GitHub

DeployHQ Overview#

DeployHQ is a service that automates the deployment of your web applications. By integrating with version control systems, DeployHQ can automatically deploy code changes to various environments. Using the DeployHQ API on Pipedream, you can orchestrate deployments, manage your projects, and synchronize deployment activities with other tools in your toolchain. It opens up possibilities for custom deployment workflows, notifications, monitoring, and more, all connected within the Pipedream ecosystem.

Trigger Code#

import common, { STATUS_FAILED } from "../common.mjs";

export default {
  ...common,
  key: "deployhq-deploy-failed",
  name: "New Deploy Failed",
  version: "0.0.2",
  description: "Emit new event when a deploy fails",
  type: "source",
  async run(request) {
    const { payload } = this.validateRequest(request);

    if (payload.status !== STATUS_FAILED) {
      console.log(`Deploy status [${payload.status}] is not ${STATUS_FAILED}`);
      return;
    }

    this.$emit({
      payload,
    }, {
      id: payload.identifier,
      summary: `Failed ${payload.identifier}`,
      ts: Date.now(),
    });
  },
};

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
DeployHQ	`deployHq`	`app`	This component uses the DeployHQ app.
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.

Trigger Authentication#

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

DeployHQ requires their users enter their email, API Key, and account name in order to connect to their API. For more info, refer to DeployHQ’s documentation.

To retrieve your API key,

Navigate to your DeployHQ account and sign in
Go to “Settings” > “Security”

Your account name is 1234 if your DeployHQ URL is https://1234.deployhq.com

About DeployHQ#

Deployment made simple. We make it super easy to automate deploying projects from Git, SVN and Mercurial repositories.

Action#

Delete Row(s) on PostgreSQL

Description:Deletes a row or rows from a table. [See the documentation](https://node-postgres.com/features/queries)

Version:2.0.6

Key:postgresql-delete-rows

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: "Delete Row(s)",
  key: "postgresql-delete-rows",
  description: "Deletes a row or rows from a table. [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(s) by searching for a value in this column",
    },
    value: {
      propDefinition: [
        postgresql,
        "value",
        (c) => ({
          table: c.table,
          column: c.column,
          schema: c.schema,
        }),
      ],
    },
  },
  async run({ $ }) {
    const {
      table,
      schema,
      column,
      value,
    } = this;

    try {
      const rows = await this.postgresql.deleteRows(
        schema,
        table,
        column,
        value,
      );
      $.export("$summary", `Deleted ${rows.length} rows from ${table}`);
      return rows;
    } catch (error) {
      let errorMsg = "Row not deleted 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.