Workbrews Activity Log Tracks Changes

Nobody logs into a deliverability dashboard every morning just to check if things are still fine. They don't — until a campaign underperforms and they go looking for why, days too late. So we shipped Warmy as a node inside Zapier and n8n. Now the checks run on their own, inside the workflows you already have. A few things worth wiring up: – A Slack alert the moment inbox placement drops below your threshold – A daily log of warm-up stats straight to Google Sheets – A new mailbox spun up automatically from a form submission – A seed-list check that runs before every campaign, not after You can create and manage mailboxes, trigger deliverability checks, pull warm-up stats, and work with templates and seed lists — all from your own automation stack. The n8n node is fully self-hostable if you keep infrastructure in-house. Both connect the same way: one Warmy API key, paste it in, done. Deliverability shouldn't depend on you remembering to check 👀

Somewhere, someone is about to Slack you asking for Editor access. Now you get to set the rules before that message shows up. Admin upgrades we just shipped: 🔓 Role request controls (Enterprise): set your own rules for role upgrade requests, or turn them off entirely. 📊 Access Context Studio data via CLI and API: metadata on who's doing what, where the agent’s really working hard, and which topics burn credits is now exportable, straight into your own reporting. Check out the full rundown in the Hex Changelog 👇

A lead-capture workflow was posting to an archived Slack channel for four months. The webhook returned 200 OK the whole time, so nobody noticed — until £700 of missed follow-ups turned up in an audit. Naming a single owner per workflow is the fix that actually sticks.

📦 Package requests that move at the same speed as your team. Workbrew notifies admins the moment a request comes in via email, Slack, or webhook, so nothing stalls waiting to be noticed. ⚡ Instant alerts when a request lands 🔄 No more requests falling through the cracks 🔗 Read the 1.10 release notes: https://buff.ly/XofQQ8W

Your team chat knows everything about your company, and it lives on a server you don't own. Slack and Teams promise they won't train on your data. That promise is one terms update away from gone, and you won't see the email that flips it. So I stopped handing it over. There's a way to run your whole team chat on your own server, and I've started moving all my companies onto it. What do you use, and how much of your data are you giving away?

Asked everyone in my RevOps survey what one thing they'd fix about how their revenue team runs. Best answer I've gotten: "lol a fuckin ticket system that gets filled out the week ahead. Would literally solve so many problems." I laughed because it's true. The most advanced RevOps problem in 2026 is: please stop sending me Slack DMs. Take part (5 min, anonymous): https://lnkd.in/ec2epxX4

The Smart Repository GitHub community website has been refreshed with detailed descriptions of its features. Whether you're evaluating Smart Repository for your organization or exploring its open-source capabilities, the updated site provides a clearer overview of what the platform offers—from intelligent document management and workflow automation to secure sharing, OCR, search, APIs, and much more. Explore the updated website: https://lnkd.in/dqwYfvQ Your feedback, suggestions, and contributions are always welcome!

3 signs your team has a search problem: 1. Someone asks "where's that file?" more than once a day 2. Your Slack has a #file-requests channel 3. Designers keep local backups "just in case" All three fixable. None require more folders.

I started taking notes in my own team's demos so I could Google the tool names afterward. Three weekends on agent orchestration and a doc benchmarking setups. I reviewed every PR line by line again. Reading their code was the last place I felt useful. Then one afternoon a P0 incident arrived. Duplicate refunds on webhook retries. I opened a terminal and started typing a grep, the way I always had. Then I asked who owned the retry path. Michal started to answer. Tomas started at the same time. Both of them stopped and stared at each other in silence. Nobody in that huddle was "wrong". Three agent runs had written that retry seam across two services, and it had never been anyone's. Git blame gave me the runs. It had no name for the person who decided it was going to be this way. "The last time I saw something like this, half our platform came from a vendor," I said. "The code arrived. Nobody owned its inheritance." Awkward silence. Next morning I opened the list of services the team owned. Twelve services. "Put your name next to the service you'd defend alone on-call at night." I wanted to know how much of the code we were allowing agents to put into production we could stand by when shit hits the fan. Four rows came back empty. Every rollback that quarter came out of those four. Three weeks later, a 9 pm alert. Tomas answered before I opened Slack. His first word was "mine." Your team can produce more software than it can carry. Drawing the map of who owns the outcome is the work that stayed human. ---- P.S. If your team ships more than anyone can own, DM me to get a grip.