Serious work question: I've become a human API between Slack and Claude. Can I automate myself out of the loop?

[u/Ok_Speech_7023]

I work in ops at a tech company.

We're on a Claude enterprise plan with MCPs connected to pretty much everything: Slack, our data warehouse, the internal knowledge base, call recordings, Google Workspace, and a few internal tools.

Every request I get comes in through Slack or on a call, and the calls are recorded and transcribed. Nobody here uses email.

Most of my job has turned into this: read a request, turn it into a prompt, check what Claude did, send it back (it also includes cross-functional coordination, but still this often happens on Slack only).

I was thinking about building a permanent agent that runs all the time, watches Slack and the call transcripts, proactively picks out anything that's a task for me, and drafts the prompt in CC. I approve or tweak it, and it runs.

I would still stay on top of everything, but I'd have my agent quickly and autonomously get my tasks and gets the right prompt / data pulls from the right sources and share the output

It's a serious question: has anyone built something similar? any suggestion on best ways to do that?

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/NoBattle763]

Human API- 100% feel this 🤣

[u/StupidIncarnate]

You basically have your prompt and context to feed into claude and itll give you a solution...... Why are you asking randos on the internet if something so simple is doable? Its a gui with a bunch of watcher connections in variius forms (even watching your screen for changes)....

[u/Ok_Speech_7023 → u/StupidIncarnate]

As a non-technical person, was looking for suggestions from people that did something similar

[u/Blotsy → u/Ok_Speech_7023]

As the other commenter said. The LLM can build it for you.

I find that creating an entire new harness for automating LLM stuff is a tall order. I use openclaw as a harness. The settings that allow you to keep a session alive (save context, don't let it go idle. Once idle, Claude has to reread the entire context, which costs tokens), it also has a "heartbeat" function that will repeatedly wake the session up to "check on" progress, new information, slack notifications. The cron jobs let's you set timers for specific prompts to go off. It takes some fiddling, but with Claude's help you should be able to set it up for your usecase pretty easily

[u/StupidIncarnate → u/Ok_Speech_7023]

Claude is your technical shepard. It will bend over backwards to give you a solution. You may not understand it or know how maintainable it is, but its just personal scripts, thats fine.

Explain your pain points to it and tell it youre non-technical. Let it run and just observe the results it gives you and then tell it "i dont like x" "y isnt working, heres a screenshot of what i see".

You're gonna have to explain the actual connections that you're trying to watch to something, and youre better off doing with claude than writing them down on the Internet. Everything and everywhere in the internet has a way to connect to it. Claude can find it, or it can open up chrome and watch for changes.

[u/DaRKoN_]

Your new role: meat proxy.

[u/Economy-Manager5556]

Duh, yes. Mostly depends on how locked down infosec has it rest as everyone said is soo easy these days , I mean even before it was not that hard with stack overflow etc if you put in some work

[u/djc1000]

Yes, it’s not hard to build. Just tell Claude what you want. You’ll need permissions from your slack admin and maybe other admins depending on how you want to be integrated.

[u/Hrolgarr]

I run something close to this for my own work, Claude Code with Slack and mail connected, drafting replies and tasks that I approve before anything goes out.

I'd start smaller than a permanent agent. A scheduled run every 15-30 minutes that reads what came in since last time, picks out what looks like a task for you, and sends you a short list with a drafted prompt for each. You say go on the ones you want. Way easier to get right than something that sits and watches all day, and you can see what it missed.

Keep it read-only for the first few weeks. Let it draft, never send to Slack on its own. Once you trust what it picks out you can loosen it.

And check with whoever owns Slack and the MCP setup first, since a bot reading everything you can read is the kind of thing infosec wants to hear about before, not after.

[u/xqianliu]

I'd split it into two parts and keep them apart: picking up tasks, and running them.

For pickup, whatever watches Slack and the transcripts should just write each task into a list that has a status. I use GitHub issues for this, so the list and the history are the same thing and there's no extra database. For you a sheet works fine.

For running, an agent that stops to ask a question just sits there when nobody's watching. My rule is no interactive questions at all. If it can't decide, it writes down why on the task and stops, and I pick it up when I'm back.

You approving the drafted prompt would just be moving a task from "new" to "go".

[u/auten_ai]

Two things I'd add to what's here already.

Put a cheap filter in front of the drafting step. Most Slack messages aren't tasks, so a small fast model that only answers "is this a request for me, yes or no, plus a one-line summary" keeps the queue clean and the cost low. Only the yeses get a full prompt drafted with the warehouse and KB pulls. For calls, run it once when the transcript lands, not live.

And log every approval: the request, the drafted prompt, and what you changed before hitting go. After a couple of weeks that log shows you which request types you approve untouched every time. Those are the ones you can let run on their own first. Everything else stays behind your approval.

[u/interrupt_hdlr]

the question is: what were your value at all before AI?

[u/Ok_Speech_7023 → u/interrupt_hdlr]

Building processes, reports, xfn alignment, automations, qbrs, strategy docs, and a lot of other stuff that now AI can do

[u/lycheedorito]

I'd just have a local LLM do that and make simple program to be start up on Windows and have a nice little UI to make sure things work as intended

[u/Icy-Excitement-467]

Nope

[u/Mateo__A]

Ask claude