Schedule Meeting with Google Meet API on New, Updated, or Deleted Warehouse from Snowflake API

Pipedream makes it easy to connect APIs for Google Meet, Snowflake and 2,400+ other apps remarkably fast.

Trigger workflow on

New, Updated, or Deleted Warehouse from the Snowflake API

Next, do this

Schedule Meeting with the Google Meet 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 Snowflake trigger and Google Meet action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New, Updated, or Deleted Warehouse trigger
1. Connect your Snowflake account
2. Configure timer
3. Optional- Select one or more Query Types
4. Optional- Select one or more Warehouse Name
Configure the Schedule Meeting action
1. Connect your Google Meet account
2. Optional- Select a Calendar ID
3. Optional- Configure Event Title
4. Optional- Configure Event Location
5. Optional- Configure Event Description
6. Optional- Configure Attendees
7. Configure Event Start Date
8. Configure Event End Date
9. Optional- Configure Recurrence
10. Optional- Select a Time Zone
11. Optional- Select a Send Updates
12. Optional- Configure Send Notifications
13. Optional- Select a Color ID
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, Updated, or Deleted Warehouse on Snowflake

Description:Emit new events when a warehouse is created, altered, or dropped

Version:0.1.2

Key:snowflake-change-to-warehouse

View on GitHub

Snowflake Overview#

Snowflake offers a cloud database and related tools to help developers create robust, secure, and scalable data warehouses. See Snowflake's Key Concepts & Architecture.

Getting Started

1. Create a user, role and warehouse in Snowflake

Snowflake recommends you create a new user, role, and warehouse when you integrate a third-party tool like Pipedream. This way, you can control permissions via the user / role, and separate Pipedream compute and costs with the warehouse. You can do this directly in the Snowflake UI.

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

2. Enter those details in Pipedream

Visit https://pipedream.com/accounts. Click the button to Connect an App. Enter the required Snowflake account data.

You'll only need to connect your account once in Pipedream. You can connect this account to multiple workflows to run queries against Snowflake, insert data, and more.

3. Build your first workflow

Visit https://pipedream.com/new to build your first workflow. Pipedream workflows let you connect Snowflake with 1,000+ other apps. You can trigger workflows on Snowflake queries, sending results to Slack, Google Sheets, or any app that exposes an API. Or you can accept data from another app, transform it with Python, Node.js, Go or Bash code, and insert it into Snowflake.

Learn more at Pipedream University.

Trigger Code#

import common from "../common-watch-for-resource-changes.mjs";

