Create Manpower Log with Procore API on New Row from Snowflake API

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

Trigger workflow on

New Row from the Snowflake API

Next, do this

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

Select this integration
Configure the New Row trigger
1. Connect your Snowflake account
2. Configure timer
3. Select a Database
4. Select a Schema
5. Select a Table Name
6. Select a Unique Key
7. Optional- Configure Emit individual events
Configure the Create Manpower Log action
1. Connect your Procore account
2. Select a Company ID
3. Select a Project ID
4. Configure Notes
5. Optional- Configure Datetime
6. Optional- Configure Number Of Workers
7. Optional- Configure Number Of Hours
8. Optional- Select a User ID
9. Optional- Select a Location 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 Row on Snowflake

Description:Emit new event when a row is added to a table

Version:0.2.3

Key:snowflake-new-row

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-table-scan.mjs";

export default {
  ...common,
  type: "source",
  key: "snowflake-new-row",
  name: "New Row",
  description: "Emit new event when a row is added to a table",
  version: "0.2.3",
  methods: {
    ...common.methods,
    async getStatement(lastResultId) {
      const sqlText = `
        SELECT *
        FROM IDENTIFIER(:1)
        WHERE ${this.uniqueKey} > :2
        ORDER BY ${this.uniqueKey} ASC
      `;
      const binds = [
        this.tableName,
        lastResultId,
      ];
      return {
        sqlText,
        binds,
      };
    },
  },
};

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
Database	`database`	`string`	Select a value from the drop down menu.
Schema	`schema`	`string`	Select a value from the drop down menu.
Table Name	`tableName`	`string`	Select a value from the drop down menu.
Unique Key	`uniqueKey`	`string`	Select a value from the drop down menu.
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 Manpower Log on Procore

Description:Create a new manpower log. [See the documentation](https://developers.procore.com/reference/rest/manpower-logs?version=latest#create-manpower-log).

Version:0.0.2

Key:procore-create-manpower-log

View on GitHub

Procore Overview#

The Procore API empowers developers to interact with its construction management software programmatically, enabling automation of tasks, data synchronization, and enhanced reporting. With APIs covering project management, quality and safety, construction financials, and field productivity, you can craft workflows that streamline operations, reduce manual entry, and provide real-time insights. On Pipedream, these capabilities can be harnessed to create workflows that react to events in Procore or orchestrate actions between Procore and other apps, optimizing construction project workflows.

Action Code#

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

export default {
  key: "procore-create-manpower-log",
  name: "Create Manpower Log",
  description: "Create a new manpower log. [See the documentation](https://developers.procore.com/reference/rest/manpower-logs?version=latest#create-manpower-log).",
  version: "0.0.2",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: false,
  },
  type: "action",
  props: {
    app,
    companyId: {
      propDefinition: [
        app,
        "companyId",
      ],
    },
    projectId: {
      optional: false,
      propDefinition: [
        app,
        "projectId",
        ({ companyId }) => ({
          companyId,
        }),
      ],
    },
    notes: {
      type: "string",
      label: "Notes",
      description: "The notes for the record",
    },
    datetime: {
      type: "string",
      label: "Datetime",
      description: "The datetime of the record. Eg. `2025-04-01T00:00:00Z`.",
      optional: true,
    },
    numWorkers: {
      type: "integer",
      label: "Number Of Workers",
      description: "The number of workers",
      optional: true,
    },
    numHours: {
      type: "string",
      label: "Number Of Hours",
      description: "The number of hours for each worker",
      optional: true,
    },
    userId: {
      propDefinition: [
        app,
        "userId",
        ({ companyId }) => ({
          companyId,
        }),
      ],
    },
    locationId: {
      propDefinition: [
        app,
        "locationId",
        ({
          companyId, projectId,
        }) => ({
          companyId,
          projectId,
        }),
      ],
    },
  },
  methods: {
    createManpowerLog({
      projectId, ...args
    } = {}) {
      return this.app.post({
        path: `/projects/${projectId}/manpower_logs`,
        ...args,
      });
    },
  },
  async run({ $ }) {
    const {
      createManpowerLog,
      companyId,
      projectId,
      datetime,
      notes,
      numWorkers,
      numHours,
      userId,
      locationId,
    } = this;

    const response = await createManpowerLog({
      $,
      companyId,
      projectId,
      data: {
        manpower_log: {
          datetime,
          notes,
          num_workers: numWorkers,
          num_hours: numHours,
          user_id: userId,
          location_id: locationId,
        },
      },
    });
    $.export("$summary", `Successfully created manpower log 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
Procore	`app`	`app`	This component uses the Procore app.
Company ID	`companyId`	`integer`	Select a value from the drop down menu.
Project ID	`projectId`	`integer`	Select a value from the drop down menu.
Notes	`notes`	`string`	The notes for the record
Datetime	`datetime`	`string`	The datetime of the record. Eg. `2025-04-01T00:00:00Z`.
Number Of Workers	`numWorkers`	`integer`	The number of workers
Number Of Hours	`numHours`	`string`	The number of hours for each worker
User ID	`userId`	`integer`	Select a value from the drop down menu.
Location ID	`locationId`	`integer`	Select a value from the drop down menu.

Action Authentication#

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

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