Using Slack's Bolt framework in Pipedream

ekellener · February 20, 2023, 1:27am

Hi,

I’m interested in building a slack application built in NodeJS, and was thinking about doing it in Pipedream. The question is if I’d like to use the bolt framework which has a different listener, http responder than axios.

I’m assuming I would use an import at the top

import { App } from ‘@slack/bolt’;

But wasn’t sure if it’s possible to not use the Axios.

Is this possible, and if so, do you have any example that uses the bolt framework in a NodeJS pipedream workflow?

Thanks
Erik

ekellener · February 23, 2023, 4:39am

I was able to find a reference example of using Google Functions which I “think” might work, except, I’m running into some import issues for the modules.

Here’s the reference example:

github.com

seratch/slack-app-examples/blob/966ce420d199472cd7daf996c741aa6b8a7aac8d/bolt-gcp-js-template/app.js

'use strict';

const config = require('./config.js');

// ------------------------------------------------------
// Bot app
// https://slack.dev/bolt/
const { App, ExpressReceiver } = require('@slack/bolt');
const expressReceiver = new ExpressReceiver({
  signingSecret: config.SLACK_SIGNING_SECRET
});
const app = new App({
  token: config.SLACK_BOT_TOKEN,
  receiver: expressReceiver
});
const expressApp = expressReceiver.app;

// ------------------------------------------------------
// If you need to use API methods that are not listed on https://api.slack.com/bot-users#methods
// you need to use user api token instead like this:

This file has been truncated. show original

When I import
import { App, ExpressReceiver } from ‘@slack/bolt’

I get the following
Code Error

SyntaxError: The requested module ‘@slack/bolt’ does not provide an export named ‘App’
Same thing with ExpressReceiver

Any ideas? I was able to get it to work with the require, but that created an issue when using the export default for the exporting of the module.

vunguyenhung · February 23, 2023, 5:00am

Hello @ekellener,

I think Slack’s Bolt framework requires a dedicated server (or serverless function) running that listen on Slack events. This is essentially the purpose of Pipedream Slack sources.

So some ways I can think of:

Only use Pipedream Slack sources and build a workflow around your usecase
Build you Slack app on GCP function or similar platform, then having it calling Pipedream HTTP webhook trigger to execute some actions on an event

ekellener · February 23, 2023, 8:11pm

Yeah, I like the idea of using the source for the workflow, but I’m still running into the import issue to get it to run w/o an error. Found some workarounds online to try, but they all require access to the package.json

Any ideas?