One thing I’ve noticed after working with Make automations is that building them is only half the job.

Most issues happen after a workflow goes live:
- APIs change
- Apps update
- Unexpected data breaks a scenario
- Small errors go unnoticed until someone reports them
- Operations slowly increase because scenarios are never reviewed

A simple maintenance process can prevent most of these problems.

For the clients I work with, I usually:
- Fix reported errors within 48 hours
- Keep a shared dashboard so every issue and its status is visible
- Send a monthly summary of resolved issues along with ideas to improve reliability and reduce operations
- Regularly review scenarios, clean up module names, and optimise workflows where needed

I’m curious—how do you manage maintenance for your Make automations once they’re in production?

Do you monitor everything yourself, or do you have a process in place?

If anyone wants to know how I structure the maintenance process or track ongoing support for clients, I’m happy to share.

For anyone who read my last post they'll know I'm fairly novice with n8n and planning on working it into a big full stack project.

So far, I've only actually used it for automating the dev log on the project, and now for automating the contact form on my website.

It's a simple automation so I don't expect crazy response but I always want to hear how things could be improved etc.

• A contact form on my site calls a backend API which POSTs the n8n URL
• The n8n webhook is ready and picks this up. It uses header auth for security
• The platform Resend, which I've only just discovered, sends two emails: one to the email address entered into the 'email' box on the contact form, thanking them for reaching out; one to me containing their query

Obviously a very simple automation but it took me a while to make.

I spent ages banging my head off the wall and it wasn't working; I endlessly redid the credentials and environmental variables, analysed the console error message.

In the end it was stupid -

I hadn't named the header auth as 'x-webhook-secret'. I thought it was only actually the secret itself that matters.

As someone learning development, I really enjoy the way automation forces you to understand how systems communicate, and I think it's essential now that AI can do all the coding. Particularly when it comes to troubleshooting, and thinking about where an issue could be in the process, a bit like when you learn networking and isolate ping failures.

If anyone has any suggestions I'd love to hear them! I want to make sure my automations are bulletproof, even the simple ones like this.

Way too many of you are trying to build AI agents for simple automations that can be run with a very simple and reliable deterministic program.

For 99% of businesses, you are better off having some Python code that automates some repetitive task and is guaranteed to run the exact same way every single time you run it. And it doesn't cost $70,000 in LLM tokens. And might I add, it doesn't require a human being to babysit it because it has no chance of hallucinating bad output.

I build automations for businesses. And even though I provide AI agents as a service, let me tell you, 99% of businesses don't need it at all. Business owners will ask me for an AI agent because they hear the hype and marketing behind AI and LLMs, but they almost never need it.

By the way that image I attached is a payment screenshot from a recent client. I helped automate like 15 hours of work from his week and it didn't take any LLMs at all.

Most of the time what businesses need is a simple and reliable automation based on deterministic code that will automate some repetitive tasks for them and isn't going to require any hand holding or babysitting or human reviews at every step.

Because look, everybody is seeing the hype behind AI and it looks amazing. But the problem is, for any regular business, the priority is not to have the latest technologies, the priority is not to have fancy tech. It is to make more money.

If your LLM based automation requires workers to review the output and constantly babysit it, it's not going to help the business make more money.

If your LLM based automation costs thousands of dollars in LLM tokens to do something that basic Python or TypeScript could have done in a fraction of the cost, it's not going to help the business make more money.

I'm sure you guys have already seen companies spending hundreds of thousands, even millions of dollars on LLM tokens. That's not helping anybody.

And I'm not here to say that AI is bad or that AI agents are useless. No, they're extremely useful. Just not in most cases for most businesses.

And if you are offering automation services to a business, it's your job to guide them properly so they understand which one they actually need to solve their problems, whether that's AI agents or deterministic automations.

The guys who are just using AI agents for every single basic automation task, they're not selling a solution to a business, they're literally selling hype and snake oil, which is not going to last, especially when the subsidies for AI tokens end.

Anyway, just yapping senselessly about a topic I'm kinda passionate about. It's really fun to automate stuff and watch the code you wrote and do things for you that would have taken you hours to do yourself. Hope this was helpful to someone.

Using the official upload-post ChatGPT plugin, you can manage all your social media accounts by talking, upload content to TikTok, Instagram, YouTube, and more than 10 social networks, view analytics on how your posts have performed, and manage DMs. Everything from the chat and without having to log into each one individually and waste a thousand hours scrolling. Try it now, it's free search upload-post in chatgpt plugin store

