Update Row with PostgreSQL API on New Booking with State from Timekit API

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

Trigger workflow on

New Booking with State from the Timekit API

Next, do this

Update 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 Timekit 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 Booking with State trigger
1. Connect your Timekit account
2. Select a Graph Type
3. Select a Booking State
4. Optional- Configure Secret
Configure the Update 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
6. 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 Booking with State on Timekit

Description:Emit new event when a booking has a specific state. [See the docs](https://developers.timekit.io/reference/graphs).

Version:0.0.1

Key:timekit-booking-with-state

View on GitHub

Timekit Overview#

Timekit is a flexible booking and resource management API that enables developers to create and manage appointments and calendars. With Timekit, you can automate the scheduling process, sync calendars, manage bookings, and craft customized booking experiences. Using Pipedream, you can leverage Timekit to create efficient workflows that automate scheduling-related tasks, trigger actions based on calendar events, and integrate with various other services for a seamless operational ecosystem.

Trigger Code#

import timekit from "../../timekit.app.mjs";
import crypto from "crypto";

const docLink = "https://developers.timekit.io/reference/graphs";

export default {
  key: "timekit-booking-with-state",
  name: "New Booking with State",
  description: `Emit new event when a booking has a specific state. [See the docs](${docLink}).`,
  version: "0.0.1",
  type: "source",
  props: {
    timekit,
    db: "$.service.db",
    http: "$.interface.http",
    graph: {
      propDefinition: [
        timekit,
        "graph",
      ],
    },
    state: {
      propDefinition: [
        timekit,
        "state",
        (c) => ({
          graph: c.graph,
        }),
      ],
    },
    secret: {
      type: "string",
      label: "Secret",
      description: "Configured secret to verify webhook events. If left blank, no verification will be done. Navigate to API Settings > Keys and look for the last card on the page. The secret shown there is the key you'll use",
      secret: true,
      optional: true,
    },
  },
  hooks: {
    async activate() {
      console.log("Creating webhook...");
      const response = await this.timekit.createWebhook({
        data: {
          url: this.http.endpoint,
          graph: this.graph,
          state: this.state,
          method: "post",
        },
      });
      const id = response.meta.message.split("id ")[1];
      this._setWebhookId(id);
    },
    async deactivate() {
      const id = this._getWebhookId();
      await this.timekit.deleteWebhook({
        id,
      });
      console.log(`Webhook ${id} was deleted successfully`);
    },
  },
  methods: {
    _getWebhookId() {
      return this.db.get("webhookId");
    },
    _setWebhookId(id) {
      this.db.set("webhookId", id);
    },
    verifySecret(payload, header) {
      if (this.secret) {
        const hash = crypto
          .createHmac("sha256", this.secret)
          .update(payload)
          .digest("hex");
        return hash === header;
      }
      return true;
    },
  },
  async run(event) {
    if (!this.verifySecret(event.bodyRaw, event.headers["x-timekit-signature"])) {
      console.log("Secret verification has failed for the incoming event. Skipping...");
      return;
    }

    const {
      id,
      description,
      updated_at: ts,
    } = event.body;

    this.$emit(event.body, {
      id,
      summary: `New ${this.graph} booking ${this.state}: ${description}`,
      ts,
    });
  },
};

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
Timekit	`timekit`	`app`	This component uses the Timekit 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.
Graph Type	`graph`	`string`	Select a value from the drop down menu:`instantinstant_paymentconfirm_declinegroup_ownergroup_customergroup_customer_paymentreservation`
Booking State	`state`	`string`	Select a value from the drop down menu.
Secret	`secret`	`string`	Configured secret to verify webhook events. If left blank, no verification will be done. Navigate to API Settings > Keys and look for the last card on the page. The secret shown there is the key you'll use

Trigger Authentication#

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

You can find your app's API key in the Admin Dashboard under "API settings".

About Timekit#

Timekit lets you build scalable and flexible booking experiences and scheduling flows that grow your business.

Action#

Update Row on PostgreSQL

Description:Updates an existing row. [See the documentation](https://node-postgres.com/features/queries)

Version:2.0.6

Key:postgresql-update-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: "Update Row",
  key: "postgresql-update-row",
  description: "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,
        }),
      ],
    },
    column: {
      propDefinition: [
        postgresql,
        "column",
        (c) => ({
          table: c.table,
          schema: c.schema,
        }),
      ],
      label: "Lookup Column",
      description: "Find row to update 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,
        }),
      ],
    },
    rowValues: {
      propDefinition: [
        postgresql,
        "rowValues",
      ],
    },
  },
  async run({ $ }) {
    const {
      schema,
      table,
      column,
      value,
      rowValues,
    } = this;
    try {
      const res = await this.postgresql.updateRow(
        schema,
        table,
        column,
        value,
        rowValues,
      );
      const summary = res
        ? "Row updated"
        : "Row not found";
      $.export("$summary", summary);
      return res;
    } catch (error) {
      let errorMsg = "Row not updated 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.
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.