← Slack + Bandwidth integrations

Send SMS with Bandwidth APIon New Message In Channels from Slack API

Pipedream makes it easy to connect APIs for Bandwidth, Slack and + other apps remarkably fast.

Trigger workflow on
New Message In Channels from the Slack API
Next, do this
Send SMS with the Bandwidth API
No credit card required
Trusted by 200,000+ developers from startups to Fortune 500 companies:
Trusted by 200,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

This integration creates a workflow with a Slack trigger and Bandwidth action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

  1. Select this integration
  2. Configure the New Message In Channels trigger
    1. Connect your Slack account
    2. Optional- Select one or more Channels
    3. Configure slackApphook
    4. Configure Ignore myself
    5. Configure Resolve names
    6. Configure Ignore bots
  3. Configure the Send SMS action
    1. Connect your Bandwidth account
    2. Configure To
    3. Configure From
    4. Configure Message
    5. Configure Messaging Application ID
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. Turn on the trigger

Details

This integration uses pre-built, open source 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

Description:Emit an event when a new message is posted to one or more channels
Version:0.0.2
Key:slack-new-message-in-channels

Trigger Code

const slack = require("../../slack.app.js");

module.exports = {
  key: "slack-new-message-in-channels",
  name: "New Message In Channels",
  version: "0.0.2",
  description: "Emit an event when a new message is posted to one or more channels",
  dedupe: "unique",
  props: {
    slack,
    conversations: {
      type: "string[]",
      label: "Channels",
      description: "Select one or more channels to monitor for new messages.",
      optional: true,
      async options({ prevContext }) {
        let {
          types,
          cursor,
          userNames,
        } = prevContext;
        if (types == null) {
          const scopes = await this.slack.scopes();
          types = [
            "public_channel",
          ];
          if (scopes.includes("groups:read")) {
            types.push("private_channel");
          }
          if (scopes.includes("mpim:read")) {
            types.push("mpim");
          }
          if (scopes.includes("im:read")) {
            types.push("im");
            // TODO use paging
            userNames = {};
            for (const user of (await this.slack.users()).users) {
              userNames[user.id] = user.name;
            }
          }
        }
        const resp = await this.slack.availableConversations(types.join(), cursor);
        return {
          options: resp.conversations.map((c) => {
            if (c.is_im) {
              return {
                label: `Direct messaging with: @${userNames[c.user]}`,
                value: c.id,
              };
            } else if (c.is_mpim) {
              return {
                label: c.purpose.value,
                value: c.id,
              };
            } else {
              return {
                label: `${c.is_private ?
                  "Private" :
                  "Public"
                } channel: ${c.name}`,
                value: c.id,
              };
            }
          }),
          context: {
            types,
            cursor: resp.cursor,
            userNames
          },
        };
      },
    },
    slackApphook: {
      type: "$.interface.apphook",
      appProp: "slack",
      async eventNames() {
        return this.conversations || [];
      },
    },
    ignoreMyself: {
      type: "boolean",
      label: "Ignore myself",
      description: "Ignore messages from me",
      default: true,
    },
    resolveNames: {
      type: "boolean",
      label: "Resolve names",
      description: "Resolve user and channel names (incurs extra API calls)",
      default: false,
    },
    ignoreBot: {
      type: "boolean",
      label: "Ignore bots",
      description: "Ignore messages from bots",
      default: false,
    },
    nameCache: "$.service.db",
  },
  methods: {
    async maybeCached(key, refreshVal, timeoutMs = 3600000) {
      let record = this.nameCache.get(key);
      const time = Date.now();
      if (!record || time - record.ts > timeoutMs) {
        record = {
          ts: time,
          val: await refreshVal(),
        };
        this.nameCache.set(key, record);
      }
      return record.val;
    },
    async getBotName(id) {
      return this.maybeCached(`bots:${id}`, async () => {
        const info = await this.slack.sdk().bots.info({
          bot: id,
        });
        if (!info.ok) throw new Error(info.error);
        return info.bot.name;
      });
    },
    async getUserName(id) {
      return this.maybeCached(`users:${id}`, async () => {
        const info = await this.slack.sdk().users.info({
          user: id,
        });
        if (!info.ok) throw new Error(info.error);
        return info.user.name;
      });
    },
    async getConversationName(id) {
      return this.maybeCached(`conversations:${id}`, async () => {
        const info = await this.slack.sdk().conversations.info({
          channel: id,
        });
        if (!info.ok) throw new Error(info.error);
        if (info.channel.is_im) {
          return `DM with ${await this.getUserName(info.channel.user)}`;
        } else {
          return info.channel.name;
        }
      });
    },
    async getTeamName(id) {
      return this.maybeCached(`team:${id}`, async () => {
        try {
          const info = await this.slack.sdk().team.info({
            team: id,
          });
          return info.team.name;
        } catch (err) {
          console.log("Error getting team name, probably need to re-connect the account at pipedream.com/apps", err);
          return id;
        }
      });
    },
  },
  async run(event) {
    if (event.subtype != null && event.subtype != "bot_message" && event.subtype != "file_share") {
      // 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.ignoreMyself && event.user == this.slack.mySlackId()) {
      return;
    }
    if (this.ignoreBot && event.subtype == "bot_message") {
      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);
      }
    }
    if (!event.client_msg_id) {
      event.pipedream_msg_id = `pd_${Date.now()}_${Math.random().toString(36)
        .substr(2, 10)}`;
    }

    this.$emit(event, {
      id: event.client_msg_id || event.pipedream_msg_id,
    });
  },
};

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.
LabelPropTypeDescription
SlackslackappThis component uses the Slack app.
Channelsconversationsstring[]Select a value from the drop down menu.
slackApphook$.interface.apphook
Ignore myselfignoreMyselfboolean

