Place Order with Alpaca API on Commitment Change Order Event (Instant) from Procore API

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

Trigger workflow on

Commitment Change Order Event (Instant) from the Procore API

Next, do this

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

Select this integration
Configure the Commitment Change Order Event (Instant) trigger
1. Connect your Procore account
2. Select a Company
3. Optional- Select a Project
Configure the Place Order action
1. Connect your Alpaca account
2. Optional- Configure Paper API
3. Configure Symbol
4. Optional- Configure Qty
5. Optional- Configure Notional
6. Select a Side
7. Select a Type
8. Select a Time in Force
9. Optional- Configure Limit Price
10. Optional- Configure Stop Price
11. Optional- Configure Trail Price
12. Optional- Configure Trail Percent
13. Optional- Configure Extended Hours
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#

Commitment Change Order Event (Instant) on Procore

Description:Emits an event each time a Commitment Change Order is created, updated, or deleted in a project.

Version:0.0.2

Key:procore-commitment-change-order

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.

Trigger Code#

const common = require("../common.js");

module.exports = {
  ...common,
  name: "Commitment Change Order Event (Instant)",
  key: "procore-commitment-change-order",
  description:
    "Emits an event each time a Commitment Change Order is created, updated, or deleted in a project.",
  version: "0.0.2",
  type: "source",
  methods: {
    ...common.methods,
    getResourceName() {
      return "Change Events";
    },
    async getDataToEmit(body) {
      const { resource_id: resourceId } = body;
      const resource = await this.procore.getChangeEvent(
        this.company,
        this.project,
        resourceId,
      );
      return {
        ...body,
        resource,
      };
    },
    getMeta(body) {
      const {
        id,
        event_type: eventType,
        resource_id: resourceId,
        timestamp,
      } = body;
      const ts = new Date(timestamp).getTime();
      return {
        id,
        summary: `${eventType} Change Order ID:${resourceId}`,
        ts,
      };
    },
  },
};

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
Procore	`procore`	`app`	This component uses the Procore app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
N/A	`http`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
Company	`company`	`integer`	Select a value from the drop down menu.
Project	`project`	`integer`	Select a value from the drop down menu.

Trigger 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:

About Procore#

The all-in-one construction management software built to help you finish quality projects — safely, on time, and within budget.

Action#

Place Order on Alpaca

