I build n8n workflows and automations for businesses: lead follow-up, notifications, reporting and the busywork that eats a team’s week. I design for what goes wrong (retries, duplicates, outages), and I’ve tested a library of 12 workflows against a real n8n instance. I’m open to project-based work and full-time automation roles. If you or someone you know needs this, message me or tag them below. Details and contact: https://www.linkedin.com/in/noah-crowley-ab6045286/

Hi everyone! I've been wondering about something and would love your thoughts. When you sell AI voice agents (like AI receptionists) to businesses, do the business owners not worry about privacy? I'm talking about all the details of their calls and the call transcripts being stored somewhere. How do these agencies get around that concern? Do they just... not store the data? Or is there something else going on? Would love to hear answers.

When a send that times out after the destination may have accepted it enters a real workflow, who owns the stop button? The human owner checks the evidence before the consequential step; an uncertain result stops the run. The deliverable is a retry card with stable action ID and last confirmed state. I would make the next decision visible beside it. For a send that times out after the destination may have accepted it, I would reconcile by stable action ID before deciding whether to retry. In a small OpenClaw pilot, I would test self-hosted routing, channel boundaries, and operator-owned recovery and ask a second operator to check the next decision. Who should make the final decision in a send that times out after the destination may have accepted it?

The artifact I want before automation expands: a draft-only message queue with a named sender. In a small Muse pilot, I would test personal-agent preparation with explicit approval before consequential actions and ask a second operator to check a safe recovery path. For a sensitive customer or client message, I would prepare context and wording while leaving the final send to the accountable person. My acceptance check has two parts: 1. Can another person read the evidence? 2. Does the workflow stop safely when the evidence is missing? The deliverable is a draft-only message queue with a named sender. I would make a safe recovery path visible beside it. What would you put on a draft-only message queue with a named sender before letting this run again?

Hi, I’m Noah, from San Diego 👋 I spent the last year building automation and AI agent systems for myself, and I just started posting about it publicly. I’ve built and tested 12 n8n workflows around production patterns like circuit breakers, idempotency keys and retries, not just happy-path demos. I’m here to learn, swap notes and see what everyone is building. If you want to compare approaches on a workflow, say hi. LinkedIn: https://www.linkedin.com/in/noah-crowley-ab6045286/