Ignore messages from me

Resolve namesresolveNamesboolean

Resolve user and channel names (incurs extra API calls)

Ignore botsignoreBotboolean

Ignore messages from bots

N/AnameCache$.service.dbThis component uses $.service.db to maintain state between component invocations.

Trigger Authentication

Slack uses OAuth authentication. When you connect your Slack account, Pipedream will open a popup window where you can sign into Slack 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 API.

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

calls:readcalls:writechannels:historychannels:readchannels:writednd:readdnd:writeemoji:readfiles:readgroups:historygroups:readgroups:writeim:historyim:readim:writelinks:readlinks:writempim:historympim:readmpim:writepins:readpins:writereactions:readreactions:writereminders:readreminders:writeremote_files:readremote_files:sharestars:readstars:writeteam:readusergroups:readusergroups:writeusers:readusers:read.emailusers:writechat:write:botchat:write:usercommandsfiles:write:userusers.profile:writeusers.profile:read

About Slack

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

Description:Send an SMS message using Bandwidth's Messaging API
Version:1.0.0
Key:bandwidth-send-sms

Action Code

const bandwidth = require("../../bandwidth.app.js");

module.exports = {
  key: "bandwidth-send-sms",
  name: "Send SMS",
  description: "Send an SMS message using Bandwidth's Messaging API",
  type: "action",
  version: "1.0.0",
  props: {
    bandwidth,
    messageTo: {
      propDefinition: [
        bandwidth,
        "messageTo",
      ],
    },
    from: {
      propDefinition: [
        bandwidth,
        "from",
      ],
    },
    message: {
      propDefinition: [
        bandwidth,
        "message",
      ],
    },
    messagingApplicationId: {
      propDefinition: [
        bandwidth,
        "messagingApplicationId",
      ],
    },
  },
  async run () {
    const response = await this.bandwidth.sendSms(
      this.messageTo,
      this.from,
      this.message,
      this.messagingApplicationId,
    );
    console.log("Status Code:", response.statusCode);
    console.log("Message ID:", response.result.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.

LabelPropTypeDescription
BandwidthbandwidthappThis component uses the Bandwidth app.
TomessageTostring

The number the message will be sent to, in E164 format ex +19195551234

Fromfromstring

The number the call or message event will come from, in E164 format ex +19195551234

Messagemessagestring

The text message content

Messaging Application IDmessagingApplicationIdstring

The ID from the messaging application created in the Bandwidth Dashboard.

The application must be associated with the location that the from number lives on.

Action Authentication

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

Bandwidth.com requires the user's username:password pair to be encoded as part of the header. (docs)
The accountId is used as part of the url to make API requests. Ex: https://dashboard.bandwidth.com/api/accounts/{accountId}/

About Bandwidth

Enterprise Grade Voice, Messaging, and 911 Access

About Pipedream

Stop writing boilerplate code, struggling with authentication and managing infrastructure. Start connecting APIs with code-level control when you need it — and no code when you don't.

Into to Pipedream
Watch us build a workflow
Watch us build a workflow
4 min
Watch now ➜
"The past few weeks, I truly feel like the clichéd 10x engineer."
@heyellieday
Powerful features that scale
Manage concurrency and execution rate
Manage concurrency and execution rate

Queue up to 10,000 events per workfow and manage the concurrency and rate at which workflows are triggered.

Process large payloads up to 5 terabytes
Process large payloads up to 5 terabytes

Large file support enables you to trigger workflows with any data (e.g., large JSON files, images and videos) up to 5 terabytes.

Return custom responses to HTTP requests
Return custom responses to HTTP requests

Return any JSON-serializable response from an HTTP triggered workflow using $respond().

Use most npm packages
Use most npm packages

To use any npm package, just require() it -- there's no npm install or package.json required.

Maintain state between executions
Maintain state between executions

Use $checkpoint to save state in one workflow invocation and read it the next time your workflow runs.

Pass data between steps
Pass data between steps

Return data from any step to inspect it in a human-friendly way and reference the data in future steps via the steps object.