List Trades with BitMEX API on New Message In Channels (Instant) from Slack (legacy) API

Pipedream makes it easy to connect APIs for BitMEX, Slack (legacy) and 3,000+ other apps remarkably fast.

Trigger workflow on

New Message In Channels (Instant) from the Slack (legacy) API

Next, do this

List Trades with the BitMEX 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 Slack (legacy) trigger and BitMEX 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 Channels (Instant) trigger
1. Connect your Slack (legacy) account
2. Optional- Select one or more Channels
3. Configure slackApphook
4. Optional- Configure Resolve Names
5. Optional- Configure Ignore Bots
6. Optional- Configure Ignore replies in threads
Configure the List Trades action
1. Connect your BitMEX account
2. Optional- Configure Filter
3. Optional- Select a Symbol
4. Optional- Configure Columns
5. Optional- Configure Count
6. Optional- Configure Start
7. Optional- Configure Reverse
8. Optional- Configure Start Time
9. Optional- Configure End Time
10. Optional- Configure Target Account ID
11. Optional- Configure Target Account 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 Message In Channels (Instant) on Slack (legacy)

Description:Emit new event when a new message is posted to one or more channels

Version:1.0.25

Key:slack-new-message-in-channels

View on GitHub

Slack (legacy) Overview#

The Pipedream app for Slack enables you to build event-driven workflows that interact with the Slack API. Once you authorize the app's access to your workspace, you can use Pipedream workflows to perform common Slack actions or write your own code against the Slack API.

The Pipedream app for Slack is not a typical app. You don't interact with it directly as a bot, and it doesn't add custom functionality to your workspace out of the box. It makes it easier to automate anything you'd typically use the Slack API for, using Pipedream workflows.

Automate posting updates to your team channels
Create a bot to answer common questions
Integrate with your existing tools and services
And much more!

Trigger Code#

import common from "../common/base.mjs";
import constants from "../common/constants.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  ...common,
  key: "slack-new-message-in-channels",
  name: "New Message In Channels (Instant)",
  version: "1.0.25",
  description: "Emit new event when a new message is posted to one or more channels",
  type: "source",
  dedupe: "unique",
  props: {
    ...common.props,
    conversations: {
      propDefinition: [
        common.props.slack,
        "conversation",
      ],
      type: "string[]",
      label: "Channels",
      description: "Select one or more channels to monitor for new messages.",
      optional: true,
    },
    // eslint-disable-next-line pipedream/props-description,pipedream/props-label
    slackApphook: {
      type: "$.interface.apphook",
      appProp: "slack",
      async eventNames() {
        return this.conversations || [
          "message",
        ];
      },
    },
    resolveNames: {
      propDefinition: [
        common.props.slack,
        "resolveNames",
      ],
    },
    ignoreBot: {
      propDefinition: [
        common.props.slack,
        "ignoreBot",
      ],
    },
    ignoreThreads: {
      type: "boolean",
      label: "Ignore replies in threads",
      description: "Ignore replies to messages in threads",
      optional: true,
    },
  },
  methods: {
    ...common.methods,
    getSummary() {
      return "New message in channel";
    },
    async processEvent(event) {
      if (event.type !== "message") {
        console.log(`Ignoring event with unexpected type "${event.type}"`);
        return;
      }
      if (event.subtype && !constants.ALLOWED_MESSAGE_IN_CHANNEL_SUBTYPES.includes(event.subtype)) {
        // This source is designed to just emit an event for each new message received.
        // Due to inconsistencies with the shape of message_changed and message_deleted
        // events, we are ignoring them for now. If you want to handle these types of
        // events, feel free to change this code!!
        console.log("Ignoring message with subtype.");
        return;
      }
      if ((this.ignoreBot) && (event.subtype == "bot_message" || event.bot_id)) {
        return;
      }
      // There is no thread message type only the thread_ts field
      // indicates if the message is part of a thread in the event.
      if (this.ignoreThreads && event.thread_ts) {
        console.log("Ignoring reply in thread");
        return;
      }
      if (this.resolveNames) {
        if (event.user) {
          event.user_id = event.user;
          event.user = await this.getUserName(event.user);
        } else if (event.bot_id) {
          event.bot = await this.getBotName(event.bot_id);
        }
        event.channel_id = event.channel;
        event.channel = await this.getConversationName(event.channel);
        if (event.team) {
          event.team_id = event.team;
          event.team = await this.getTeamName(event.team);
        }
      }
      return event;
    },
  },
  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
Slack (legacy)	`slack`	`app`	This component uses the Slack (legacy) app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Channels	`conversations`	`string[]`	Select a value from the drop down menu.
	`slackApphook`	`$.interface.apphook`
Resolve Names	`resolveNames`	`boolean`	Instead of returning `channel`, `team`, and `user` as IDs, return their human-readable names.
Ignore Bots	`ignoreBot`	`boolean`	Ignore messages from bots
Ignore replies in threads	`ignoreThreads`	`boolean`	Ignore replies to messages in threads

Trigger Authentication#

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

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

channels:historychannels:readchannels:writeemoji:readgroups:historygroups:readgroups:writeim:historyim:readim:writelinks:readlinks:writempim:historympim:readmpim:writereactions:readreactions:writereminders:readreminders:writestars:readteam:readusergroups:readusergroups:writeusers:readusers:read.emailusers:writechat:write:botchat:write:userfiles:write:userfiles:readcommandsusers.profile:writeusers.profile:readsearch:read

About Slack (legacy)#

Slack is a channel-based messaging platform. With Slack, people can work together more effectively, connect all their software tools and services, and find the information they need to do their best work — all within a secure, enterprise-grade environment.

Action#

List Trades on BitMEX

Description:Retrieve a list of executed trades from your BitMEX account. [See the documentation](https://www.bitmex.com/api/explorer/#!/Execution/Execution_getTradeHistory)

Version:0.0.1

Key:bitmex-list-trades

View on GitHub

Action Code#

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

export default {
  key: "bitmex-list-trades",
  name: "List Trades",
  description: "Retrieve a list of executed trades from your BitMEX account. [See the documentation](https://www.bitmex.com/api/explorer/#!/Execution/Execution_getTradeHistory)",
  version: "0.0.1",
  annotations: {
    destructiveHint: false,
    openWorldHint: false,
    readOnlyHint: true,
  },
  type: "action",
  props: {
    bitmex,
    filter: {
      type: "object",
      label: "Filter",
      description: "Generic table filter. Send JSON key/value pairs, such as `{\"execType\": [\"Settlement\", \"Trade\"]}` to filter on multiple values. For explanations on filters refer to http://www.onixs.biz/fix-dictionary/5.0.SP2/msgType_8_8.html",
      optional: true,
    },
    symbol: {
      propDefinition: [
        bitmex,
        "symbol",
      ],
      optional: true,
    },
    columns: {
      type: "string[]",
      label: "Columns",
      description: "Array of column names to fetch. If omitted, will return all columns. Note that this method will always return item keys, even when not specified, so you may receive more columns that you expect.",
      optional: true,
    },
    count: {
      type: "integer",
      label: "Count",
      description: "Number of results to fetch. Must be a positive integer. Defaults to 100",
      optional: true,
      default: 100,
    },
    start: {
      type: "integer",
      label: "Start",
      description: "Starting point for results. Defaults to 0",
      optional: true,
      default: 0,
    },
    reverse: {
      type: "boolean",
      label: "Reverse",
      description: "If `true`, will sort results newest first. Defaults to `false`",
      optional: true,
      default: false,
    },
    startTime: {
      type: "string",
      label: "Start Time",
      description: "Starting date filter for results (format: `YYYY-MM-DDTHH:mm:ss.sssZ`)",
      optional: true,
    },
    endTime: {
      type: "string",
      label: "End Time",
      description: "Ending date filter for results (format: `YYYY-MM-DDTHH:mm:ss.sssZ`)",
      optional: true,
    },
    targetAccountId: {
      type: "integer",
      label: "Target Account ID",
      description: "AccountId fetching the trade history, must be a paired account with main user",
      optional: true,
    },
    targetAccountIds: {
      type: "string",
      label: "Target Account IDs",
      description: "AccountIds fetching the trade history, must be a paired account with main user. Can be wildcard `*` to get all accounts linked to the authenticated user",
      optional: true,
    },
  },
  async run({ $ }) {
    const response = await this.bitmex.getTradeHistory({
      filter: this.filter,
      symbol: this.symbol,
      columns: this.columns,
      count: this.count,
      start: this.start,
      reverse: this.reverse,
      startTime: this.startTime,
      endTime: this.endTime,
      targetAccountId: this.targetAccountId,
      targetAccountIds: this.targetAccountIds,
    });

    const count = Array.isArray(response)
      ? response.length
      : 0;
    $.export("$summary", `Successfully retrieved ${count} trade${count === 1
      ? ""
      : "s"}`);
    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
BitMEX	`bitmex`	`app`	This component uses the BitMEX app.
Filter	`filter`	`object`	Generic table filter. Send JSON key/value pairs, such as `{"execType": ["Settlement", "Trade"]}` to filter on multiple values. For explanations on filters refer to http://www.onixs.biz/fix-dictionary/5.0.SP2/msgType_8_8.html
Symbol	`symbol`	`string`	Select a value from the drop down menu.
Columns	`columns`	`string[]`	Array of column names to fetch. If omitted, will return all columns. Note that this method will always return item keys, even when not specified, so you may receive more columns that you expect.
Count	`count`	`integer`	Number of results to fetch. Must be a positive integer. Defaults to 100
Start	`start`	`integer`	Starting point for results. Defaults to 0
Reverse	`reverse`	`boolean`	If `true`, will sort results newest first. Defaults to `false`
Start Time	`startTime`	`string`	Starting date filter for results (format: `YYYY-MM-DDTHH:mm:ss.sssZ`)
End Time	`endTime`	`string`	Ending date filter for results (format: `YYYY-MM-DDTHH:mm:ss.sssZ`)
Target Account ID	`targetAccountId`	`integer`	AccountId fetching the trade history, must be a paired account with main user
Target Account IDs	`targetAccountIds`	`string`	AccountIds fetching the trade history, must be a paired account with main user. Can be wildcard `*` to get all accounts linked to the authenticated user

List Trades with BitMEX API on New Message In Channels (Instant) from Slack (legacy) API

Pipedream makes it easy to connect APIs for BitMEX, Slack (legacy) and 3,000+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of3,000+apps by most popular

1
-
24
of
3,000+
apps by most popular