← Slack + Bubble integrations

Bubble with Bubble API on New Message In Channels (Instant) from Slack API

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

Trigger workflow on
New Message In Channels (Instant) from the Slack API
Next, do this
Bubble with the Bubble API
No credit card required
Into to Pipedream
Watch us build a workflow
Watch us build a workflow
7 min
Watch now ➜
Trusted by 250,000+ developers from startups to Fortune 500 companies:
Trusted by 250,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

This integration creates a workflow with a Slack trigger and Bubble 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 (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
  3. Configure the Bubble action
    1. Connect your Bubble account
  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 new event when a new message is posted to one or more channels
Version:1.0.1
Key:slack-new-message-in-channels

Trigger Code

import common from "../common/base.mjs";

export default {
  ...common,
  key: "slack-new-message-in-channels",
  name: "New Message In Channels (Instant)",
  version: "1.0.1",
  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 != 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.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;
    },
  },
};

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.
N/AnameCache$.service.dbThis component uses $.service.db to maintain state between component invocations.
Channelsconversationsstring[]Select a value from the drop down menu.
slackApphook$.interface.apphook
Resolve NamesresolveNamesboolean

Instead of returning channel, team, and user as IDs, return their human-readable names.

Ignore BotsignoreBotboolean

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

Description:
Version:0.1.1
Key:bubble-bubble

Action Code

// legacy_hash_id: a_YEiwAL
import { axios } from "@pipedream/platform";

export default {
  key: "bubble-bubble",
  name: "Bubble",
  version: "0.1.1",
  type: "action",
  props: {
    bubble: {
      type: "app",
      app: "bubble",
    },
  },
  async run({ $ }) {
  // Since every Bubble API is specific to its associated app, you'll
  // need to modify the code below to work with your API. This code
  // is meant to provide the scaffolding you need to get started.
    return await axios($, {
      url: `${this.bubble.$auth.root_url}`,
      headers: {
        Authorization: `Bearer ${this.bubble.$auth.api_key}`,
      },
    });
  },
};

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
BubblebubbleappThis component uses the Bubble app.

Action Authentication

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

  1. Activate the Bubble API for your app (within your app, visit Settings -> API). Bubble exposes both a Workflow and a Data API — read about both to understand which one you should enable.

  2. Each API has a unique Root URL. If you activate both the Workflow and the Data API for your application, you'll need to connect each as separate apps in Pipedream, labeling them appropriately in the Nickname field below. You'll also be asked to generate an API key. Enter both of those values in the form below.


The API Bubble exposes for your app is specific to your app. For example, the paths you make HTTP requests against are tied to the names of your Bubble workflows. Because of this, the starter code Pipedream produces for Bubble will not immediately work. You'll need to modify the code to work with your app's endpoints. Bubble generates a Swagger specification specific to your app that should list each of its available endpoints, which should help you develop against it.

About Bubble

Code-free programming language

More Ways to Connect Bubble + Slack

Bubble with Bubble API on New Direct Message (Instant) from Slack API
Slack + Bubble
 
Try it
Bubble with Bubble API on New Mention (Instant) from Slack API
Slack + Bubble
 
Try it
Bubble with Bubble API on New Reaction Added (Instant) from Slack API
Slack + Bubble
 
Try it
Bubble with Bubble API on New Star Added (Instant) from Slack API
Slack + Bubble
 
Try it
Bubble with Bubble API on New Star Added To Message (Instant) from Slack API
Slack + Bubble
 
Try it
New Message In Channels (Instant) from the Slack API

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

 
Try it
New Direct Message (Instant) from the Slack API

Emit new event when a message was posted in a direct message channel

 
Try it
New Mention (Instant) from the Slack API

Emit new event when a username or specific keyword is mentioned in a channel

 
Try it
New Reaction Added (Instant) from the Slack API

Emit new event when a member has added an emoji reaction to an item

 
Try it
New Star Added (Instant) from the Slack API

Emit new event when a star is added to an item

 
Try it
Send Message to a Public Channel with the Slack API

Send a message to a public channel and customize the name and avatar of the bot that posts the message. See postMessage or scheduleMessage docs here

 
Try it
Send Message to a Private Channel with the Slack API

Send a message to a private channel and customize the name and avatar of the bot that posts the message. See postMessage or scheduleMessage docs here

 
Try it
Send a Direct Message with the Slack API

Send a direct message to a single user. See postMessage or scheduleMessage docs here

 
Try it
Send Message Using Block Kit with the Slack API

Send a message using Slack's Block Kit UI framework to a channel, group or user. See postMessage or scheduleMessage docs here

 
Try it
Reply to a Message Thread with the Slack API

Send a message as a threaded reply. See postMessage or scheduleMessage docs here

 
Try it