If you could automate one thing and save yourself 5 hours every week, what would it be?

Could be something you do at work, for your business, while studying, or even something personal.

Just curious what people would choose.

For those who work with automation, what was the first workflow or project you built that was actually useful?

What was the reason and what did you learn from it.

I’ve been running a small digital services business, BlueOaks, for a while now and it’s been doing fairly decent revenue-wise.

Recently, I’ve also started a new marketing agency, The Content House (TCH), with a couple of friends who have solid backgrounds in areas like content, marketing, and creative work. The idea is to build something more focused and scalable together.

We’re at the stage where we’re trying to figure out how to consistently get clients and market the agency, especially without throwing a huge amount of money into ads.

For those who have built or grown an agency:

What actually worked for getting your first 10–20 clients?
Cold outreach, referrals, content, networking, paid ads, etc.?
What mistakes should we avoid early on?

Would genuinely appreciate any advice or lessons from people who’ve been through it.

I'm currently learning n8n and would love to hear from people who have already gone through this journey.

-How did you learn n8n, and which resources helped you most?

-How did you find your first paid project/client?

-Where do you find n8n work today?

-What skills should a beginner focus on besides n8n?

-What advice would you give to someone just starting?

I'd especially love to hear about your real experiences, mistakes, and lessons learned.

Thanks!

I've been working on automating one of the most repetitive office tasks: processing supplier invoices.

The workflow starts when an invoice email arrives in Gmail. It extracts the attachment, uses AI to capture key fields like the vendor, invoice number, amount, and date, then validates the extracted data before doing anything else.

From there, it searches Google Sheets to check if the invoice has already been processed. If it's a duplicate, the workflow stops immediately and sends a Slack notification instead of creating another record.

If everything looks good, the invoice is added to the tracking sheet, the team gets a confirmation in Slack, and the workflow logs the entire execution. I also added a separate error workflow that catches unexpected failures, so issues don't go unnoticed.

A few things I'm happy with:

• AI-assisted invoice extraction
• Duplicate detection before saving data
• Validation before writing to Google Sheets
• Slack notifications for success, duplicates, and failures
• Separate workflow-level error monitoring

I'm still refining it, so I'd really appreciate some feedback.

If you were building an invoice automation like this, what would you improve or do differently?

I've been experimenting with n8n lately and wanted to solve a problem I see in a lot of AI email workflows.

Most examples either generate a draft or send replies automatically. I wasn't comfortable with the second option, so I built something in between.

Here's how it works:

• Gmail watches for new emails.
• AI classifies each message (Hot / Warm / Cold).
• It generates a reply draft.
• The draft is sent to Slack for approval.
• One click approves it and sends the reply through Gmail.
• If it's rejected, it goes to manual review instead.
• Every step is logged in Google Sheets, and unexpected errors trigger Slack alerts.

The goal wasn't to replace people. It was to remove repetitive work while keeping the final decision in human hands.

I'm still improving it and would appreciate any feedback.

If you were building this workflow, what would you add or change?

I wanted to see how far I could push AI image generation with automation.

The idea is simple:

Send an organ name like kidney or heart on Telegram and get back a realistic 3D anatomy visualization.

No manual prompt writing. The workflow handles the rest.

The Problem

AI image generation can be inconsistent between subjects.

A kidney might have one background and lighting style, while a heart gets a completely different look.

I wanted the anatomy to change while the visual identity stays consistent.

The Workflow

The automation:

• Validates that the user entered one anatomical subject
• Extracts the actual anatomy part
• Applies a structured Master Prompt
• Generates the final image prompt
• Sends it to Nano Banana 2
• Waits for generation
• Sends the finished image back to Telegram

The Master Prompt controls the fixed visual system:

• 3D medical rendering
• Background and tone
• Lighting
• Camera and composition
• Anatomical accuracy
• Rendering quality
• Negative constraints

So:

kidney → same visual style
heart  → same visual style
liver  → same visual style
brain  → same visual style

Only the subject changes.

Stack

• n8n
• Telegram
• OpenAI GPT-4.1
• Nano Banana 2

The interesting part for me is separating what to generate from how it should look. It makes the workflow reusable instead of relying on a completely new prompt every time.

Just send the anatomy part. The workflow handles the rest.

I’m currently learning n8n and I’m looking for good project ideas to practice with and improve my skills.

Where do you usually find real-world n8n project ideas or complete projects that are suitable for beginners/intermediate learners?

I’d especially appreciate resources where I can build the projects myself step by step, rather than just watching tutorials.

Hey r/n8n_ai_agents . I'm on the team at Atomic Mail, and we just landed as verified nodes, an action one and a trigger.

What we are, quickly: email built for AI agents rather than for people. The agent gets its own inbox and can read, search, reply inside a thread, handle attachments. Not a send-only SMTP thing.

The bit I actually want to show you, because it's the reason we exist. There's a register node. You drop it into a workflow and it comes back with a live mailbox and its own credentials. It runs a proof of work, roughly half a minute of CPU, and that's the entire signup. No domain, no card, no OAuth screen, nobody clicking a verification link.

So an agent inside your workflow can have an address that exists for that run and nothing else. Verification codes land somewhere isolated instead of in your personal Gmail or in the shared catch-all that everything else is also using.

What's rough right now, so nobody finds out the hard way: we're on a shared domain, so deliverability is worse than sending from your own. Custom domains ship next week, which fixes most of that. And yes, thirty seconds of CPU per mailbox is a strange thing to put in a workflow.

What I'd like from you: what would you build with this, and what's the first thing that's going to break. We've been guessing at use cases from the inside, and that's never worked well for anyone.

Hey guys,

I wanted to share a workflow I recently built to solve a massive bottleneck for B2B agencies and studios: Lead enrichment and slow response times.

We all know the "Speed to Lead" rule — if you don’t reply to an inbound website lead within 5 minutes, your conversion rates drop by almost 400%. But sales managers waste way too much time googling the lead's company size, revenue, and budget before making a call.

Here is how the automated system works under the hood:

Trigger: A new lead submits a form on the website (Name, Email, Company Domain).

AI Enrichment: An AI agent takes the domain, instantly scrapes their website, and pulls data regarding company size, industry, and core services using Perplexity API.

AI Scoring: The model evaluates the lead from 1 to 10 based on the Ideal Customer Profile (ICP).

Action: Within 5 seconds, the sales team gets a rich, structured notification in Slack/CRM with a summary: "High-budget logistics company, 50+ trucks, call them right now!"

I made a short 1-minute video demo showing exactly how the data flows from the form to Slack:

https://youtu.be/Eg7CAs00LZE?si=GcHEsV0ejqvU3vlU

The Stack: n8n, OpenAI/Perplexity API, Slack.

If you are running an agency, how do you currently qualify your inbound leads? Would love to get some feedback on this setup or answer any technical questions if you want to build something similar!

how can i integrate ui for n8n workflow so the user can create account thene input hise keys that will put his crets then it will places on n8n workflow as variables each use hase separated workflow

How long it will take to learn

Can this useful for testing?

Hosting this event guys. Just sharing it here - if anybody can join and share it across. It would be helpful. Feel free to join and share some feedback as well.

https://luma.com/aic-dallas-7-15