← Slack + Firebase Admin SDK integrations

Save Event to Firestore with Firebase Admin SDK API on New Message In Channels (Instant) from Slack API

Pipedream makes it easy to connect APIs for Firebase Admin SDK, Slack and 800+ other apps remarkably fast.

Trigger workflow on
New Message In Channels (Instant) from the Slack API
Next, do this
Save Event to Firestore with the Firebase Admin SDK 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 Firebase Admin SDK 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. Configure Resolve names
    5. Configure Ignore bots
  3. Configure the Save Event to Firestore action
    1. Connect your Firebase Admin SDK account
    2. Configure deliveryId
    3. Configure firestoreCollection
    4. Configure data
  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.0
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.0",
  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

Resolve user and channel names (incurs extra API calls)

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.4.2
Key:firebase_admin_sdk-replicate-event-firestore

Action Code

// legacy_hash_id: a_rJipb5
import admin from "firebase-admin";
import lodash from "lodash";

export default {
  key: "firebase_admin_sdk-replicate-event-firestore",
  name: "Save Event to Firestore",
  version: "0.4.2",
  type: "action",
  props: {
    firebase_admin_sdk: {
      type: "app",
      app: "firebase_admin_sdk",
    },
    deliveryId: {
      type: "string",
    },
    firestoreCollection: {
      type: "string",
    },
    data: {
      type: "string",
    },
  },
  async run({ $ }) {
    // Enter values for the following parameters below this code step,
    // These get passed to the initializeApp method below.
    const {
      projectId,
      clientEmail,
      privateKey,
    } = this.firebase_admin_sdk.$auth;

    // Before passing the privateKey to the initializeApp constructor,
    // we have to replace newline characters with literal newlines
    const formattedPrivateKey = privateKey.replace(/\\n/g, "\n");

    const app = admin.initializeApp({
      credential: admin.credential.cert({
        projectId,
        clientEmail,
        privateKey: formattedPrivateKey,
      }),
    });

    const db = admin.firestore();
    const deliveryId = this.deliveryId;

    let updates = [];
    updates.push(`updating ${deliveryId}`);

    const p1 = db.collection(this.firestoreCollection).doc(deliveryId)
      .set(lodash.assign({}, this.data, {
        pipedream: {
          updatedAt: (new Date().toISOString()),
        },
      }))
      .then(function() {
        updates.push("Updated successfully");
        app.delete().then(function() {
          updates.push("App deleted successfully");
        })
          .catch(function(error) {
            updates.push("Error deleting app:", error);
          });
      })
      .catch(function(error) {
        updates.push("Error writing:", error);
      });

    const result = await Promise.all([
      p1,
    ]);

    $.export("updates", updates);

    return result;
  },
};

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
Firebase Admin SDKfirebase_admin_sdkappThis component uses the Firebase Admin SDK app.
deliveryIddeliveryIdstring
firestoreCollectionfirestoreCollectionstring
datadatastring

Action Authentication

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

1) Enable the Cloud Firestore API on your Firebase account, and make sure you've created at least one collection in the database.

2) Follow these instructions to generate a private key tied to your Firebase service account. This will generate a JSON file that contains the project ID, private key, and client email that you should paste below.

3) When entering the private key, please add the full string included in the JSON file, from -----BEGIN PRIVATE KEY----- to -----END PRIVATE KEY-----, with all newline characters included.

About Firebase Admin SDK

Firebase is Google's mobile platform that helps you quickly develop high-quality apps and grow your business.

More Ways to Connect Firebase Admin SDK + Slack