Delete Row(s) with PostgreSQL API on New Submission Received from Basin API

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

Trigger workflow on

New Submission Received from the Basin 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 Basin 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 Submission Received trigger
1. Connect your Basin account
2. Configure timer
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 Submission Received on Basin

Description:Emit new event on each new form submission received.

Version:0.0.1

Key:basin-new-submission-received

View on GitHub

Basin Overview#

The Basin API provides a powerful platform for automating form submissions, gathering feedback, and conducting surveys with ease. By leveraging the Pipedream's serverless execution model, you can trigger workflows in response to new form submissions, process and analyze the data, and take action in countless other apps. Whether you're routing form data to a CRM, generating support tickets, or synthesizing customer insights, Basin on Pipedream simplifies these tasks with its event-driven architecture and seamless integrations.

Trigger Code#

import basin from "../../basin.app.mjs";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  name: "New Submission Received",
  version: "0.0.1",
  key: "basin-new-submission-received",
  description: "Emit new event on each new form submission received.",
  type: "source",
  dedupe: "unique",
  props: {
    basin,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      static: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
  },
  methods: {
    emitEvent(data) {
      this.$emit(data, {
        id: data.id,
        summary: `New submission received with ID ${data.id}`,
        ts: Date.parse(data.created_at),
      });
    },
    _setLastSyncDate(date) {
      this.db.set("lastSyncDate", date);
    },
    _getLastSyncDate() {
      return this.db.get("lastSyncDate");
    },
  },
  hooks: {
    async deploy() {
      const { submissions } = await this.basin.getSubmissions();

      submissions.slice(0, 10).reverse()
        .forEach(this.emitEvent);
    },
  },
  async run() {
    const lastSyncDate = this._getLastSyncDate() ?? (new Date).getTime();
    this._setLastSyncDate((new Date).getTime());

    let page = 1;

    while (true) {
      const { submissions } = await this.basin.getSubmissions({
        params: {
          page,
        },
      });

      submissions
        .filter((submission) => Date.parse(submission.created_at) > lastSyncDate)
        .reverse()
        .forEach(this.emitEvent);

      if (submissions.length < 100) {
        break;
      }

      page++;
    }
  },
};

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
Basin	`basin`	`app`	This component uses the Basin app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`

Trigger Authentication#

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

Go to the Dashboard for your form and then select the 'Integrations' tab. Each form has it's own API key.

About Basin#

Deploy a powerful, easy-to-configure form backend without writing a single line of server side code.

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.