Not a bug. The booking landed at 3:41am and your workflow sends on trigger. The build (n8n, ~10 min): → Never send on the trigger. Every customer-facing send passes through ONE send-window check first. → Timezone comes from the client config row, never from the server. n8n runs in UTC. Your client doesn't. → Window: 08:00-20:00 local. Outside it → write the message to a queue tab with a send-after timestamp. → One scheduled run every 15 min drains the queue. Anything older than 24h gets dropped, not sent. A reminder for yesterday is worse than no reminder. → Alerts to the OWNER ignore the window. Messages to their customers never do. Queuing instead of delaying is the whole build. A Wait node holding 200 executions overnight is one restart away from firing all of them at once. Same logic behind the 25 free automations + 30 prompts in the Classroom. What time did your last automation actually send? 👇 Deploy, don't study.

Most unpaid invoices aren't disputes. Nobody ever followed up. The build (n8n, ~10 min): → Invoice sent → one row in a Sheet: customer, amount, due date, status → Day 1 past due: one SMS, not an email. "Invoice #204 for the fence repair — link below." An email with a PDF attached gets buried. → Day 7: same message, payment link on its own line. Nothing else. → Day 14: the owner gets pinged to call. An automation should never be the thing asking twice for money. → Paid webhook from the invoicing tool → status flips, sequence stops instantly → Log days-to-payment per customer. That column tells the owner who to ask for a deposit next time. Stopping on the paid webhook is the whole build. One reminder sent after someone already paid undoes a year of goodwill. Same logic behind the 25 free automations + 30 prompts in the Classroom. How long does your client wait to get paid right now? 👇 Deploy, don't study.

One line, no essay needed. Tell me the single repetitive task in your business (or your client's) that eats the most time every week - answering missed calls, chasing quotes, booking reminders, dedupe-ing the CRM, whatever it is. Drop it below in one sentence. I'll reply to EVERY single one with the exact automation from the Vault that kills it + the ~15-min build. First come today, I answer them all. Go 👇

A customer texts a photo of a broken fence at 8pm. The owner sees it Thursday. By then two competitors have already quoted it. The build (n8n, ~15 min): → One intake point: form upload or an SMS/WhatsApp media webhook. Photos never live in someone's camera roll. → Image lands → a vision node returns THREE fixed fields: what the job is, rough scope, and what's missing to price it. → Missing info → auto-reply asking for exactly that. "Can you send a wider shot of the full run?" Never "we'll be in touch." → Enough info → a DRAFT quote built from the client's own price list Sheet. The owner approves in one tap. Never auto-send a price. → Every photo, tag and outcome writes to one Sheet. That's the job history and the pricing feedback loop. Asking for the missing shot is the whole build. A vague photo doesn't need a human — it needs one specific question, sent in 60 seconds instead of three days. Same logic behind the 25 free automations + 30 prompts in the Classroom. How long does your client take to turn a photo into a quote? 👇 Deploy, don't study.