← Twilio + Slack integrations

Reply to a Message Thread with Slack APIon New Incoming SMS from Twilio API

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

Trigger workflow on
New Incoming SMS from the Twilio API
Next, do this
Reply to a Message Thread with the Slack 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 Twilio trigger and Slack 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 Incoming SMS trigger
    1. Connect your Twilio account
    2. Select a Incoming Phone Number
    3. Configure Twilio Auth Token
    4. Optional- Configure SMS Response Message
  3. Configure the Reply to a Message Thread action
    1. Connect your Slack account
    2. Configure Thread Timestamp
    3. Configure Reply Channel or Conversation ID
    4. Configure Text
    5. Optional- Configure Send as User
    6. Optional- Configure Bot Username
    7. Optional- Configure Icon (emoji)
    8. Optional- Configure Icon (image URL)
  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:Configures a webhook in Twilio, tied to an incoming phone number, and emits an event each time an SMS is sent to that number
Version:0.0.4
Key:twilio-new-incoming-sms

Trigger Code

const twilio = require("../../twilio.app.js");
const MessagingResponse = require("twilio").twiml.MessagingResponse;
const twilioClient = require("twilio");

module.exports = {
  key: "twilio-new-incoming-sms",
  name: "New Incoming SMS",
  description:
    "Configures a webhook in Twilio, tied to an incoming phone number, and emits an event each time an SMS is sent to that number",
  version: "0.0.4",
  dedupe: "unique",
  props: {
    twilio,
    incomingPhoneNumber: { propDefinition: [twilio, "incomingPhoneNumber"] },
    authToken: { propDefinition: [twilio, "authToken"] },
    responseMessage: { propDefinition: [twilio, "responseMessage"] },
    http: {
      type: "$.interface.http",
      customResponse: true,
    },
  },
  hooks: {
    async activate() {
      console.log(
        `Creating webhook for phone number ${this.incomingPhoneNumber}`
      );
      const createWebhookResp = await this.twilio.setIncomingSMSWebhookURL(
        this.incomingPhoneNumber,
        this.http.endpoint
      );
      console.log(createWebhookResp);
    },
    async deactivate() {
      console.log(
        `Removing webhook from phone number ${this.incomingPhoneNumber}`
      );
      const deleteWebhookResp = await this.twilio.setIncomingSMSWebhookURL(
        this.incomingPhoneNumber,
        "" // remove the webhook URL
      );
      console.log(deleteWebhookResp);
    },
  },
  async run(event) {
    const { body, headers } = event;
    const twiml = new MessagingResponse();

    // https://support.twilio.com/hc/en-us/articles/223134127-Receive-SMS-and-MMS-Messages-without-Responding
    let responseBody = "<Response></Response>";
    if (this.responseMessage) {
      twiml.message(this.responseMessage);
      responseBody = twiml.toString();
    }

    this.http.respond({
      status: 200,
      headers: { "Content-Type": "text/xml" },
      body: responseBody,
    });

    const twilioSignature = headers["x-twilio-signature"];
    if (!twilioSignature) {
      console.log("No x-twilio-signature header in request. Exiting.");
      return;
    }

    // See https://www.twilio.com/docs/usage/webhooks/webhooks-security
    if (
      !twilioClient.validateRequest(
        this.authToken,
        twilioSignature,
        `${this.http.endpoint}/`, // This must match the incoming URL exactly, which contains a /
        body
      )
    ) {
      throw new Error(
        "Computed Twilio signature doesn't match signature received in header"
      );
    }

    this.$emit(body, {
      summary: body.Body, // the content of the text message
      id: headers["i-twilio-idempotency-token"], // if Twilio retries a message, but we've already emitted, dedupe
    });
  },
};

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
TwiliotwilioappThis component uses the Twilio app.
Incoming Phone NumberincomingPhoneNumberstringSelect a value from the drop down menu.
Twilio Auth TokenauthTokenstring

Your Twilio auth token, found in your Twilio console. Required for validating Twilio events.

SMS Response MessageresponseMessagestring

The message you want to send in response to incoming messages. Leave this blank if you don't need to issue a response.

N/Ahttp$.interface.httpThis 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.

Trigger Authentication

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

In Twilio, create an API key. There are two types of keys: Master and Standard. You'll need a Master key to interact with certain API endpoints, like /Accounts. If you don't need to interact with those endpoints, you can use a Standard key.

Once created, you'll receive an Sid and Secret here that you should enter in the corresponding fields below.

Then, in your Twilio Dashboard, you'll see your Account SID listed near the top. This is required for certain API operations. Enter that in the AccountSid field below.

About Twilio

Cloud communications platform for building SMS, Voice & Messaging applications on an API built for global scale

Action

Description:Send a message as a threaded reply
Version:0.1.0
Key:slack-reply-to-a-message

Action Code

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

module.exports = {
  key: "slack-reply-to-a-message",
  name: "Reply to a Message Thread",
  description: "Send a message as a threaded reply",
  version: "0.1.0",
  type: "action",
  props: {
    slack,
    thread_ts: {
      propDefinition: [
        slack,
        "thread_ts",
      ],
      optional: false,
    },
    reply_channel: {
      propDefinition: [
        slack,
        "reply_channel",
      ],
      optional: false,
    },
    text: {
      propDefinition: [
        slack,
        "text",
      ],
      optional: false,
    },
    as_user: {
      propDefinition: [
        slack,
        "as_user",
      ],
    },
    username: {
      propDefinition: [
        slack,
        "username",
      ],
    },
    icon_emoji: {
      propDefinition: [
        slack,
        "icon_emoji",
      ],
    },
    icon_url: {
      propDefinition: [
        slack,
        "icon_url",
      ],
    },
  },
  async run() {
    return await this.slack.sdk().chat.postMessage({
      text: this.text,
      channel: this.reply_channel,
      thread_ts: this.thread_ts,
      as_user: this.as_user,
      username: this.username,
      icon_emoji: this.icon_emoji,
      icon_url: this.icon_url,
    });
  },
};

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
SlackslackappThis component uses the Slack app.
Thread Timestampthread_tsstring

Provide another message's ts value to make this message a reply (e.g., if triggering on new Slack messages, enter {{event.ts}}). Avoid using a reply's ts value; use its parent instead.

Reply Channel or Conversation IDreply_channelstring

Provide the channel or conversation ID for the thread to reply to (e.g., if triggering on new Slack messages, enter {{event.channel}}). If the channel does not match the thread timestamp, a new message will be posted to this channel.

Texttextstring

Text of the message to send (see Slack's formatting docs). This field is usually required, unless you're providing only attachments instead. Provide no more than 40,000 characters or risk truncation.

Send as Useras_userboolean

Optionally pass TRUE to post the message as the authed user, instead of as a bot. Defaults to FALSE.

Bot Usernameusernamestring

Optionally customize your bot's user name (default is Pipedream). Must be used in conjunction with as_user set to false, otherwise ignored.

Icon (emoji)icon_emojistring

Optionally provide an emoji to use as the icon for this message. E.g., :fire: Overrides icon_url. Must be used in conjunction with as_user set to false, otherwise ignored.

Icon (image URL)icon_urlstring

Optionally provide an image URL to use as the icon for this message. Must be used in conjunction with as_user set to false, otherwise ignored.

Action 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.

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.