Upsert Row with PostgreSQL API on New Form Submission from Formcarry API

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

Trigger workflow on

New Form Submission from the Formcarry API

Next, do this

Upsert 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 Formcarry 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 Form Submission trigger
1. Connect your Formcarry account
2. Configure timer
3. Configure Form ID
Configure the Upsert Row action
1. Connect your PostgreSQL account
2. Select a Schema
3. Select a Table
4. Select a Conflict Target
5. Configure Row Values
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 Form Submission on Formcarry

Description:Emit new event when the specified form receives a new submission. [See the documentation](https://formcarry.com/docs/formcarry-api/submissions-api#cc7f3010897b4c938c8829db46b18656)

Version:0.0.1

Key:formcarry-new-form-submission

View on GitHub

Formcarry Overview#

Formcarry is an API for form processing, empowering developers to handle form submissions without the need for server-side code. With Formcarry, you can effortlessly collect, process, and integrate form data with various services. Using Pipedream, you can create serverless workflows that react to form submissions by triggering actions within Formcarry or in other apps, streamlining data collection and automation processes.

Trigger Code#

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

export default {
  key: "formcarry-new-form-submission",
  name: "New Form Submission",
  description: "Emit new event when the specified form receives a new submission. [See the documentation](https://formcarry.com/docs/formcarry-api/submissions-api#cc7f3010897b4c938c8829db46b18656)",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  props: {
    formcarry,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    formId: {
      type: "string",
      label: "Form ID",
      description: "The ID of the form to watch for new submissions",
    },
  },
  hooks: {
    async deploy() {
      await this.processEvent(25);
    },
  },
  methods: {
    _getLastTs() {
      return this.db.get("lastTs") || 0;
    },
    _setLastTs(lastTs) {
      this.db.set("lastTs", lastTs);
    },
    generateMeta(submission) {
      return {
        id: submission._id,
        summary: `New Form Submission ID: ${submission._id}`,
        ts: Date.parse(submission.createdAt),
      };
    },
    async processEvent(max) {
      const lastTs = this._getLastTs();

      const results = this.formcarry.paginate({
        fn: this.formcarry.listSubmissions,
        args: {
          formId: this.formId,
        },
        resourceKey: "submissions",
        max,
      });

      const submissions = [];
      for await (const item of results) {
        const ts = Date.parse(item.createdAt);
        if (ts >= lastTs) {
          submissions.push(item);
        } else {
          break;
        }
      }

      if (!submissions.length) {
        return;
      }

      this._setLastTs(Date.parse(submissions[0].createdAt));

      submissions.forEach((submission) => {
        const meta = this.generateMeta(submission);
        this.$emit(submission, meta);
      });
    },
  },
  async run() {
    await this.processEvent();
  },
};

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
Formcarry	`formcarry`	`app`	This component uses the Formcarry app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
Form ID	`formId`	`string`	The ID of the form to watch for new submissions

Trigger Authentication#

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

About Formcarry#

Formcarry allows you to collect submissions from your own HTML form, without any back-end code.

Action#

Upsert Row on PostgreSQL

Description:Adds a new row or updates an existing row. [See the documentation](https://node-postgres.com/features/queries)

Version:2.0.6

Key:postgresql-upsert-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";
import format from "pg-format";

export default {
  name: "Upsert Row",
  key: "postgresql-upsert-row",
  description: "Adds a new row or updates an existing row. [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,
        }),
      ],
    },
    conflictTarget: {
      propDefinition: [
        postgresql,
        "column",
        (c) => ({
          table: c.table,
          schema: c.schema,
        }),
      ],
      label: "Conflict Target",
      description: "If insert fails, update the row with the same value in this column.",
    },
    rowValues: {
      propDefinition: [
        postgresql,
        "rowValues",
      ],
    },
  },
  methods: {
    /**
     * Upserts a row in a table.
     * @param {object} args - The parameters to the query.
     * @param {string} args.schema - The name of the schema.
     * @param {string} args.table - The name of the table.
     * @param {Array<string>} args.columns - The columns in which to insert values.
     * @param {Array<any>} args.values - The values to insert.
     * @param {string} args.conflictTarget - The column to use as the conflict target.
     * @returns {Promise<object>} A promise that resolves with the result of the query.
     * @throws {Error} Will throw an error if the query fails.
     */
    upsertRow({
      schema, table, columns, values, conflictTarget = "id",
    } = {}) {
      const placeholders = this.postgresql.getPlaceholders({
        values,
      });

      const updates = columns
        .filter((column) => column !== conflictTarget)
        .map((column) => `${column}=EXCLUDED.${column}`);

      const query = `
        INSERT INTO ${schema}.${table} (${columns})
          VALUES (${placeholders})
          ON CONFLICT (${conflictTarget})
          DO UPDATE SET ${updates}
          RETURNING *
      `;

      return this.postgresql.executeQuery({
        text: format(query, schema, table),
        values,
      });
    },
  },
  async run({ $ }) {
    const {
      upsertRow,
      rowValues,
      ...args
    } = this;

    const columns = Object.keys(rowValues);
    const values = Object.values(rowValues);

    try {
      const res = await upsertRow({
        columns,
        values,
        ...args,
      });
      const summary = res
        ? "Row upserted"
        : "Row not upserted";
      $.export("$summary", summary);
      return res;
    } catch (error) {
      let errorMsg = "Row not upserted 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.
Conflict Target	`conflictTarget`	`string`	Select a value from the drop down menu.
Row Values	`rowValues`	`object`	Enter the column names and respective values as key/value pairs, or with structured mode off as `{{{columnName:"columnValue"}}}`

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.