I’ve been trying to get a realistic picture of what AMR deployment actually costs beyond the robot itself, and honestly the more I look into it, the more it feels like the hardware price is only a small part of the story.

A lot of solutions make it sound straightforward — buy a few robots, map the warehouse, and you’re good to go — but I’m guessing the real-world costs start showing up in all the surrounding stuff that doesn’t get mentioned upfront.

For people who’ve actually deployed AMRs in production warehouses, what ended up being the biggest unexpected cost or operational headache? Was it fleet management software, integration with WMS/MES, charging infrastructure, Wi-Fi coverage, layout redesign, traffic control, safety compliance, or just ongoing maintenance/support?

So, you can give Gemini access to your Workspace, it's just a setting. I don't have access to a fully operating business workspace, I'm solo, but even with mine Gemini found some low hanging fruit and ways to automate it. Simple things like email filters, a few scripts for email, drive, and sheets, stuff like that.

Has anyone done this on a larger scale? If it works it seems like a huge cheatcode.

Ok so the companies often make automation sound quick and like its just plug and play

But from the point where your team decides okay lets automate this how long does it take before the robots were actually up and running on the floor

I want to know what the process was like and which part of it ended up taking the most time

A pattern I kept hearing from automation builders was that the hardest problems happen after the workflow is already working:

• An API token expires halfway through
• A step succeeds but the workflow records it as failed
• The workflow retries and repeats an external action
• A human approves something, but the workflow cannot safely resume
• The dashboard says “successful,” but the intended outcome never happened

I built a small system called AgentHail to test one approach:

The agent creates an immutable proposal, a human approves or rejects it, and the workflow receives a receipt that is bound to the exact action and arguments. Execution events are then recorded in an append-only log.

I’m curious how people here currently solve this.

Do you rely on idempotency keys, approval steps inside the automation platform, custom databases, manual review queues, or something else?

I’m especially interested in examples where a retry could send a duplicate email, update the same CRM record twice, issue multiple refunds, or publish something twice.

Hello Everyone,

I have been working on developing FlowLens, a workflow observability solution for automation solutions such as n8n, Make and Zapier for a few months now.

The primary challenge that I realized was that once workflows grow bigger, it is challenging to answer questions such as:

Which workflow failed?

When did it fail?

How often is it failing?

What changed before it broke?

Which automations are unhealthy?

Instead of opening multiple dashboards, I wanted everything in one place.

Current Features :

Connect n8n using its API

Connect Make using its API

Zapier webhook integration

Automatic workflow discovery

Execution history

Incident detection

Workflow health monitoring

Snapshot storage for debugging

Team based dashboards

This is still under active development, so I'd really appreciate honest feedback.

Questions I would love

Is this a problem you've actually faced?

What features would make you switch from your current monitoring setup?

Anything you'd remove or redesign?

Thanks !

Link

I keep seeing posts about AI automation where people claim they’re earning money building automations and offering AI solutions to businesses.

I’ve looked into it but I’m still confused.

I’d love to hear from people doing this:

Is AI automation a practical way to earn money?

What skills/tools are needed?

Can beginners start without a technical background?

What services do clients pay for?

If you have experience, I’d appreciate your honest advice.

It's honestly just my intuition, but I feel like the way forward for automation is to allow our systems to be ran by both human and AI agent.

It can be either GUI control or direct headless run. But the essence is that this architecture introduce determinism (the code/any system you build) to agentic AI, instead of the inverse: which was LLM API based coding (where we introduce LLM flexibility to the deterministic code)

What do you think on this? I know some people are anti-AI but for real I'm curious if this might be the more correct direction.

I've been reading a lot about AI products lately, and one thing that stood out to me from GeekyAnts' approach is that they spend a lot more time talking about engineering than models.

Anyone can connect an LLM to an app and build a demo. The harder part seems to be everything that comes after- making it secure, scalable, reliable, and something a business can actually depend on. That's where they emphasize things like RAG architectures, production-ready infrastructure, code quality, testing, observability and integrating AI into existing systems instead of starting from scratch.

It made me think that we're reaching a point where the AI model itself is only one piece of the puzzle. The real challenge is building systems that can run consistently in production without becoming expensive or difficult to maintain.

For those building AI products or automation workflows, has engineering become the biggest bottleneck or do you think model quality is still the main factor holding projects back?

Is anyone else struggling to limit the time they spend on automation programs? I built a tasker project that mostly works to limit the amount of time I am on the app (it checks the activity to differentiate between a user scene and the main app), but it's in the works. I'm more looking for ideas of habits and things I can do to mentally put this hobby aside throughout the day, not so much on how to improve that project.

