You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 21, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,11 +38,11 @@ If you prefer to run your bot locally, see [Running the connector locally](#runn
38
38
Go back to your app on Slack. In the left navigation menu under 'Features' choose 'Event Subscriptions'. Then:
39
39
1. Turn on Enable Events
40
40
2. Enter the following URL in the Request URL field: `https://[yourherokuappname].herokuapp.com/slack/events` (replace [yourherokuappname] with the name of your app on Heroku)
41
-
Note that the url ends with '/slack/event'
41
+
Note that the url ends with '/slack/events', and that the connector is already running locally, or on Heroku, to avoid a 'Challenge parameter' error.
42
42
3. Under 'Subscribe to Bot Events', subscribe to the following event: `message.im`
43
-
4. Save changes
43
+
4. Save changes. Reinstall the app, if recommended by the dashboard
44
44
45
-
That's it! Your bot should now be available in Slack and responding to messages that are sent to it.
45
+
That's it! Your bot should now be available as an app in Slack and ready to respont to the messages sent to it.
46
46
47
47
## Adding message attachments
48
48
To add [message attachments](https://api.slack.com/docs/message-attachments), this connector looks for an output parameter `slack` in the engine response. The value of that parameter is assumed to contain the attachement JSON as defined by Slack.
@@ -65,7 +65,12 @@ If you prefer to manually install this connector or run it locally, proceed as f
65
65
```
66
66
ngrok http 3000
67
67
```
68
-
4. Start the connector with the following command (replacing the environment variables with the appropriate values):
69
-
```
68
+
4. Create a file called .env in the project's root folder, based on the sample file called '.env.sample' that is included in the project. Inside .env, replace the environment variables with the corresponding values:
0 commit comments