Tool
Source-linked workflows that name Slack. Part of the AI agent use cases on UsecaseBoard, or browse all use cases.
An n8n agent searches a knowledge base and order history in parallel, uses GPT-4o-mini to classify and draft replies, emails resolvable tickets, and routes billing/refund/security cases to Slack with a draft (~$0.90/mo at 50 tickets/day).
Indie Hackers founder Sean Prentice used Claude Code to build an orchestrator + marketing director + specialist agents (content/ads/research) for his SaaS; outputs land in Slack and nothing posts or spends without his explicit say (~$10/mo self-use).
A creator pattern posts a Grok Bot routine that every 2 hours checks email + Slack, sorts urgent/reply/ignore, and drafts replies in the owner's voice—sending nothing until approval, vs ~$2k/mo for a human VA.
Zapier's updated EA playbook shows stacking Zaps for inbox digests in the exec's voice, CRM-backed pre-meeting briefs, meeting recaps, Slack-reaction tasks, and form-driven travel approvals.
Agenta’s LocalLLaMA post shows self-hosted AI coworkers with per-agent folders—one marketing agent keeps ICP/competitor wiki; another posts a daily Slack report of Reddit threads to join.
NisonCo’s Zapier agent reviews call transcripts, logs commitments in the CRM, pings Slack, and leaves a Gmail follow-up draft—so the rep only hits send.
Official Agents API cookbook: connect Slack threads to persistent agent sessions, workplace tools, and isolated sandboxes so workplace chat becomes a durable agent runtime.
Make’s trigger guide shows how to bootstrap agent scenarios from Slack, Telegram, email, forms, webhooks, or mailhooks, then add tools, knowledge, and instructions—or run on a schedule.
Official n8n AI example: a chat agent answers with GPT-4; if unsure it calls a sub-workflow that asks for the user's email and posts the unanswered question to a Slack support channel.
The example distinguishes waiting reviews, requested re-reviews, and approved changes and prepares reminders containing the work's size and blocking context.
The scenario distinguishes customer-visible changes from internal work and drafts a recurring changelog with links back to the merged pull requests.
The scenario translates a business question into a warehouse query and keeps the query and returned data beside the answer for team verification.
The example groups CSAT and NPS comments into themes and examines how explicit feedback changed around a release or pricing update.
The example gathers promises from calls and email before coordinating the CRM change, handoff document, customer-success notification, kickoff, and welcome draft.
The example reads a linked article, summarizes its claims, and compares the implications with the team's documented plans before saving takeaways.
The scenario searches channels, threads, and attachments to retrieve a remembered artifact and the qualifications that accompanied it.
The published routine summarizes selected channels during an absence, puts direct mentions first, and allows a separately defined urgent escalation path.
The scenario compares attendee availability and local working hours, proposes suitable slots, and books the selected option after confirmation.
The scenario watches connected calls and messages for explicit commitments, adds dated tasks, and reconciles completion and waiting states in a daily review.
The example combines missed conversations and recordings into a prioritized catch-up brief, including decisions and items assigned to the returning user.
Lindy's scenario identifies actionable bugs in an on-call channel, checks existing issues, and attaches new reports to the appropriate ticket.
The example tracks missing receipts, invoice approvals, and unanswered finance queries, then prepares staged reminders and a holdout list for the close owner.
The scenario combines ticket aging, unresolved dependencies, and SLA clocks into a daily escalation watch with draft status updates.
Lindy demonstrates turning a short product-video brief into a script, storyboard, and reviewable draft, with follow-up requests for concrete edits.
The example calculates daily cross-platform ROAS, CPA, and CTR and surfaces campaigns that need review rather than requiring separate platform checks.
The published example updates a deal from a Slack instruction and finds recent customer replies or commitments that have not reached the CRM record.
The example retrieves similar resolved Zendesk tickets to draft a response and uses past resolution context to suggest an owner for unfamiliar problems.
Lindy's published example combines scheduled competitor research with a separate pricing-page change watch and a Slack tracker update.
The workflow analyzes recorded customer calls using chosen communication criteria, logs the feedback, and sends a private coaching summary through Slack.
The assistant asks focused questions about a work issue, explores actions within the user's control, and drafts an escalation summary when the user chooses that path.
The assistant analyzes a chosen deal segment across size, cycle length, and competitive context, then prepares a reviewed brief for Notion and Slack.
The MCP workflow filters accounts by renewal date, assesses engagement and open cases, and records a risk review with recommended follow-up actions.
The agent applies configured lead rules, enriches eligible contacts with Clearbit, and sends a Slack qualification summary with a Gmail draft for review.
The assistant reads existing goals, searches recent work activity for relevant accomplishments, and drafts source-linked progress updates for the goal tracker.
The assistant creates several domain-relevant viewpoints, compares their critiques and alternatives, and records a synthesized decision brief for later review.
The workflow identifies a recruiter's roles in Ashby, checks candidate-stage bottlenecks and stale records, and adds unresolved Slack actions to a prioritized review.
The template retrieves Ashby context, asks eligibility questions, calculates a proposed bonus, checks the supplied policy range, and drafts a Slack approval request.
The agent reads a selected Slack message and organizes its project context into audience, timeline, deliverables, actions, and budget sections.
The skill extracts facts from hiring data, meeting notes, and Slack, drafts the monthly talent narrative, and coordinates reviewer tasks before leadership publication.
The template summarizes Zoom 1:1 transcripts, analyzes chosen communication measures, and tracks coaching feedback over time in a table.
The agent identifies role requests, extracts hiring details, asks for missing information, and confirms the newly created Ashby opening in the original thread.
The agent uses a new BambooHR record to personalize a Slack welcome and calculate calendar check-ins from the employee's start date.
The agent reads Qwoted opportunity emails, compares each request with supplied team profiles, and sends potential expert matches to Slack.
The agent checks the next two weeks of calendar entries, handles configured conflicts, and creates a calendar block containing the planned LinkedIn content.
When a checkmark reaction marks a solved issue, the agent reads the thread, checks existing documentation, and adds a new reference only when needed.
An Ashby-triggered agent resolves the candidate and role and posts a contextual Slack reminder for the interview team's feedback.
The agent searches a structured HR policy table, replies within the Slack thread, and escalates requests that the knowledge base does not resolve.
A Zapier agent checks calendar events for guests and an existing conference link, creates a Zoom meeting when needed, and confirms the update through Slack.
The assistant combines an Ashby scorecard, hiring rubric, and Slack context to examine a stated concern and prepare a reasoned recruiter response.
The MCP template applies a clear-writing checklist to a draft, foregrounds the requested action, and can deliver the approved revision through Slack or Gmail.
The skill reads a pre-filtered Ashby sourcing dashboard, summarizes the current week's activity, and creates a Slack draft scoped to the recruiter's own numbers.
This agent retrieves the latest policies from Box, evaluates an internal request against them, and provides Slack guidance with references to the relevant sections.
The assistant combines Asana status with launch documents to prepare a readiness assessment showing completed work, open items, and blockers.
A connected AI assistant retrieves specified Slack conversations, summarizes decisions and actions, and can prepare replies for review.
This workflow reads product and positioning sources in Notion, then drafts a sales one-pager with benefits, objections, and evidence before sharing it.
The template retrieves selected Slack threads and documents through MCP and saves a searchable, organized knowledge base that an AI assistant can use later.
The template combines Ashby feedback and BrightHire transcripts to identify already-covered topics, unresolved risks, and useful final-round questions in a Google Doc.
An AI assistant applies explicit stage probabilities to Salesforce deals, compares a prior snapshot, and prepares Sheets detail and Slack highlights for review.
The workflow verifies role ownership in the ATS, groups new referrals by recruiter, and posts deduplicated Slack threads for follow-up.
The template gathers role objectives through a chatbot and combines them with company examples to draft a job description, application questions, and interview guide.
Claire Vo moved ChatPRD's Holly Helpdesk to Grok Bot: it sweeps Intercom and email on an hourly routine from a playbook, drafts replies, and sends refund requests as human approval cards that open a single Stripe action—never auto-refunds.
Anthropic's Cowork recipe combines incident-channel messages, alert chronology, logs, and a local template to produce an evidence-linked postmortem and action tracker.
Zapier's purchase-request template matches requested software against an approved Google Sheet, suggests existing alternatives, and escalates genuinely new requests with researched context rather than authorizing purchases.
This Zapier template reads the reacted-to Slack thread, estimates urgency and task duration, finds a weekday opening, and creates a Calendar event containing the original discussion link.
Claire Vo's Zapier template reviews the coming week's Calendar events and sends a Slack summary with meeting details and suggested focus blocks, scheduled for Sunday evening.
Zapier's Career Wins Collector turns an emoji reaction into a contextual summary of a Slack conversation, highlighting the user's contribution and preserving the date and original message link.
Zapier's template reads a week's Google Doc entries, classifies their emotional tone, identifies patterns, proposes a small habit, appends the analysis, and sends a Slack reflection.
An n8n template combines an Ollama agent, three Supabase vector knowledge bases, Postgres memory, request validation, deduplication, and confidence-based escalation across Slack, Gmail, and callbacks.
AGPL self-hostable workspace runs Claude Code, Codex, OpenCode or Pi in isolated sandboxes; hand off from Slack/web/API, attach playbooks/skills/knowledge, approve sensitive actions, and get PRs or files back—positioned as an open Devin alternative.
@GitHub in Slack and Microsoft Teams can now answer across multiple repositories in one thread—open PRs, weekly merges, cross-frontend/backend investigations—plus use shared Slack thread context without copy-paste.
Merlin dispatches team asks from Slack/Linear/GitHub to Claude Code or Codex already signed in on teammates’ machines—reuse local repos, MCP servers, and skills with no extra model API bill; results return in the same thread, with shared skills, schedules, and workspace memory.
OpenAI's SRE example ties an alert webhook to a persistent agent session and Slack thread, investigates bundled telemetry and code-change fixtures, and records rollback decisions without performing deployments.
Morgan DeBaun's tutorial describes daily Gmail categorization and a Slack digest, prioritizing unresolved business messages while leaving sending to the user, plus a Friday review of stalled drafts and follow-ups.
Hasnain Supra combined Gmail, JavaScript, and Groq to turn sales PDFs into a Slack summary and an HTML email report.
The workflow searches a live product API, waits separately for selection and purchase approval, then submits a checkout request and reports the asynchronous order result in Slack.
OpenAI vision extracts receipt totals and currency; deterministic checks compare them with expected booking values and route uncertain or mismatched documents to Slack.
The agent uses Reducto to extract resume information and can connect the parsed profiles with the recruiting team's Ashby and Slack workflow.
Make's Post-Call Hero case study describes a transcript-driven agent that drafts follow-up email, prepares CRM changes, and can create stakeholder Slack channels, supported by fixed context files and a limited tool set.
The agent analyzes multiple Gong transcripts using configured sales frameworks and returns cross-call insights through Slack.
The agent uses product documentation to handle support questions and can convert unresolved customer conversations into Jira issues with configured routing fields.
Gumloop shares a flow based on its expert-vetting process, combining public research, company context, internal usage data, and written requirements before reporting the assessment.
The flow checks imminent calendar meetings and has an agent gather email, CRM, Slack, and attendee research, sending a Slack brief when useful context exists.
This agent first explores the connected data source and records schema context, then answers natural-language questions with structured results and optional visual output.
An AI workflow subtracts travel time to the next meeting from a calendar gap, then recommends a nearby cafe matching preferences or sends a departure reminder.
The workflow reads survey data from Sheets, groups responses by sentiment, analyzes batches with AI, and saves a consolidated thematic report with Slack notification.
An OpenRouter-backed agent reads open Todoist tasks, prioritizes them using configured criteria, and posts a concise plan with overdue-item warnings to Slack.
Gemini drafts a reply using the sender's HubSpot contact, company, deal, and ticket context; the workflow sends through Gmail only after Slack approval.
OCR and Claude identify invoice and payment data; a Slack reviewer approves partial or final payment updates, with receipt records related back to each Notion invoice.
A VLM Run workflow parses emailed resumes, analyzes linked GitHub activity, and records a technical candidate profile with notifications for the recruiting team.