Place Order with Alpaca API on New Message in Channel from Discord Bot API

Pipedream makes it easy to connect APIs for Alpaca, Discord Bot and 2,000+ other apps remarkably fast.

Trigger workflow on

New Message in Channel from the Discord Bot 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 800,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Discord Bot 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 New Message in Channel trigger
1. Connect your Discord Bot account
2. Select a Guild
3. Select one or more Channels
4. Optional- Configure Emit messages as a single event
5. Configure timer
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#

New Message in Channel on Discord Bot

Description:Emit new event for each message posted to one or more channels

Version:0.0.18

Key:discord_bot-new-message-in-channel

View on GitHub

Discord Bot Overview#

The Discord Bot API unlocks the power to interact with Discord users and channels programmatically, making it possible to automate messages, manage servers, and integrate with other services. With Pipedream's serverless platform, you can create complex workflows that respond to events in Discord, process data, and trigger actions in other apps. This opens up opportunities for community engagement, content moderation, analytics, and more, without the overhead of managing infrastructure.

Trigger Code#

import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
import maxBy from "lodash.maxby";
import common from "../common.mjs";
import sampleEmit from "./test-event.mjs";

const { discord } = common.props;

export default {
  ...common,
  key: "discord_bot-new-message-in-channel",
  name: "New Message in Channel",
  description: "Emit new event for each message posted to one or more channels",
  type: "source",
  version: "0.0.18",

  dedupe: "unique", // Dedupe events based on the Discord message ID
  props: {
    ...common.props,
    db: "$.service.db",
    channels: {
      type: "string[]",
      label: "Channels",
      description: "The channels you'd like to watch for new messages",
      propDefinition: [
        discord,
        "channelId",
        ({ guildId }) => ({
          guildId,
        }),
      ],
    },
    emitEventsInBatch: {
      type: "boolean",
      label: "Emit messages as a single event",
      description:
        "If `true`, all messages are emitted as an array, within a single Pipedream event. Defaults to `false`, emitting each Discord message as its own event in Pipedream",
      optional: true,
      default: false,
    },
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
  },
  async run({ $ }) {
    // We store a cursor to the last message ID
    let lastMessageIDs = this._getLastMessageIDs();

    // If this is our first time running this source,
    // get the last N messages, emit them, and checkpoint
    for (const channelId of this.channels) {
      let lastMessageID;
      let messages = [];

      if (!lastMessageID) {
        messages = await this.discord.getMessages({
          $,
          channelId,
          params: {
            limit: 100,
          },
        });

        lastMessageID = messages.length
          ? maxBy(messages, (message) => message.id).id
          : 1;

      } else {
        let newMessages = [];

        do {
          newMessages = await this.discord.getMessages({
            $,
            channelId,
            params: {
              after: lastMessageIDs[channelId],
            },
          });

          messages = messages.concat(newMessages);

          lastMessageID = newMessages.length
            ? maxBy(newMessages, (message) => message.id).id
            : lastMessageIDs[channelId];

        } while (newMessages.length);
      }

      // Set the new high water mark for the last message ID
      // for this channel
      lastMessageIDs[channelId] = lastMessageID;

      if (!messages.length) {
        console.log(`No new messages in channel ${channelId}`);
        return;
      }

      console.log(`${messages.length} new messages in channel ${channelId}`);

      // Batched emits do not take advantage of the built-in deduper
      if (this.emitEventsInBatch) {
        const suffixChar =
          messages.length > 1
            ? "s"
            : "";

        this.$emit(messages, {
          summary: `${messages.length} new message${suffixChar}`,
          id: lastMessageID,
        });

      } else {
        messages.forEach((message) => {
          this.$emit(message, {
            summary: message.content,
            id: message.id, // dedupes events based on this ID
          });
        });
      }
    }

    // Set the last message ID for the next run
    this._setLastMessageIDs(lastMessageIDs);
  },
  sampleEmit,
};

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
Discord Bot	`discord`	`app`	This component uses the Discord Bot app.
Guild	`guildId`	`string`	Select a value from the drop down menu.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Channels	`channels`	`string[]`	Select a value from the drop down menu.
Emit messages as a single event	`emitEventsInBatch`	`boolean`	If `true`, all messages are emitted as an array, within a single Pipedream event. Defaults to `false`, emitting each Discord message as its own event in Pipedream
	`timer`	`$.interface.timer`

Trigger Authentication#

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

This app allows you to use the Discord API using your own Discord bot. If you don't want to use a custom bot, and you just need to use the Discord API, exit this screen and use the Discord app, instead.

If you want to use your own Discord bot, but haven't created one yet, see these instructions or watch this video. You'll need to add this bot to your server(s) to make successful API requests.

Once you've created your bot, you'll find the Bot token within the Bot section of your app. Enter that token below.

About Discord Bot#

Use this app to interact with the Discord API using a bot in your account

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 + Discord Bot#

Other Popular Integrations#

Cancel All Orders with Alpaca API on New Message in Channel from Discord Bot API

Discord Bot + Alpaca

Try it

Cancel Order with Alpaca API on New Message in Channel from Discord Bot API

Discord Bot + Alpaca

Try it

Cancel Order with Alpaca API on New Guild Member from Discord Bot API

Discord Bot + Alpaca

Try it

Cancel All Orders with Alpaca API on New Guild Member from Discord Bot API

Discord Bot + Alpaca

Try it

Close All Positions with Alpaca API on New Message in Channel from Discord Bot API

Discord Bot + Alpaca

Try it

Popular Triggers#

New Message in Channel from the Discord Bot API

Emit new event for each message posted to one or more channels

Try it

New Forum Thread Message from the Discord Bot API

Emit new event for each forum thread message posted. Note that your bot must have the MESSAGE_CONTENT privilege intent to see the message content, see the docs here.

Try it

New Guild Member from the Discord Bot API

Emit new event for every member added to a guild. See docs here

Try it

New Thread Message from the Discord Bot API

Emit new event for each thread message posted.

Try it