About

What automatelab is

A working notebook for people who automate things at work. We publish specific how-tos, troubleshooting guides, and honest comparisons across the tools we actually use - n8n, Make, Zapier, Cursor, Claude Code, MCP, and the long tail of AI agent frameworks that show up in production every quarter.

The bar we hold ourselves to: every post answers a question someone typed into Google or pasted into Claude. No “in today’s fast-paced world” intros, no listicles built from press releases, no “10 game-changing tools” ranked by affiliate payout.

What we cover

No-code and low-code automation (Zapier, Make, n8n, Power Automate), agent frameworks (LangChain, CrewAI, custom MCP servers), AI coding tools (Cursor, Claude Code, Copilot, Aider), and the RPA platforms still keeping the lights on at most enterprises (UiPath, Automation Anywhere). We write about integrations between specific named tools, not “the future of work.”

What we don’t cover

Funding rounds. Predictions. CEO interviews. Anything that’s still under NDA. If a vendor pays us to write about them, we’ll say so on the post - we haven’t yet.

How we write

Every article is written or reviewed by someone who has actually run the workflow described. We cite primary sources - vendor docs, GitHub issues, official changelogs - on the noun phrase that names them. We use real version numbers and real error messages. When a piece references a price, the price links to the vendor’s pricing page; when it references behavior, the behavior was reproduced on a live account. If we get something wrong, we mark the correction inline with a date and what changed.

External links are nofollow by default. We don’t sell links, sponsored placements, or “expert quotes” in posts.

Bylines

All posts are published under AutomateLab Editorial. We don’t run individual bylines on posts - the editorial standards above are consistent across the site, and a single byline is easier to hold to that standard than a roster of guest names.

Who runs it

automatelab is edited by Artyom Rabzonov. Tips, corrections, and pitches: editor@automatelab.tech.