30 Claude Prompts That Build Slack Bots

You are a Slack developer building interactive poll tooling. <context> I need a quick poll bot delivered as one self-contained, ready-to-run Bolt for JavaScript artifact. A slash command creates a poll with custom options and live vote tallies shown as buttons in the channel. </context> <inputs> - Command syntax: [E.G. /poll "Question" "Option A" "Option B"] - Vote rule: [SINGLE CHOICE / MULTI] - Show voters: [NAMES / COUNT ONLY] - Who can close: [ANYONE / CREATOR ONLY] </inputs> <task> Build app.js: a slash command that parses the question and options, posts a Block Kit poll where each option is a button showing its live count, and action handlers that record each user's vote (enforcing single or multi choice), update the message counts, and optionally list voters. Add a "Close poll" button (creator-gated) that freezes results and highlights the winner. Include the manifest and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; parse quoted options robustly; real interactive buttons. - Env-only tokens; store votes per poll and per user; prevent double-counting; chat.update for live tallies. - Valid, commented code. </constraints> <format> Return the code as an artifact (file per block), then a setup guide and how to persist polls so counts survive a restart. </format>

You are a Slack developer building anonymous feedback tools. <context> I need an anonymous survey bot delivered as one self-contained, ready-to-run Bolt for JavaScript artifact. It DMs a multi-question survey to a group and posts aggregated results with no way to trace an answer to a person. </context> <inputs> - Recipients: [CHANNEL MEMBERS / USER LIST] - Questions: [MIX OF SCALE 1-5 AND FREE TEXT] - Results channel: [#CHANNEL] - Close time: [WHEN TO AGGREGATE, TZ] </inputs> <task> Build app.js: a trigger that DMs each recipient a Block Kit modal with the questions, a view handler that stores responses WITHOUT any user identifier, and a close job that posts aggregated results (average and distribution per scale question, a shuffled list of free-text answers) to the results channel with the response count. Include the manifest and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; never store user ID alongside answers; real modal and Block Kit output. - Env-only tokens; suppress results if fewer than a minimum number of responses to protect anonymity. - Valid, commented code. </constraints> <format> Return the code as an artifact (file per block), then a setup guide and a note on the anonymity guarantees and the minimum-response threshold. </format>

You are a people-analytics engineer building recurring pulse surveys in Slack. <context> I need a recurring eNPS pulse bot delivered as one self-contained, ready-to-run Bolt for JavaScript artifact. On a schedule it asks the classic 0-10 recommend question plus one open comment, then computes and posts the eNPS score. </context> <inputs> - Cadence: [E.G. MONTHLY, DAY + TZ] - Audience: [CHANNEL / USER GROUP] - Questions: [0-10 SCORE + OPTIONAL COMMENT] - Results destination: [#CHANNEL / DM TO HR] </inputs> <task> Build app.js: a scheduler that DMs each person a Block Kit modal with a 0-10 rating and a comment field, a view handler that stores scores anonymously by period, and a close step that classifies promoters/passives/detractors, computes eNPS = %promoters - %detractors, and posts a Block Kit summary with the score, breakdown, response rate, and shuffled comments. Include the manifest and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; store by period; anonymous; correct eNPS math. - Env-only tokens; suppress results below a minimum response count; real modal and Block Kit output. - Valid, commented code. </constraints> <format> Return the code as an artifact (file per block), then a setup guide and how to trend eNPS across periods over time. </format>

You are a Slack developer building fun team-decision bots. <context> I need a decision poll bot delivered as one self-contained, ready-to-run Bolt for JavaScript artifact. It runs a timed poll for group decisions (lunch spot, meeting time, name vote) and auto-announces the winner when the timer ends. </context> <inputs> - Command: [E.G. /decide] - Options source: [TYPED IN OR A PRESET LIST LIKE LUNCH SPOTS] - Timer: [E.G. AUTO-CLOSE IN 30 MIN] - Tie rule: [RANDOM PICK / RUNOFF] </inputs> <task> Build app.js: a slash command that starts a poll with the given options and a countdown, posts a Block Kit message with vote buttons and a visible "closes at" time, records votes, and a scheduled close that tallies, announces the winner with a celebratory message, and applies the tie rule when needed. Include the manifest and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; real buttons, a scheduled auto-close, and tie handling. - Env-only tokens; store votes per poll; disable buttons after close; light, non-cheesy copy. - Valid, commented code. </constraints> <format> Return the code as an artifact (file per block), then a setup guide and how to save preset option lists (e.g. favorite lunch spots). </format>

You are a Slack developer building emoji-reaction voting tools. <context> I need a reaction-vote tally bot delivered as one self-contained, ready-to-run Bolt for JavaScript artifact. It watches a message for specific emoji reactions and reports a live tally, useful for lightweight yes/no or option votes. </context> <inputs> - How a vote starts: [SLASH COMMAND ON A MESSAGE / SHORTCUT] - Emoji-to-option mapping: [E.G. :white_check_mark: = YES, :x: = NO] - Report style: [THREADED REPLY / UPDATE ORIGINAL] - Close condition: [MANUAL / AFTER N MINUTES] </inputs> <task> Build app.js: a trigger that marks a message as a reaction poll and pre-adds the mapped emojis, listeners for reaction_added and reaction_removed that keep a live count per option (ignoring emojis outside the map), and a report that updates a Block Kit tally either in-thread or on the original message, then declares the result on close. Include the manifest and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; subscribe to reaction events; count only mapped emojis. - Env-only tokens; handle removed reactions correctly (decrement); avoid counting the bot's own seed reactions. - Valid, commented code. </constraints> <format> Return the code as an artifact (file per block), then the exact event scopes needed and how to change the emoji-to-option map. </format>

You are a Slack developer building scheduling bots. <context> I need a recurring reminder bot delivered as one self-contained, ready-to-run Bolt for JavaScript artifact. People set repeating reminders from a slash command and the bot posts them on schedule to a user or channel. </context> <inputs> - Command syntax: [E.G. /remind #channel "text" every weekday at 9am] - Recurrence types: [DAILY, WEEKDAYS, WEEKLY, MONTHLY] - Timezone handling: [PER-USER TZ FROM PROFILE] - List/cancel: [HOW USERS MANAGE THEIR REMINDERS] </inputs> <task> Build app.js: a slash command that parses target, message, and recurrence into a stored schedule, a scheduler that fires due reminders in each user's timezone and posts them, and subcommands to list and cancel a user's reminders via a Block Kit view. Use chat.scheduleMessage where the recurrence allows and a cron loop for repeats. Include the manifest and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; parse natural-ish recurrence; respect each user's timezone. - Env-only tokens; persist schedules so they survive restart (isolated store you can swap for a DB); no duplicate fires. - Valid, commented code. </constraints> <format> Return the code as an artifact (file per block), then a setup guide, the parsing grammar you support, and how to move the store to a database. </format>

You are a Slack developer building meeting-reminder automation. <context> I need a meeting reminder bot delivered as one self-contained, ready-to-run Bolt for JavaScript artifact. Before each meeting it DMs attendees a reminder with the agenda and join link, and a follow-up to capture notes after. </context> <inputs> - Meeting source: [STATIC LIST / CALENDAR FEED / MANUAL /meeting COMMAND] - Lead time: [E.G. 10 MIN BEFORE] - Fields: [TITLE, TIME, JOIN LINK, AGENDA, ATTENDEES] - Post-meeting: [PROMPT FOR NOTES? WHERE TO POST] </inputs> <task> Build app.js: ingestion of meetings (from a list or a /meeting command that captures the fields), a scheduler that DMs each attendee a Block Kit reminder with title, time, join button, and agenda at the lead time, and an optional post-meeting prompt asking the organizer for notes and posting them to a channel. Include the manifest and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; timezone-correct scheduling; join link as a real button. - Env-only tokens; do not double-remind; store meetings in an isolated, swappable module. - Valid, commented code. </constraints> <format> Return the code as an artifact (file per block), then a setup guide and how to feed it from a Google/Outlook calendar via ICS or API. </format>

You are a Slack developer building team-culture bots. <context> I need a birthday and work-anniversary bot delivered as one self-contained, ready-to-run Bolt for JavaScript artifact. Each morning it checks for birthdays and work anniversaries and posts a warm celebration to a channel. </context> <inputs> - People data: [CSV/ARRAY OF NAME, SLACK ID, BIRTHDAY, START DATE] - Celebration channel: [#CHANNEL] - Daily check time: [TIME + TZ] - Message style: [WARM, PLAYFUL, MINIMAL] </inputs> <task> Build app.js: a daily job that compares today (month/day) against each person's birthday and start date, posts a Block Kit celebration @mentioning the person (for anniversaries include the number of years), and handles multiple celebrations on the same day in one message. Keep the people data in a separate, editable file. Include the manifest and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; people data isolated and easy to edit; correct year math for anniversaries. - Env-only tokens; handle Feb 29 gracefully; group same-day celebrations; warm, non-cringe copy. - Valid, commented code. </constraints> <format> Return the code as an artifact (file per block), then a setup guide and how to load people data from an HR system instead of a file. </format>

You are a Slack developer building deadline-tracking bots. <context> I need a task deadline nudger delivered as one self-contained, ready-to-run Bolt for JavaScript artifact. It tracks tasks with due dates and DMs owners escalating reminders as deadlines approach and pass. </context> <inputs> - Task source: [/task COMMAND / IMPORTED LIST WITH OWNER + DUE DATE] - Reminder cadence: [E.G. 2 DAYS BEFORE, DAY OF, OVERDUE DAILY] - Escalation: [PING MANAGER WHEN OVERDUE > X DAYS] - Owner timezone: [FROM PROFILE] </inputs> <task> Build app.js: a /task command (or import) capturing title, owner, and due date; a daily job that DMs owners a Block Kit reminder at each cadence stage with a "Mark done" and "Snooze" button; escalation that pings a manager when a task is overdue beyond the threshold; and status updates that stop reminders once done. Include the manifest and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; owner-timezone-aware; escalating stages, not repeated identical pings. - Env-only tokens; "Mark done" halts further nudges; store tasks in a swappable module. - Valid, commented code. </constraints> <format> Return the code as an artifact (file per block), then a setup guide and how to sync tasks from a project tool via its API. </format>

You are a Slack developer building distributed-team scheduling. <context> I need a timezone-aware team reminder bot delivered as one self-contained, ready-to-run Bolt for JavaScript artifact. It sends a recurring reminder to each team member at the same LOCAL time, wherever they are. </context> <inputs> - Reminder text: [WHAT TO SEND] - Local target time: [E.G. 9:00 LOCAL EACH WEEKDAY] - Team: [CHANNEL / USER LIST] - Delivery: [DM / EPHEMERAL IN CHANNEL] </inputs> <task> Build app.js: read each member's timezone from their Slack profile (users.info), compute their next local occurrence of the target time, schedule the reminder per user (via chat.scheduleMessage or a per-user timer), and reschedule for the next occurrence after it fires. Handle DST correctly by recomputing from the timezone rather than storing fixed UTC offsets. Include the manifest and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; derive timezone from profile; recompute each cycle so DST is correct. - Env-only tokens; no double-sends; skip users with no timezone set (log them). - Valid, commented code. </constraints> <format> Return the code as an artifact (file per block), then a setup guide, the scopes needed to read timezones, and how to add opt-out. </format>

You are a developer-experience engineer wiring GitHub into Slack. <context> I need a GitHub-to-Slack PR notification bot delivered as one self-contained, ready-to-run artifact. It receives GitHub webhooks and posts clean, actionable Slack messages for pull request events. </context> <inputs> - Events to handle: [OPENED, REVIEW REQUESTED, APPROVED, MERGED] - Notify channel(s): [#CHANNEL, OR PER-REPO MAP] - Reviewer mapping: [GITHUB LOGIN -> SLACK ID, IF ANY] - Delivery: [BOT TOKEN / INCOMING WEBHOOK] </inputs> <task> Build a small server (Express or Bolt receiver) that verifies the GitHub webhook signature, parses pull_request and review events, and posts a Block Kit message per event: PR title as a link, author, status, requested reviewers (@mentioning mapped Slack users), and a merge celebration on merge. Include package.json, the endpoint route, the app manifest or webhook notes, and .env.example. </task> <constraints> - One runnable project as labeled code blocks; VERIFY the X-Hub-Signature-256 HMAC before processing. - Env-only secrets and tokens; map GitHub logins to Slack IDs so mentions actually notify; clickable PR links. - Valid, commented code; ignore event types you do not handle. </constraints> <format> Return the code as an artifact (file per block), then how to register the webhook, the exact scopes, and how to add per-repo channel routing. </format>

You are an integration engineer connecting an issue tracker to Slack. <context> I need an issue-tracker sync bot delivered as one self-contained, ready-to-run artifact. It creates issues from Slack and posts status updates back, keeping a two-way link between a thread and an issue. </context> <inputs> - Tracker: [E.G. LINEAR / JIRA / GITHUB ISSUES] - Create command: [E.G. /issue] - Fields: [TITLE, DESCRIPTION, PROJECT/LABEL, ASSIGNEE] - Status channel: [#CHANNEL] - Tracker API auth: [TOKEN VIA ENV] </inputs> <task> Build app.js (Bolt): a /issue slash command opening a modal, a view handler that calls the tracker's API to create the issue and posts a Block Kit card with the issue key, link, and status, storing the mapping between the Slack message and the issue ID; plus a webhook endpoint that receives tracker status changes and updates the Slack message/thread. Include the manifest, the API client module, and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; isolate the tracker API calls in one client module so it is swappable. - Env-only tokens for both Slack and the tracker; verify inbound webhook auth; keep the Slack-to-issue map. - Valid, commented code with clear error handling on API failures. </constraints> <format> Return the code as an artifact (file per block), then how to get the tracker API token, the fields the modal supports, and how to extend the status mapping. </format>

You are a backend engineer wiring Stripe events into Slack. <context> I need a Stripe-to-Slack notification bot delivered as one self-contained, ready-to-run artifact. It receives Stripe webhooks and posts a clear Slack message for revenue events like new subscriptions, payments, and failed charges. </context> <inputs> - Events to handle: [E.G. checkout.session.completed, invoice.paid, invoice.payment_failed, customer.subscription.deleted] - Notify channel: [#CHANNEL, OR SPLIT WINS VS ISSUES] - Amount formatting: [CURRENCY, WHETHER TO SHOW MRR] - Delivery: [INCOMING WEBHOOK / BOT TOKEN] </inputs> <task> Build an Express server that verifies the Stripe webhook signature with the signing secret, handles the listed event types, and posts a Block Kit message each: new sale/subscription in green with amount, plan, and customer; failed payment in red with the reason and a link to the Stripe dashboard; churn events flagged for follow-up. Include package.json, the raw-body-aware endpoint, the app/webhook setup notes, and .env.example. </task> <constraints> - One runnable project as labeled code blocks; MUST use the raw request body for Stripe signature verification. - Env-only secrets; format currency correctly from the smallest unit; distinct visuals for wins vs problems. - Valid, commented code; return 200 quickly and ignore unhandled event types. </constraints> <format> Return the code as an artifact (file per block), then how to set the Stripe webhook and signing secret, and how to route revenue vs failures to separate channels. </format>

You are an automation engineer connecting Slack to Google Sheets. <context> I need a Google Sheets logger bot delivered as one self-contained, ready-to-run artifact. A slash command appends a structured row to a spreadsheet (e.g. logging expenses, leads, or standups) and confirms in Slack. </context> <inputs> - Command: [E.G. /log] - Columns to capture: [E.G. DATE, PERSON, CATEGORY, AMOUNT, NOTE] - Target sheet: [SPREADSHEET ID + TAB] - Auth: [SERVICE ACCOUNT JSON VIA ENV] - Confirmation: [EPHEMERAL / CHANNEL] </inputs> <task> Build app.js (Bolt): a /log slash command opening a Block Kit modal with a field per column, a view handler that authenticates to the Google Sheets API with a service account and appends the row via spreadsheets.values.append, then confirms with the captured values and a link to the sheet. Include package.json, the Sheets client module, the manifest, and .env.example (service account handling). </task> <constraints> - One runnable Node project as labeled code blocks; isolate Sheets auth/append in one module. - Env-only credentials (service account key from env, not committed); validate/parse numeric fields before appending. - Valid, commented code with error handling if the append fails. </constraints> <format> Return the code as an artifact (file per block), then how to create the service account, share the sheet with it, and change the column set. </format>

You are an integration engineer building a flexible inbound-webhook relay for Slack. <context> I need a generic webhook relay bot delivered as one self-contained, ready-to-run artifact. It accepts inbound JSON from any tool (Zapier, monitoring, custom apps) and turns it into a clean, templated Slack message. </context> <inputs> - Sources to support: [NAMED PAYLOAD SHAPES, E.G. ZAPIER, TYPEFORM, CUSTOM] - Routing: [SOURCE OR PAYLOAD FIELD -> CHANNEL] - Auth: [SHARED SECRET OR HMAC PER SOURCE] - Message templates: [FIELDS TO SHOW PER SOURCE] </inputs> <task> Build an Express server with a single /hook/:source endpoint that authenticates the request (shared secret or HMAC), looks up a per-source template that maps payload fields into a Block Kit message, routes to the configured channel, and posts via the Slack Web API. Provide a clearly editable templates/config module so adding a new source is data, not code. Include package.json, the endpoint, the manifest or webhook notes, and .env.example. </task> <constraints> - One runnable Node project as labeled code blocks; per-source auth verified before processing. - Env-only tokens/secrets; templates and routing in one editable config; safely handle missing payload fields. - Valid, commented code; return clear 2xx/4xx codes. </constraints> <format> Return the code as an artifact (file per block), then how to add a new source (config entry only), the auth model, and an example curl to test it. </format>