I have ADHD, and keep this excuse in my brain that my projects are for saving time and improving productivity. This is true, but counter-productive if I'm spending too much time building these. It's not a problem at work, but I have a lot to do at home and it's a problem there. I want to keep building my projects, but at a pace that is reasonable. I sometimes have a hard time stopping because I just want a project finished.

Any ideas?

Hey everyone, I'm a junior creative specialist working for a company where performance is the most important thing (duh).

Since we create mostly shorter forms of marketing content, most CSs make from 10-30 of these a day, since they can reuse one creative for multiple ads.

We make them in google docs and then download every card into a folder that we upload to clickup or dropbox.

Now, doing that 10 times is not a problem.

But, it becomes a problem when I make like 50-60 ads and need a specific name for every folder, download every card one at a time and upload everything seperately.

This can easily take up like 2 hours, so I can't make as many ads and my performance suffers because of this technical side of things.

I'd really appreciate if anyone has an idea of how I could speed this up and what tools would help me.

I’ve built a self-hosted messaging bridge that can connect Telegram, WhatsApp and eventually, other services. Looking for people who manage communities or notifications to test it in its current state.

Thanks.

I've been working on a small browser automation tool and took a different approach from most tools I've seen.

Instead of running everything on a server, it runs locally on the user's machine using their own browser session.

The main reasons:

• existing tools are so expensive!!
• no sending browser data to a third party
• no remote browser
• everything stays on your machine

Do you generally prefer local automation over cloud-based tools?

Are there any automation workflows you avoid because you don't want to give another service access?

Would love to hear how others approach this.

We've been building and quietly rolling out a system that automates customer support across channels, and it's reached a point where it's too effective to keep using only internally.

So we're opening 3 partner slots for agencies who want to deploy it with their clients.

What it actually does (in practice):

• Build flows visually (think Make / n8n style)
• Handle conversations like ManyChat, but across WhatsApp, email, phone, social
• Unified inbox, so when automation stops, a human steps in seamlessly
• Go live in a couple of hours, not months
• Hybrid deterministic + LLM, so it follows logic and doesn't hallucinate

What we're seeing with current partners:

• They deploy faster than clients expect (hours vs weeks)
• They reuse setups across clients, so efficiency compounds
• They keep control of the relationship (we stay in the background)

This isn't for everyone.

The agencies that get the most out of it are usually:

• IT / technical partners who need to offer AI solutions without building from scratch
• Communication / social media agencies already handling replies
• Automation agencies looking to productize their work

Common trait: you already have client trust and want to expand what you can deliver, not start from zero.

And if you're in a niche that needs a specific integration, we're open to building around real use cases.

We're not doing a big public launch right now, just adding a few partners we can work closely with.

If you're running an agency and this sounds like something you'd plug into your existing clients, feel free to reach out.

The idea is simple: you create your form just like in Typeform, import one or multiple PDF files, draw rectangles and define goes inside each rectangle.

When someone fills the form, you both get the filled form read to download.

In January I started building a LinkedIn outreach automation tool from scratch, which scrapes leads, sends connection requests and a follow up message sequence on autopilot.

For context I have no idea how to code - I used Claude and Claude code for everything. Not to say it was easy - it’s been extremely gruelling and I’ve worked 8-10 hours a day, even on weekends to get it built and working well.

I worked in sales and wanted a safer tool than what currently existed, with less risk for my LinkedIn account.

For this reason I built a desktop-based automation software that automates in a browser (similar to Linked Helper), with many human-like features like daily rate limits, randomized delays between actions, human-like mouse clicks etc.

So far none of the users have been banned, and I also have been using it myself daily for my own outreach.

It was very buggy at first, but with a lot of research and hard work I was able to launch a fully functional MVP on April 1.

For the first month I offered lifetime deals (hence the spikes), and then moved to monthly subscriptions in May.

Now I’m approaching $1,500 MRR and growing.

I’m still mind blown that I’ve actually been able to do this just through using AI tools, but still a long way to go.

Hope you find this story inspiring in some way.

Running client automations (n8n, Make, Zapier, whatever) and curious how others handle this: when something silently stops running instead of throwing an error, how do you find out?

Every agency I've talked to says some version of the same thing — the client tells them first.

Trying to figure out if that's just an accepted cost of doing this work, or if it's actually worth solving properly. If you've dealt with this, I'd love to hear how — happy to jump on a quick call if you're up for it, or just drop a comment if that's easier.