Description:Places a new order for the given account. An order request may be rejected if the account is not authorized for trading, or if the tradable balance is insufficient to fill the order, [See the docs](https://alpaca.markets/docs/api-references/trading-api/orders/#request-a-new-order)

Version:0.1.0

Key:alpaca-place-order

View on GitHub

Alpaca Overview#

Alpaca API allows you to harness the power of automated trading by providing an interface to manage your stock and equity portfolio through simple API calls. It's particularly suited for building trading bots, algorithmic trading strategies, or just automating interactions with your investment portfolio. Whether you're looking to place trades based on specific market conditions, automatically adjust your portfolio in response to certain triggers, or simply streamline your investment activities, Alpaca's trading API offers a robust solution.

Action Code#

import app from "../../alpaca.app.mjs";
import { ConfigurationError } from "@pipedream/platform";

export default {
  type: "action",
  key: "alpaca-place-order",
  version: "0.1.0",
  name: "Place Order",
  description: "Places a new order for the given account. An order request may be rejected if the account is not authorized for trading, or if the tradable balance is insufficient to fill the order, [See the docs](https://alpaca.markets/docs/api-references/trading-api/orders/#request-a-new-order)",
  props: {
    app,
    isPaperAPI: {
      propDefinition: [
        app,
        "isPaperAPI",
      ],
    },
    symbol: {
      type: "string",
      label: "Symbol",
      description: "Symbol, asset ID, or currency pair to identify the asset to trade (ex. `AAPL`, `BTC/USD`).",
    },
    qty: {
      type: "string",
      label: "Qty",
      description: "Number of shares to trade. Can be fractionable for only `market` and `day` order types.",
      optional: true,
    },
    notional: {
      type: "string",
      label: "Notional",
      description: "Dollar amount to trade. Cannot work with `Qty`. Can only work for `market` order types and `day` for time in force.",
      optional: true,
    },
    side: {
      propDefinition: [
        app,
        "side",
      ],
    },
    type: {
      type: "string",
      label: "Type",
      description: "Type",
      options: [
        "market",
        "limit",
        "stop",
        "stop_limit",
        "trailing_stop",
      ],
    },
    timeInForce: {
      type: "string",
      label: "Time in Force",
      description: "Please see [this doc](https://alpaca.markets/docs/trading/orders/#time-in-force) for more info on what values are possible for what kind of orders.",
      options: [
        "day",
        "gtc",
        "opg",
        "cls",
        "ioc",
        "fok",
      ],
    },
    limitPrice: {
      type: "string",
      label: "Limit Price",
      description: "Required if type is `limit` or `stop_limit`",
      optional: true,
    },
    stopPrice: {
      type: "string",
      label: "Stop Price",
      description: "Required if type is `stop` or `stop_limit`",
      optional: true,
    },
    trailPrice: {
      type: "string",
      label: "Trail Price",
      description: "This or `trail_percent` is required if type is `trailing_stop`",
      optional: true,
    },
    trailPercent: {
      type: "string",
      label: "Trail Percent",
      description: "This or `trail_price` is required if type is `trailing_stop`",
      optional: true,
    },
    extendedHours: {
      type: "boolean",
      label: "Extended Hours",
      description: "If true, order will be eligible to execute in premarket/afterhours. Only works with `Type` **Limit** and `Time in Force` **Day**.",
      optional: true,
      default: false,
    },
  },
  async run ({ $ }) {
    if (!this.qty && !this.notional) {
      throw new ConfigurationError("Either `Qty` or `Notional` is required!");
    }
    if (this.qty && this.notional) {
      throw new ConfigurationError("`Qty` and `Notional` cannot be given at the same time!");
    }
    if ((this.type == "limit" || this.type == "stop_limit") && !this.limitPrice) {
      throw new ConfigurationError("`Limit Price` is required when `Type` is `limit` or `stop_limit`!");
    }
    if ((this.type == "stop" || this.type == "stop_limit") && !this.stopPrice) {
      throw new ConfigurationError("`Stop Price` is required when `Type` is `limit` or `stop_limit`!");
    }
    if (this.type == "trailing_stop" && !this.trailPrice && !this.trailPercent) {
      throw new ConfigurationError("`Trail Price` or `Trail Percent` is required when `Type` is `trailing_stop`!");
    }
    const response = await this.app.placeOrder({
      $,
      isPaperAPI: this.isPaperAPI,
      data: {
        symbol: this.symbol,
        qty: this.qty,
        notional: this.notional,
        side: this.side,
        type: this.type,
        time_in_force: this.timeInForce,
        limit_price: this.limitPrice,
        stop_price: this.stopPrice,
        trail_price: this.trailPrice,
        trail_percent: this.trailPercent,
        extended_hours: this.extendedHours,
      },
    });
    $.export("$summary", `Order(ID:${response.id}) has been placed.`);
    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
Alpaca	`app`	`app`	This component uses the Alpaca app.
Paper API	`isPaperAPI`	`boolean`	Set to `true` if Paper API is used. Default is `false`.
Symbol	`symbol`	`string`	Symbol, asset ID, or currency pair to identify the asset to trade (ex. `AAPL`, `BTC/USD`).
Qty	`qty`	`string`	Number of shares to trade. Can be fractionable for only `market` and `day` order types.
Notional	`notional`	`string`	Dollar amount to trade. Cannot work with `Qty`. Can only work for `market` order types and `day` for time in force.
Side	`side`	`string`	Select a value from the drop down menu:`buysell`
Type	`type`	`string`	Select a value from the drop down menu:`marketlimitstopstop_limittrailing_stop`
Time in Force	`timeInForce`	`string`	Select a value from the drop down menu:`daygtcopgclsiocfok`
Limit Price	`limitPrice`	`string`	Required if type is `limit` or `stop_limit`
Stop Price	`stopPrice`	`string`	Required if type is `stop` or `stop_limit`
Trail Price	`trailPrice`	`string`	This or `trail_percent` is required if type is `trailing_stop`
Trail Percent	`trailPercent`	`string`	This or `trail_price` is required if type is `trailing_stop`
Extended Hours	`extendedHours`	`boolean`	If true, order will be eligible to execute in premarket/afterhours. Only works with `Type` Limit and `Time in Force` Day.

Action Authentication#

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

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

account:writetradingdata

About Alpaca#

Commission-Free API First Stock Brokerage

More Ways to Connect Alpaca + Procore#

Other Popular Integrations#

Cancel All Orders with Alpaca API on Budget Snapshot Event (Instant) from Procore API

Procore + Alpaca

Place Order with Alpaca API on Commitment Change Order Event (Instant) from Procore API

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

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

Developers ♥ Pipedream

1-24of2,400+apps by most popular

1
-
24
of
2,400+
apps by most popular