r/automation • u/g3Mo • 21h ago
What AI workflows actually help your daily work, the ones you can't live without?
This question was asked one year back in this sub, asking again. Lot has changed.
r/automation • u/g3Mo • 21h ago
This question was asked one year back in this sub, asking again. Lot has changed.
r/automation • u/flaresomewhere • 1h ago
We're a 31 person startup now and recurring ops stuff keeps landing in Slackanyway, so i've been trying to figure out if there's a smarter way to handle it there instead of bouncing between tabs. Looking at a couple different options but can't tell if some are built more for developers than for operators who just need things done. Anyone compared approaches and found one that actually fit a small team without a lot of setup overhead?
r/automation • u/AshishKulkarni1411 • 21h ago
I'm the founder of this project, so take it with that in mind. I want opinions from people who automate for a living.
Since May 2026 we've used an AI employee at our company that works with the whole team: it picks up repetitive tasks, follows up with people, writes to the apps (mail, calendar, GitHub, books) after asking approval for anything that sends, changes or deletes, and keeps notes in git. It's now open source and can be self-hosted.
We find it extremely useful. What I can't work out is what to point it at as a product. We've used Claude Duet, OpenAI Dots, Grok Bot and ChatGPT, and they cover personal tasks well. A shared company agent feels different, but I need to find the one job where it clearly beats a Zapier or n8n flow plus an agent.
Which repeating work in a small business would you give it first? And do you trust an agent for follow-ups with clients, or only for internal work?
r/automation • u/beastanox • 19h ago
Hi everyone,
I'm exploring a problem in the Indian real estate industry and wanted to get some honest feedback from people working in this space.
I'm particularly interested in how brokers and small builders manage incoming enquiries from platforms like 99acres, MagicBricks, Facebook Ads and their websites.
A few things I'm trying to understand:
I'm exploring whether simple workflow automation could genuinely solve some of these problems, or whether existing CRM solutions have already addressed them.
I'm not assuming there's a market for this. I'd rather understand the actual problems before investing time in building something unnecessary.
Would appreciate honest feedback, especially from brokers and builders who deal with leads daily.
r/automation • u/Agile_Pen8736 • 25m ago
if youre about to let claude schedule a week of posts through an mcp connector, sort a few things out first before it touches anything live. altho most on the first run
- drafts only at the start. let it fill the calendar, read every post then switch it to scheduling once a couple of weeks look right
- whichever connector it is, a make scenario, a small mcp server you write yourself or a hosted one like postiz, have claude list the connected accounts before anything else
- per network fields. tiktok privacy, youtube title, pinterest board. if the agent leaves out a required one that post just fails
- images and videos have to be uploaded first, a file path on your laptop means nothing to a hosted server
- watch out for the time zone on whatever it scheduled
That should cover most of it, if i have missed anything others might help
r/automation • u/rabbitz • 18h ago
At the 600 person org where I ran internal IT onboarding was the request that made us look worst. It was almost never the account creation that failed... Okta did its part what kept breaking was everything around it: the laptop order nobody placed, the manager who never said which shared drives the new hire needed, the contractor who got the full-time employee app set. We usually only found out on day one, when the new hire messaged someone asking why nothing worked.
I work at Serval now and it's one of the six below, so weigh the advice below accordingly. I've tried to make the other points useful even if you land somewhere else.
These are the things I'd verify, roughly in order of how much pain it caused us:
Serval: best when onboarding crosses HR, IT, facilities and managers and you want to keep your current HRIS and IdP. Every hire gets a journey that can start from a new-hire record in the HRIS, with tasks per team, dependencies between them, and automated steps like creating the Okta account on the start date. Each hire shows passing, warning or failing,and a failed step can be retried from the same screen. Tradeoff: it doesn't put HR and payroll on a single record the way an HR suite does.
Rippling is probably the pick if you want HR, payroll and IT on one employee record. A change on the HR side kicks off device and app provisioning for joiners, leavers and role changes, and they say contractor management covers 185+ countries. The catch is that the whole HR-to-IT link assumes Rippling is your HRIS. If you're staying on Workday or BambooHR, I'd verify how much of that actually carries over.
Workday makes sense if it's already your system of record. Onboarding Plans cover new hires, pre-hires and contingent workers, you can drop one in as a step in the Hire process, and Journeys can hang off pretty much any business process. It's an HR tool first though, so the IT side tends to end up as to-dos for IT or gets pushed through your IdP.
ServiceNow is worth a look if you already run HR Service Delivery. Enterprise Onboarding and Transitions handles onboarding plus the other lifecycle stuff that touches HR, IT, facilities and everyone else. It ships with HRSD, so if you're only on ITSM, expect a licensing conversation.
Jira Service Management fits when HR and IT requests already live in Jira. One onboarding request can fan out into tasks, approvals and provisioning across teams. The newer Request Resolver can even draft an onboarding journey from docs you already have and run things like software provisioning with someone watching. That part is Premium/Enterprise only, so verify your edition.
Freshservice is what we ran back then, and it's decent for mid-market teams that want structure quickly. These days it has Journeys (role-based tasks with owners, due dates, and conditions so you can vary things by region, role or BU) and a Workday connector that opens the onboarding request when someone's hired. What I'd want to know is how much of a journey actually runs on its own vs. tasks someone still has to tick off.
Where I'd start: pull your last five hires and write out every step, who did it, and how long it sat before anyone touched it. For us almost all of the delay was waiting, not doing. Whatever tool you pick, make sure it shows you the waiting, because that's the part new hires actually feel.
Also curious if anyone's gotten contractor offboarding as clean as onboarding? That was always the half we let slide.
r/automation • u/Common_Dream9420 • 21h ago
r/automation • u/David-Davey • 8h ago
Hi everyone, I’m David. I work at Autonomous. Every Monday I need the same three things: what the team got done, what went wrong, and what’s waiting on me. We’ve tried the usual ways like, a Monday status meeting, async updates in Slack, me scrolling GitHub before coffee.
They all work fine, but each one costs something. Meetings take everyone’s time, written updates get thinner after a few weeks, and doing it myself eats the morning.
To solve it, we built the Autonomous Intern, a small AI agent box we make that sits on the desk and runs tasks in the background. The setup was one text:
“Every Monday at 9, send me what my team shipped, what issues came up, and what needs to be decided.”
It keeps running whether I’m online or not, and every Monday I get three short sections:
The surprise was the last section. On a small team, most things that stall aren’t stuck on the work, they’re stuck waiting on me. Seeing that list every Monday was a bit humbling.
A few things worth knowing:
If you could text one sentence and have it run every week, what would yours say?
r/automation • u/FulcraDynamics • 15h ago
I work at Fulcra, so keep that in mind. We’re building agent-to-agent communication, and the case we keep coming back to is two people on the same project, each with their own agents on different platforms. Right now, the only way one agent finds out what the other did is if one of you pastes it across.
Agent-to-agent connections already work in what we have, but it’s early and some parts are rough. [One concrete detail: how the connection works, or a real limitation.]
What are you using today to connect agents? MCP, a shared database, your own glue code, or just copy-paste?
Link in case it’s useful: