Project description
The bot needs to handle four scenarios. First — approval requests: a slash command opens a modal, the request is posted with 'Approve' and 'Reject' buttons, and the decision is recorded with the approver's name and timestamp. Second — standup collection: at a set time the bot asks each participant three questions and posts a neat summary in the team channel. Third — time-off requests: an employee enters dates through an interactive form, a manager confirms with one click, the result is saved. Fourth — notifications from our internal systems: the bot receives events and distributes formatted messages to the right channels or people.
We expect implementation via official Slack API with the correct set of permissions and OAuth scopes, request signature verification, and principle of least privilege — no more access than each function needs. Interactive components, modal windows, and scheduled tasks should work reliably, and each action should be logged. Describe your approach, where you propose to host the bot and how you'll store secrets and handle request limits.
— Slash commands and modal windows for approvals
— Scheduled standup collection with summary
— Time-off flow with one-click confirmation
— Incoming webhooks from internal systems
— Minimal scopes and signed requests