Update Contact with Cloudpresenter API on New Query Results from Snowflake API

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

Trigger workflow on

New Query Results from the Snowflake API

Next, do this

Update Contact with the Cloudpresenter 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 Cloudpresenter action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Query Results trigger
1. Connect your Snowflake account
2. Configure timer
3. Configure SQL Query
4. Optional- Configure Primary key
5. Optional- Configure Emit individual events
Configure the Update Contact action
1. Connect your Cloudpresenter account
2. Select a Contact UUID
3. Optional- Configure First Name
4. Optional- Configure Last Name
5. Optional- Configure Email
6. Optional- Configure Company
7. Optional- Configure Job Title
8. Optional- Configure Street Address
9. Optional- Configure City
10. Optional- Configure State
11. Optional- Configure Country
12. Optional- Configure Phone
13. Optional- Select one or more Tag IDs
14. Optional- Select one or more Custom Field IDs
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 Query Results on Snowflake

Description:Run a SQL query on a schedule, triggering a workflow for each row of results

Version:0.2.2

Key:snowflake-query-results

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.mjs";
import { v4 as uuidv4 } from "uuid";

export default {
  ...common,
  type: "source",
  key: "snowflake-query-results",
  name: "New Query Results",
  // eslint-disable-next-line
  description: "Run a SQL query on a schedule, triggering a workflow for each row of results",
  version: "0.2.2",
  props: {
    ...common.props,
    sqlQuery: {
      type: "string",
      label: "SQL Query",
      description: "Run this query on a schedule, triggering the workflow for each row of results",
    },
    // Ordering props correctly
    timer: common.props.timer,
    dedupeKey: {
      type: "string",
      label: "Primary key",
      description: "The column in your query to use for de-duplication. Duplicate rows won't trigger your workflow",
      optional: true,
    },
    emitIndividualEvents: {
      propDefinition: [
        common.props.snowflake,
        "emitIndividualEvents",
      ],
    },
  },
  methods: {
    ...common.methods,
    generateMeta(data) {
      const {
        row: { [this.dedupeKey]: id = uuidv4() },
        timestamp: ts,
      } = data;
      const summary = `New event (ID: ${id})`;
      return {
        id,
        summary,
        ts,
      };
    },
    generateMetaForCollection(data) {
      const { timestamp: ts } = data;
      const id = uuidv4();
      const summary = `New event (ID: ${id})`;
      return {
        id,
        summary,
        ts,
      };
    },
    getStatement() {
      return {
        sqlText: this.sqlQuery,
      };
    },
  },
};

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
SQL Query	`sqlQuery`	`string`	Run this query on a schedule, triggering the workflow for each row of results
Primary key	`dedupeKey`	`string`	The column in your query to use for de-duplication. Duplicate rows won't trigger your workflow
Emit individual events	`emitIndividualEvents`	`boolean`	Defaults to `true`, triggering workflows on each record in the result set. Set to `false` to emit records in batch (advanced)

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#

Update Contact on Cloudpresenter

Description:Updates an existing contact within the Cloudpresenter application. [See the documentation](https://cloudpresenter.stoplight.io/docs/cloudpresenter-public-apis/tjbk1nm3qvbg2-update-contact)

Version:0.0.1

Key:cloudpresenter-update-contact

View on GitHub

Action Code#

import cloudpresenter from "../../cloudpresenter.app.mjs";
import {
  getCustomFieldProps, getPaginatedResources, parseCustomFields,
} from "../../common/utils.mjs";

export default {
  key: "cloudpresenter-update-contact",
  name: "Update Contact",
  description: "Updates an existing contact within the Cloudpresenter application. [See the documentation](https://cloudpresenter.stoplight.io/docs/cloudpresenter-public-apis/tjbk1nm3qvbg2-update-contact)",
  version: "0.0.1",
  type: "action",
  props: {
    cloudpresenter,
    contactId: {
      propDefinition: [
        cloudpresenter,
        "contactId",
      ],
    },
    firstName: {
      propDefinition: [
        cloudpresenter,
        "firstName",
      ],
      optional: true,
    },
    lastName: {
      propDefinition: [
        cloudpresenter,
        "lastName",
      ],
      optional: true,
    },
    email: {
      propDefinition: [
        cloudpresenter,
        "email",
      ],
      optional: true,
    },
    company: {
      propDefinition: [
        cloudpresenter,
        "company",
      ],
    },
    jobTitle: {
      propDefinition: [
        cloudpresenter,
        "jobTitle",
      ],
    },
    streetAddress: {
      propDefinition: [
        cloudpresenter,
        "streetAddress",
      ],
    },
    city: {
      propDefinition: [
        cloudpresenter,
        "city",
      ],
    },
    state: {
      propDefinition: [
        cloudpresenter,
        "state",
      ],
    },
    country: {
      propDefinition: [
        cloudpresenter,
        "country",
      ],
    },
    phone: {
      propDefinition: [
        cloudpresenter,
        "phone",
      ],
    },
    tagIds: {
      propDefinition: [
        cloudpresenter,
        "tagIds",
      ],
    },
    customFieldIds: {
      propDefinition: [
        cloudpresenter,
        "customFieldIds",
      ],
      reloadProps: true,
    },
  },
  async additionalProps() {
    return getCustomFieldProps(this);
  },
  async run({ $ }) {
    const contacts = await getPaginatedResources({
      resourceFn: this.cloudpresenter.listContacts,
      resourceType: "contacts",
    });
    const contact = contacts.find(({ uuid }) => uuid === this.contactId);
    contact.tags = contact?.tags
      ? contact.tags.map(({ id }) => id)
      : [];
    contact.custom_fields = contact?.custom_fields
      ? contact.custom_fields.filter((field) => field.custom_field).map((field) => ({
        id: field.custom_field.id,
        value: field.value,
      }))
      : [];

    const response = await this.cloudpresenter.updateContact({
      $,
      contactId: this.contactId,
      data: {
        contact: {
          first_name: this.firstName || contact.first_name,
          last_name: this.lastName || contact.last_name,
          email: this.email || contact.email,
          company: this.company || contact.company,
          job_title: this.jobTitle || contact.job_title,
          address: this.streetAddress || contact.address,
          city: this.city || contact.city,
          state: this.state || contact.state,
          country: this.country || contact.country,
          phone_number: this.phone || contact.phone,
          tags: this.tagIds || contact.tags,
          custom_fields: this.customFieldIds
            ? parseCustomFields(this)
            : contact.custom_fields,
        },
      },
    });
    $.export("$summary", `Successfully updated contact with ID: ${this.contactId}`);
    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
Cloudpresenter	`cloudpresenter`	`app`	This component uses the Cloudpresenter app.
Contact UUID	`contactId`	`string`	Select a value from the drop down menu.
First Name	`firstName`	`string`	The first name of the contact
Last Name	`lastName`	`string`	The last name of the contact
Email	`email`	`string`	The email address of the contact
Company	`company`	`string`	The company of the contact
Job Title	`jobTitle`	`string`	The job title of the contact
Street Address	`streetAddress`	`string`	The street address of the contact
City	`city`	`string`	The city of the contact
State	`state`	`string`	The state of the contact
Country	`country`	`string`	The country of the contact
Phone	`phone`	`string`	The phone number of the contact
Tag IDs	`tagIds`	`string[]`	Select a value from the drop down menu.
Custom Field IDs	`customFieldIds`	`integer[]`	Select a value from the drop down menu.

Action Authentication#

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

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