Create Tweet with Twitter API on New Message In Channels (Instant) from Slack API

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

Trigger workflow on

New Message In Channels (Instant) from the Slack API

Next, do this

Create Tweet with the Twitter API

No credit card required

▶

Watch us build a workflow

7 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Slack trigger and Twitter 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 account
2. Optional- Select one or more Channels
3. Configure slackApphook
4. Optional- Configure Resolve Names
5. Optional- Configure Ignore Bots
Configure the Create Tweet action
1. Connect your Twitter account
2. Optional- Configure Text
3. Optional- Configure In Reply To Tweet (ID)
4. Optional- Configure Exclude Reply User IDs
5. Optional- Configure Media IDs
6. Optional- Configure Tagged User IDs
7. Optional- Configure Place ID
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

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

Version:1.0.13

Key:slack-new-message-in-channels

View on GitHub

Slack Overview#

The Pipedream Slack app enables you to build event-driven workflows that interact with the Slack API. When you authorize the Pipedream 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 Slack app 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 just makes it easier to automate anything you'd typically use the Slack API for, using Pipedream workflows.

Here are some examples of automations you can build with Pipedream on Slack:

Automate posting updates to your team channel
Create a bot to answer common questions
Integrate with your existing tools and services
Build a custom dashboard to track your team's progress
Create a bot to handle scheduling and meeting requests
And much more!

Should I use the Slack or Slack Bot app on Pipedream?

The Slack app is the easiest and most convienent option to get started. It installs the official Pipedream bot into your Slack workspace with just a few clicks.

However, if you'd like to use your own bot registered with the Slack API, you can use the Slack Bot app instead.

The Slack Bot requires a bot token to allow your Pipedream workflows to authenticate as your bot. The extra set up steps allow you to list your custom bot on the Slack Marketplace, or install the bot on other workspaces as your bot's name instead of as Pipedream.

Trigger Code#

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

export default {
  ...common,
  key: "slack-new-message-in-channels",
  name: "New Message In Channels (Instant)",
  version: "1.0.13",
  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",
      ],
    },
  },
  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;
      }
      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	`slack`	`app`	This component uses the Slack 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

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:

bookmarks:writecalls: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:readsearch: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#

Create Tweet on Twitter

Description:Create a new tweet. [See the documentation](https://developer.twitter.com/en/docs/twitter-api/tweets/manage-tweets/api-reference/post-tweets)

Version:2.1.1

Key:twitter-create-tweet

View on GitHub

Action Code#

import app from "../../app/twitter.app.mjs";
import { ACTION_ERROR_MESSAGE } from "../../common/errorMessage.mjs";
import { defineAction } from "@pipedream/types";
const DOCS_LINK = "https://developer.twitter.com/en/docs/twitter-api/tweets/manage-tweets/api-reference/post-tweets";
export default defineAction({
    key: "twitter-create-tweet",
    name: "Create Tweet",
    description: `Create a new tweet. [See the documentation](${DOCS_LINK})`,
    version: "2.1.1",
    type: "action",
    props: {
        app,
        text: {
            type: "string",
            label: "Text",
            description: "Text of the Tweet being created. Required if `Media IDs` is not set.",
            optional: true,
        },
        inReplyToTweetId: {
            type: "string",
            label: "In Reply To Tweet (ID)",
            description: "Tweet ID of the Tweet being replied to. Please note that this prop needs to be set if `Exclude Reply User IDs` is also set.",
            optional: true,
        },
        excludeReplyUserIds: {
            type: "string[]",
            label: "Exclude Reply User IDs",
            description: "A list of User IDs to be excluded from the reply Tweet thus removing a user from a thread.",
            optional: true,
        },
        mediaIds: {
            type: "string[]",
            label: "Media IDs",
            description: "A list of Media IDs being attached to the Tweet. This is only required if `Tagged User IDs` is set.",
            optional: true,
        },
        taggedUserIds: {
            type: "string[]",
            label: "Tagged User IDs",
            description: "A list of User IDs being tagged in the Tweet with Media. If the user you're tagging doesn't have photo-tagging enabled, their names won't show up in the list of tagged users even though the Tweet is successfully created.",
            optional: true,
        },
        placeId: {
            type: "string",
            label: "Place ID",
            description: "Place ID being attached to the Tweet for geo location.",
            optional: true,
        },
    },
    async run({ $ }) {
        try {
            const { text, inReplyToTweetId, excludeReplyUserIds, mediaIds, placeId, taggedUserIds, } = this;
            const params = {
                $,
                data: {
                    text,
                    ...((inReplyToTweetId || excludeReplyUserIds) && {
                        reply: {
                            exclude_reply_user_ids: excludeReplyUserIds,
                            in_reply_to_tweet_id: inReplyToTweetId,
                        },
                    }),
                    ...((mediaIds || taggedUserIds) && {
                        media: {
                            media_ids: mediaIds,
                            tagged_user_ids: taggedUserIds,
                        },
                    }),
                    ...(placeId && {
                        geo: {
                            place_id: placeId,
                        },
                    }),
                },
            };
            const response = await this.app.createTweet(params);
            $.export("$summary", `Successfully posted tweet (ID ${response.data?.id})`);
            return response;
        }
        catch (err) {
            $.export("error", err);
            throw new Error(ACTION_ERROR_MESSAGE);
        }
    },
});

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
Twitter	`app`	`app`	This component uses the Twitter app.
Text	`text`	`string`	Text of the Tweet being created. Required if `Media IDs` is not set.
In Reply To Tweet (ID)	`inReplyToTweetId`	`string`	Tweet ID of the Tweet being replied to. Please note that this prop needs to be set if `Exclude Reply User IDs` is also set.
Exclude Reply User IDs	`excludeReplyUserIds`	`string[]`	A list of User IDs to be excluded from the reply Tweet thus removing a user from a thread.
Media IDs	`mediaIds`	`string[]`	A list of Media IDs being attached to the Tweet. This is only required if `Tagged User IDs` is set.
Tagged User IDs	`taggedUserIds`	`string[]`	A list of User IDs being tagged in the Tweet with Media. If the user you're tagging doesn't have photo-tagging enabled, their names won't show up in the list of tagged users even though the Tweet is successfully created.
Place ID	`placeId`	`string`	Place ID being attached to the Tweet for geo location.

Action Authentication#

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

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

do not use

About Twitter#

From breaking news and entertainment to sports and politics, get the full story with all the live commentary. Use a Twitter developer app you've created to send API requests.

More Ways to Connect Twitter + Slack#

Other Popular Integrations#

Advanced Search with Twitter API on New Message In Channels from Slack API

Slack + Twitter

Create Tweet with Twitter API on New Message In Channels (Instant) from Slack API

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

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

Developers ♥ Pipedream

Should I use the Slack or Slack Bot app on Pipedream?

1-12of1400+apps by most popular

1
-
12
of
1400+
apps by most popular