export default {
  ...common,
  props: {
    ...common.props,
    warehouses: {
      propDefinition: [
        common.props.snowflake,
        "warehouses",
      ],
      optional: true,
    },
  },
  type: "source",
  key: "snowflake-change-to-warehouse",
  // eslint-disable-next-line
  name: "New, Updated, or Deleted Warehouse",
  description: "Emit new events when a warehouse is created, altered, or dropped",
  version: "0.1.2",
  async run() {
    await this.watchObjectsAndEmitChanges("WAREHOUSE", this.warehouses, this.queryTypes);
  },
};

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
Snowflake	`snowflake`	`app`	This component uses the Snowflake app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`	Watch for changes on this schedule. Snowflake query history has roughly a 45 minute delay
Query Types	`queryTypes`	`string[]`	Select a value from the drop down menu:`CREATEALTERDROP`
Warehouse Name	`warehouses`	`string[]`	Select a value from the drop down menu.

Trigger Authentication#

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

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

About Snowflake#

A data warehouse built for the cloud

Action#

Schedule Meeting on Google Meet

Description:Creates a new event in Google Calendar with a Google Meet link. [See the documentation](https://developers.google.com/calendar/api/v3/reference/events/insert)

Version:0.0.1

Key:google_meet-schedule-meeting

View on GitHub

Google Meet Overview#

The Google Meet API allows developers to automate aspects of the video conferencing service, like creating and managing meetings. With Pipedream, these capabilities can be leveraged to build custom workflows, integrating Google Meet with other services to streamline scheduling, notification, and management processes. For instance, you can automate the creation of meetings in response to calendar events, sync meeting details with a CRM, or initiate follow-up actions once a meeting concludes.

Action Code#

import googleMeet from "../../google_meet.app.mjs";
import { v4 as uuidv4 } from "uuid";

export default {
  key: "google_meet-schedule-meeting",
  name: "Schedule Meeting",
  description: "Creates a new event in Google Calendar with a Google Meet link. [See the documentation](https://developers.google.com/calendar/api/v3/reference/events/insert)",
  version: "0.0.1",
  type: "action",
  props: {
    googleMeet,
    calendarId: {
      propDefinition: [
        googleMeet,
        "calendarId",
      ],
    },
    summary: {
      label: "Event Title",
      type: "string",
      description: "Enter a title for the event, (e.g., `My event`)",
      optional: true,
    },
    location: {
      label: "Event Location",
      type: "string",
      description: "Specify the location of the event",
      optional: true,
    },
    description: {
      label: "Event Description",
      type: "string",
      description: "Enter a description for the event",
      optional: true,
    },
    attendees: {
      label: "Attendees",
      type: "string[]",
      description: "Enter an array of email addresses for any attendees",
      optional: true,
    },
    eventStartDate: {
      label: "Event Start Date",
      type: "string",
      description: "For all-day events, enter the Event day in the format `yyyy-mm-dd`. For events with time, format according to [RFC3339](https://www.rfc-editor.org/rfc/rfc3339.html#section-1): `yyyy-mm-ddThh:mm:ss+01:00`. A time zone offset is required unless a time zone is explicitly specified in timeZone.",
    },
    eventEndDate: {
      label: "Event End Date",
      type: "string",
      description: "For all-day events, enter the Event day in the format `yyyy-mm-dd`. For events with time, format according to [RFC3339](https://www.rfc-editor.org/rfc/rfc3339.html#section-1): `yyyy-mm-ddThh:mm:ss+01:00`. A time zone offset is required unless a time zone is explicitly specified in timeZone.",
    },
    recurrence: {
      label: "Recurrence",
      type: "string[]",
      description: "Recurrence rule(s) for the event. For example, `RRULE:FREQ=DAILY;INTERVAL=2` means once every two days, `RRULE:FREQ=YEARLY` means annually.\nYou can combine multiple recurrence rules. [See the documentation](https://developers.google.com/calendar/api/concepts/events-calendars#recurrence_rule)",
      optional: true,
    },
    timeZone: {
      propDefinition: [
        googleMeet,
        "timeZone",
      ],
    },
    sendUpdates: {
      propDefinition: [
        googleMeet,
        "sendUpdates",
      ],
    },
    sendNotifications: {
      propDefinition: [
        googleMeet,
        "sendNotifications",
      ],
    },
    colorId: {
      propDefinition: [
        googleMeet,
        "colorId",
      ],
    },
  },
  methods: {
    async getTimeZone(selectedTimeZone) {
      const { value: timeZone } = selectedTimeZone ?? await this.googleMeet.getSettings({
        setting: "timezone",
      });
      return timeZone;
    },
    formatAttendees(selectedAttendees, currentAttendees) {
      let attendees = [];
      if (selectedAttendees && Array.isArray(selectedAttendees)) {
        attendees = selectedAttendees.map((email) => ({
          email,
        }));
      } else if (currentAttendees && Array.isArray(currentAttendees)) {
        return currentAttendees.map((attendee) => ({
          email: attendee.email,
        }));
      }
      return attendees;
    },
    checkDateOrDateTimeInput(date, type) {
      if (type === "date") {
        return date && date.length <= 10
          ? date
          : undefined;
      }
      if (type === "dateTime") {
        return date && date.length > 10
          ? date
          : undefined;
      }
    },
    getDateParam({
      date,
      timeZone,
    }) {
      return {
        date: this.checkDateOrDateTimeInput(date, "date"),
        dateTime: this.checkDateOrDateTimeInput(date, "dateTime"),
        timeZone,
      };
    },
  },
  async run({ $ }) {
    const timeZone = await this.getTimeZone(this.timeZone);
    const attendees = this.formatAttendees(this.attendees);

    const data = {
      calendarId: this.calendarId,
      sendUpdates: this.sendUpdates,
      sendNotifications: this.sendNotifications,
      resource: {
        summary: this.summary,
        location: this.location,
        description: this.description,
        start: this.getDateParam({
          date: this.eventStartDate,
          timeZone,
        }),
        end: this.getDateParam({
          date: this.eventEndDate,
          timeZone,
        }),
        recurrence: this.recurrence,
        attendees,
        colorId: this.colorId,
        conferenceData: {
          createRequest: {
            requestId: uuidv4(),
            conferenceSolutionKey: {
              type: "hangoutsMeet",
            },
          },
        },
      },
      conferenceDataVersion: 1,
    };

    const response = await this.googleMeet.createEvent(data);

    $.export("$summary", `Successfully created event: "${response.id}"`);

    return response;
  },
};

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
Google Meet	`googleMeet`	`app`	This component uses the Google Meet app.
Calendar ID	`calendarId`	`string`	Select a value from the drop down menu.
Event Title	`summary`	`string`	Enter a title for the event, (e.g., `My event`)
Event Location	`location`	`string`	Specify the location of the event
Event Description	`description`	`string`	Enter a description for the event
Attendees	`attendees`	`string[]`	Enter an array of email addresses for any attendees
Event Start Date	`eventStartDate`	`string`	For all-day events, enter the Event day in the format `yyyy-mm-dd`. For events with time, format according to RFC3339: `yyyy-mm-ddThh:mm:ss+01:00`. A time zone offset is required unless a time zone is explicitly specified in timeZone.
Event End Date	`eventEndDate`	`string`	For all-day events, enter the Event day in the format `yyyy-mm-dd`. For events with time, format according to RFC3339: `yyyy-mm-ddThh:mm:ss+01:00`. A time zone offset is required unless a time zone is explicitly specified in timeZone.
Recurrence	`recurrence`	`string[]`	Recurrence rule(s) for the event. For example, `RRULE:FREQ=DAILY;INTERVAL=2` means once every two days, `RRULE:FREQ=YEARLY` means annually. You can combine multiple recurrence rules. See the documentation
Time Zone	`timeZone`	`string`	Select a value from the drop down menu.
Send Updates	`sendUpdates`	`string`	Select a value from the drop down menu:`allexternalOnlynone`
Send Notifications	`sendNotifications`	`boolean`	Whether to send notifications about the event update
Color ID	`colorId`	`string`	Select a value from the drop down menu.

Action Authentication#

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

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

emailprofilehttps://www.googleapis.com/auth/calendar.eventshttps://www.googleapis.com/auth/calendar.readonlyhttps://www.googleapis.com/auth/calendar.settings.readonly