Skip to content
This repository has been archived by the owner on Oct 9, 2020. It is now read-only.

Interactive Messages need a publicly exposed https address for the Request URL #1

Open
E-ThanG opened this issue Sep 10, 2017 · 1 comment

Comments

@E-ThanG
Copy link

E-ThanG commented Sep 10, 2017

Hello,

I've been working on figuring out the interactive messages in slack for a few days now. I finally found a tutorial that detailed the required steps, including in the developer console. Ultimately I didn't know that I needed to have a publicly exposed server for some URLs and that http wasn't supported on some of them as well. I followed the instructions here to figure this out: https://github.com/howdyai/botkit/blob/master/docs/slack-events-api.md and used ngrok.io to tunnel to my localhost webserver. It'd be awesome of the instructions here included the required steps to get the example to actually function to a private dev box. Which URLs need to be public and so on.

It'd also be nice if something said about the "Request URL" being the same thing as the "Action URL", I'm not sure why there are two names for the same thing, but that isn't intuitive at all. I spent some time trying to figure out what this third URL was. It'd be helpful to mention which lines in the script need to be edited and to which value. I found conflicting information about the channel being plain text channel name or a unique slack internal name. Some examples had the # prepended, others didn't.

Thank you,

Ethan Grinnell

@Roach
Copy link
Contributor

Roach commented Jan 3, 2018

Thanks for the notes!

I'll add some ngrok notes and a link to our Ngrok tutorial 👍

The naming of Interactive Components has changed since I wrote this, so I'll get that updated as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants