Query SQL Database with Database API on New Event Scheduled from Calendly API

Pipedream makes it easy to connect APIs for Database, Calendly and 2,700+ other apps remarkably fast.

Trigger workflow on

New Event Scheduled from the Calendly API

Next, do this

Query SQL Database with the Database 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 Calendly trigger and Database action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Event Scheduled trigger
1. Connect your Calendly account
2. Configure timer
Configure the Query SQL Database action
1. Connect your Database account
2. Select a Database Type
3. Connect your Database account
4. Connect your Database account
5. Connect your Database account
6. Connect your Database account
7. Connect your Database account
8. Connect your Database account
9. Configure sql
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 Event Scheduled on Calendly

Description:Emit new event when a event is scheduled.

Version:0.0.7

Key:calendly_v2-new-event-scheduled

View on GitHub

Calendly Overview#

The Calendly API lets you craft bespoke scheduling experiences within your apps or automate repetitive tasks involving your calendar. With this API, you can read event types, set up webhooks for new events, list invitees, or create and cancel invitation links programmatically. Pipedream's serverless platform takes the heavy lifting out of integrating Calendly with hundreds of other apps, enabling you to focus on creating workflows that save time, enhance productivity, and eliminate scheduling errors.

Trigger Code#

import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
import app from "../../calendly_v2.app.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  key: "calendly_v2-new-event-scheduled",
  name: "New Event Scheduled",
  description: "Emit new event when a event is scheduled.",
  version: "0.0.7",
  type: "source",
  dedupe: "unique",
  props: {
    app,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      static: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
  },
  methods: {
    emitEvent(data) {
      const id = data.uri.split("/").reverse()[0];

      this.$emit(data, {
        id: id,
        summary: `New scheduled event with ID ${id}`,
        ts: Date.parse(data.created_at),
      });
    },
    _setLastResourceId(id) {
      this.db.set("lastResourceId", id);
    },
    _getLastResourceId() {
      return this.db.get("lastResourceId");
    },
  },
  async run() {
    const lastResourceId = this._getLastResourceId();

    let nextPage;

    do {
      const {
        pagination, collection: events,
      } = await this.app.listEvents({
        params: {
          page_token: nextPage,
          count: 100,
          sort: "created_at:desc",
        },
      });

      if (events.length) {
        this._setLastResourceId(events[events.length - 1].uri);

        events.forEach(this.emitEvent);
      }

      if (
        events.length < 100 ||
        events.find(({ uri }) => uri === lastResourceId)
      ) {
        nextPage = null;
        return;
      }

      nextPage = pagination.next_page;
    } while (nextPage);
  },
  sampleEmit,
};

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

Trigger Authentication#

Calendly uses OAuth authentication. When you connect your Calendly account, Pipedream will open a popup window where you can sign into Calendly and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Calendly API.

Pipedream requests the following authorization scopes when you connect your account:

About Calendly#

Schedule meetings without the hassle. Never get double booked. Calendly works with your calendar to automate appointment scheduling.

Action#

Query SQL Database on Database

Description:Execute a SQL Query. See [our docs](https://pipedream.com/docs/databases/working-with-sql) to learn more about working with SQL in Pipedream.

Version:0.0.4

Key:database-query-sql-database

View on GitHub

Database Overview#

The Database API on Pipedream allows users to execute SQL commands directly within workflows, enabling rich and dynamic data manipulation and storage. It supports PostgreSQL, MySQL, and SQLite, making it a versatile option for managing data across various database systems. With this API, users can perform tasks such as data insertion, querying, updates, and deletions, directly within their automations, facilitating real-time data processing and integration across multiple platforms.

Action Code#

/* eslint-disable no-unused-vars */
/* eslint-disable pipedream/props-label */
/* eslint-disable pipedream/props-description */
import postgresql from "../../../postgresql/postgresql.app.mjs";
import mysql from "../../../mysql/mysql.app.mjs";
import snowflake from "../../../snowflake/snowflake.app.mjs";
import azure_sql from "../../../azure_sql/azure_sql.app.mjs";
import microsoft_sql_server from "../../../microsoft_sql_server/microsoft_sql_server.app.mjs";
import turso from "../../../turso/turso.app.mjs";

export default {
  name: "Query SQL Database",
  key: "database-query-sql-database",
  description:
    "Execute a SQL Query. See [our docs](https://pipedream.com/docs/databases/working-with-sql) to learn more about working with SQL in Pipedream.",
  version: "0.0.4",
  type: "action",
  props: {
    database: {
      type: "app",
      app: "database",
    },
    db_type: {
      label: "Database Type",
      type: "string",
      description: "Select the database type you need to query",
      options: [
        {
          label: "PostgreSQL",
          value: "postgresql",
        },
        {
          label: "MySQL",
          value: "mysql",
        },
        {
          label: "Snowflake",
          value: "snowflake",
        },
        {
          label: "Azure SQL Server",
          value: "azure_sql",
        },
        {
          label: "Microsoft SQL Server",
          value: "microsoft_sql_server",
        },
        {
          label: "Turso",
          value: "turso",
        },
      ],
      reloadProps: true,
    },
    postgresql: {
      ...postgresql,
      hidden: true,
    },
    mysql: {
      ...mysql,
      hidden: true,
    },
    snowflake: {
      ...snowflake,
      hidden: true,
    },
    azure_sql: {
      ...azure_sql,
      hidden: true,
    },
    microsoft_sql_server: {
      ...microsoft_sql_server,
      hidden: true,
    },
    turso: {
      ...turso,
      hidden: true,
    },
    sql: {
      type: "sql",
      auth: {
        app: "postgresql",
      },
      hidden: true,
    },
  },
  async additionalProps(prev) {
    const db_type = this.db_type?.value || this.db_type;

    prev.snowflake.hidden = db_type !== "snowflake";
    prev.mysql.hidden = db_type !== "mysql";
    prev.postgresql.hidden = db_type !== "postgresql";
    prev.azure_sql.hidden = db_type !== "azure_sql";
    prev.microsoft_sql_server.hidden = db_type !== "microsoft_sql_server";
    prev.turso.hidden = db_type !== "turso";
    prev.sql.hidden = !db_type;

    prev.snowflake.disabled = db_type !== "snowflake";
    prev.mysql.disabled = db_type !== "mysql";
    prev.postgresql.disabled = db_type !== "postgresql";
    prev.azure_sql.disabled = db_type !== "azure_sql";
    prev.microsoft_sql_server.disabled = db_type !== "microsoft_sql_server";
    prev.turso.disabled = db_type !== "turso";

    prev.sql.disabled = !db_type;
    prev.sql.auth.app = db_type;

    return {
      sql: {
        type: "sql",
        auth: {
          app: db_type,
        },
        label: "SQL Query",
      },
    };
  },
  async run({
    steps, $,
  }) {
    const db_type = this.db_type.value || this.db_type;
    const args = this[db_type].executeQueryAdapter(this.sql);
    const data = await this[db_type].executeQuery(args);
    $.export(
      "$summary",
      `Returned ${data.length} ${data.length === 1
        ? "row"
        : "rows"}`,
    );
    return data;
  },
};

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
Database	`database`	`app`	This component uses the Database app.
Database Type	`db_type`	`string`	Select a value from the drop down menu:`{ "label": "PostgreSQL", "value": "postgresql" }{ "label": "MySQL", "value": "mysql" }{ "label": "Snowflake", "value": "snowflake" }{ "label": "Azure SQL Server", "value": "azure_sql" }{ "label": "Microsoft SQL Server", "value": "microsoft_sql_server" }{ "label": "Turso", "value": "turso" }`