Create Meeting with Recruit CRM API on New Query Results from Snowflake API

Pipedream makes it easy to connect APIs for Recruit CRM, Snowflake and 2,000+ other apps remarkably fast.

Trigger workflow on

New Query Results from the Snowflake API

Next, do this

Create Meeting with the Recruit CRM API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 800,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Snowflake trigger and Recruit CRM 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 Create Meeting action
1. Connect your Recruit CRM account
2. Configure Title
3. Optional- Configure Description
4. Optional- Configure Address
5. Select a Reminder
6. Configure Start Date
7. Configure End Date
8. Optional- Select a Related To Type
9. Optional- Select a Related To
10. Optional- Select one or more Attendee Contacts
11. Optional- Select one or more Attendee Candidates
12. Optional- Select one or more Associated Candidates
13. Optional- Select one or more Associated Companies
14. Optional- Select one or more Associated Contacts
15. Optional- Select one or more Associated Jobs
16. Optional- Select one or more Associated Deals
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.1.13

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.1.13",
  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#

Create Meeting on Recruit CRM

Description:Creates a new meeting. [See the documentation](https://docs.recruitcrm.io/docs/rcrm-api-reference/ca9713d31352a-creates-a-new-meeting)

Version:0.0.1

Key:recruit_crm-create-meeting

View on GitHub

Recruit CRM Overview#

The Recruit CRM API provides a suite of functions to automate and streamline recruitment processes. It allows you to integrate your recruitment workflow with other services, create custom applications, or even build bots. With Pipedream, you can connect the Recruit CRM API to a vast array of other apps and services to automate actions like updating candidate records, syncing with HR systems, or triggering notifications based on recruitment activities.

Action Code#

import app from "../../recruit_crm.app.mjs";

export default {
  key: "recruit_crm-create-meeting",
  name: "Create Meeting",
  description: "Creates a new meeting. [See the documentation](https://docs.recruitcrm.io/docs/rcrm-api-reference/ca9713d31352a-creates-a-new-meeting)",
  type: "action",
  version: "0.0.1",
  props: {
    app,
    title: {
      propDefinition: [
        app,
        "title",
      ],
    },
    description: {
      propDefinition: [
        app,
        "description",
      ],
    },
    address: {
      type: "string",
      label: "Address",
      description: "The address of the meeting. Example: `Video call (https://examplelink)`",
      optional: true,
    },
    reminder: {
      propDefinition: [
        app,
        "reminder",
      ],
    },
    startDate: {
      propDefinition: [
        app,
        "startDate",
      ],
    },
    endDate: {
      type: "string",
      label: "End Date",
      description: "The end date and time of the meeting. Example: `2020-06-29T06:36:22.000000Z`",
    },
    relatedToType: {
      propDefinition: [
        app,
        "relatedToType",
      ],
    },
    relatedTo: {
      label: "Related To",
      description: "Associated entity's slug. Example: `23123`",
      propDefinition: [
        app,
        "relatedTo",
        ({ relatedToType }) => ({
          relatedToType,
        }),
      ],
    },
    attendeeContacts: {
      type: "string[]",
      label: "Attendee Contacts",
      description: "Comma separated contact IDs. Example: `21345,33123`",
      propDefinition: [
        app,
        "contactId",
        () => ({
          mapper: ({
            slug: value, first_name: label,
          }) => ({
            label,
            value,
          }),
        }),
      ],
    },
    attendeeCandidates: {
      type: "string[]",
      label: "Attendee Candidates",
      description: "Comma separated candidate IDs. Example: `2543,65478`",
      propDefinition: [
        app,
        "candidateId",
        () => ({
          mapper: ({
            slug: value, first_name: label,
          }) => ({
            label,
            value,
          }),
        }),
      ],
    },
    associatedCandidates: {
      type: "string[]",
      label: "Associated Candidates",
      description: "Comma separated candidate IDs. Example: `275,16318617835190000051Ond`",
      propDefinition: [
        app,
        "candidateId",
        () => ({
          mapper: ({
            slug: value, first_name: label,
          }) => ({
            label,
            value,
          }),
        }),
      ],
    },
    associatedCompanies: {
      type: "string[]",
      label: "Associated Companies",
      description: "Comma separated company IDs. Example: `275,16318617835190000051Ond`",
      propDefinition: [
        app,
        "companyId",
        () => ({
          mapper: ({
            slug: value, company_name: label,
          }) => ({
            label,
            value,
          }),
        }),
      ],
    },
    associatedContacts: {
      type: "string[]",
      label: "Associated Contacts",
      description: "Comma separated contact IDs. Example: `275,16318617835190000051Ond`",
      propDefinition: [
        app,
        "contactId",
        () => ({
          mapper: ({
            slug: value, first_name: label,
          }) => ({
            label,
            value,
          }),
        }),
      ],
    },
    associatedJobs: {
      type: "string[]",
      label: "Associated Jobs",
      description: "Comma separated job IDs. Example: `275,16318617835190000051Ond`",
      propDefinition: [
        app,
        "jobId",
        () => ({
          mapper: ({
            slug: value, name: label,
          }) => ({
            label,
            value,
          }),
        }),
      ],
    },
    associatedDeals: {
      type: "string[]",
      label: "Associated Deals",
      description: "Comma separated deal IDs. Example: `275,16318617835190000051Ond`",
      propDefinition: [
        app,
        "dealId",
        () => ({
          mapper: ({
            slug: value, name: label,
          }) => ({
            label,
            value,
          }),
        }),
      ],
    },
  },
  methods: {
    createMeeting(args  = {}) {
      return this.app.post({
        path: "/meetings",
        ...args,
      });
    },
  },
  async run({ $: step }) {
    const {
      // eslint-disable-next-line no-unused-vars
      app,
      createMeeting,
      ...data
    } = this;

    const response = await createMeeting({
      step,
      data,
    });

    step.export("$summary", `Successfully created meeting with ID \`${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
Recruit CRM	`app`	`app`	This component uses the Recruit CRM app.
Title	`title`	`string`	The title of the meeting
Description	`description`	`string`	The description of the meeting
Address	`address`	`string`	The address of the meeting. Example: `Video call (https://examplelink)`
Reminder	`reminder`	`string`	Select a value from the drop down menu:`{ "label": "No Reminder", "value": "-1" }{ "label": "0 Minutes Before", "value": "0" }{ "label": "15 Minutes Before", "value": "15" }{ "label": "30 Minutes Before", "value": "30" }{ "label": "1 Hour Before", "value": "60" }{ "label": "2 Hours Before", "value": "120" }{ "label": "1 Day Before", "value": "1440" }`
Start Date	`startDate`	`string`	The start date and time of the meeting. Example: `2020-06-29T05:36:22.000000Z`
End Date	`endDate`	`string`	The end date and time of the meeting. Example: `2020-06-29T06:36:22.000000Z`
Related To Type	`relatedToType`	`string`	Select a value from the drop down menu:`candidatecontactcompanyjobdeal`
Related To	`relatedTo`	`string`	Select a value from the drop down menu.
Attendee Contacts	`attendeeContacts`	`string[]`	Select a value from the drop down menu.
Attendee Candidates	`attendeeCandidates`	`string[]`	Select a value from the drop down menu.
Associated Candidates	`associatedCandidates`	`string[]`	Select a value from the drop down menu.
Associated Companies	`associatedCompanies`	`string[]`	Select a value from the drop down menu.
Associated Contacts	`associatedContacts`	`string[]`	Select a value from the drop down menu.
Associated Jobs	`associatedJobs`	`string[]`	Select a value from the drop down menu.
Associated Deals	`associatedDeals`	`string[]`	Select a value from the drop down menu.

Action Authentication#

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

To retrieve your API Token,

Navigate to your Recruit CRM account and sign in
Go to “Admin Settings” > “API & Integrations”