Attach to event source other than express

[barlock]

I would like to use Slapp in a serverless environment. In doing so, I'm not actually ever running a real http server, all I have is the data from Slack's event api.

This would be fairly easy to hook up by just calling slapp.reciever.emit("message", msg) after building it, but I would like to have a supported way to pass in data and get it into slapp.

I imagine this would look like:

function eventReciever(data) {
    slapp.sendEvent(data)
}

This would take care of calling context, building the Message and sending it through Slapp.

[mbrevoort]

Really good point. What would you expect for format for data to be? Would you expect to have separate functions for each type of Slack request (event, slash command, action, options) or a single handler that would infer which one of those it is and emit from there?

[selfcontained]

Could data just be the body sent from slack? I would think a single function you just pass that into and let slapp route it regardless of its a slash command or from the event API would be the nicest developer experience, but am remembering all the nuances with different slack payloads for different types and wonder how much of an issue that might be.

[barlock]

Yes I was thinking it would be the data that slack posts to you. Basically the result of JSON.parse(res.body). A single function would be nice, but after looking through reciever/middleware/parse-* I think having one function per type would probably make the most sense. Otherwise you'd be relying on the data object to be a formatted version of the POST data.

[mbrevoort]

Trickiest part is that Slash commands are urlencoded, Events are application/json and actions are urlencoded json.

https://www.youtube.com/watch?v=-XSC_UG5_kU

[barlock]

Yeah that was certainly nice of them 😛. After thinking through this a bit, I think it's probably best to have 1 function per event type (event, slack, action, options) rather than inferring the event type which could get sketchy.

I also think that, given this is a more generic handler that is abstracted away from the requests coming in, that dealing with the Content-type should be up whatever is dealing with that and have these functions take the POST data converted to JSON. That should be in line with most systems.

[simonsayscode]

I also have interest in this. My goal was to create a serverless slack framework but I ended up just prototying and sticking with the default express app.

[selfcontained]

Totally, will make some time to check out that PR, been swamped lately but really want to see this feature added.

[Vlaaaaaaad]

Any updates on this?

[seratch]

I'm sorry to say, but the maintainers of this project (bolt-js) no longer support the slapp library. Please let us close this issue now.