![]() Healthcheck to ensure your API is functional "SLACK_SIGNING_SECRET": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ", // required "SLACK_SIGNING_VERSION": "v0 "Įndpoints are provided for the following routes: Route "SLACK_OAUTH_SCOPE": "app_mentions:read chat:write ", NOTE - after applying this module you must update the SecretsManager secret with the slackbot configuration JSON (all values are optional except where indicated) Secret_name = "slackbot " # CUSTOM RESPONDERS Slack_api_function_name = "slackbot-slack-api " # SECRET Responder_function_name = "slackbot-responder " Receiver_function_name = "slackbot-receiver " See the example project for detailed usage.ĭomain_certificate_arn = data. Route53 record with regional latency routing configuration. ![]() V24 takes a more "batteries included" appoach, creating: NOTE - Previous versions of this module attempted to be as unopinionated as possible when creating Slackbots. ![]() See the section on responding to events synchronously for details. External select menus and some callbacks, for example, need to respond to Slack with custom data and cannot be processed asyncronously. In some cases, you may want your Slack app to send a custom, synchronous, response to Slack instead of an empty 200 OK. See the section on responding to events asynchronously for details. ![]() The application intentionally does very little: it will receive an event from Slack in the form of an HTTP request, verify its origin, publish the payload to EventBridge where it can be processed downstream using event patterns, and finally respond to Slack with an empty 200 OK response.Īdding asynchronous features to your slackbot is as simple as adding the appropriate EventBridge rule/target, and some kind of handler function. A simple, serverless, asynchronous HTTP back end for your Slack app. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |