<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Hourbench Blog</title>
    <link>https://hourbench.tech/blog.html</link>
    <description>Short, checkable notes on AI and no-code automation for small businesses.</description>
    <language>en</language>
    <lastBuildDate>Sun, 08 Nov 2026 09:00:00 +0000</lastBuildDate>
    <item>
      <title>Client onboarding as a chain, not a checklist</title>
      <link>https://hourbench.tech/blog-kunden-onboarding-als-kette-statt-checkliste.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-kunden-onboarding-als-kette-statt-checkliste.html</guid>
      <pubDate>Sun, 08 Nov 2026 09:00:00 +0000</pubDate>
      <description>Workflow 02.05 sends four onboarding emails without anyone having to remember them. Reading the file shows where it waits for a client&#x27;s answer: nowhere. Here is where that wait belongs.</description>
    </item>
    <item>
      <title>Update n8n now: two security fixes matter to self-hosters</title>
      <link>https://hourbench.tech/blog-n8n-sicherheitsupdate-oktober-2026.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-n8n-sicherheitsupdate-oktober-2026.html</guid>
      <pubDate>Sun, 01 Nov 2026 09:00:00 +0000</pubDate>
      <description>n8n has disclosed two high-severity vulnerabilities. Self-hosters should update and check two node types now.</description>
    </item>
    <item>
      <title>Follow up without becoming a nuisance: the stop condition is the core</title>
      <link>https://hourbench.tech/blog-nachfassen-ohne-zu-nerven-abbruchbedingung.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-nachfassen-ohne-zu-nerven-abbruchbedingung.html</guid>
      <pubDate>Thu, 22 Oct 2026 09:00:00 +0000</pubDate>
      <description>Workflow 02.04 sends a sequence of follow-up emails. Its useful lesson sits before the writing step: who is excluded, who merely waits, and why a reply does not yet stop the file as shipped.</description>
    </item>
    <item>
      <title>A website form into the CRM, without duplicate entries</title>
      <link>https://hourbench.tech/blog-website-formular-ins-crm-ohne-doppeleintraege.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-website-formular-ins-crm-ohne-doppeleintraege.html</guid>
      <pubDate>Thu, 15 Oct 2026 09:00:00 +0000</pubDate>
      <description>Workflow 02.03 validates a form, enriches the enquiry and writes it to a lead sheet. But a repeated submission reveals a missing decision before the append step.</description>
    </item>
    <item>
      <title>OpenAI is retiring GPT-4o mini: check your n8n workflows now</title>
      <link>https://hourbench.tech/blog-openai-kuendigt-gpt-4o-mini-ab.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-openai-kuendigt-gpt-4o-mini-ab.html</guid>
      <pubDate>Wed, 14 Oct 2026 09:00:00 +0000</pubDate>
      <description>OpenAI will remove GPT-4o mini from the API on 14 January 2027. The Automation Vault uses that model, so its workflows need a controlled migration.</description>
    </item>
    <item>
      <title>Make raises Core, Pro and Teams prices</title>
      <link>https://hourbench.tech/blog-make-preise-oktober-2026.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-make-preise-oktober-2026.html</guid>
      <pubDate>Mon, 12 Oct 2026 09:00:00 +0000</pubDate>
      <description>Make&#x27;s monthly prices for 10,000 credits have risen. Existing users should check their billing cycle before the next renewal.</description>
    </item>
    <item>
      <title>Make restores Core, Pro and Teams pricing</title>
      <link>https://hourbench.tech/blog-make-preise-core-pro-teams-zurueck.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-make-preise-core-pro-teams-zurueck.html</guid>
      <pubDate>Thu, 08 Oct 2026 09:00:00 +0000</pubDate>
      <description>Make&#x27;s public price table changed overnight. The named tiers are back, and the entry volume shown for Core has doubled.</description>
    </item>
    <item>
      <title>Make replaces Core with one paid plan</title>
      <link>https://hourbench.tech/blog-make-ersetzt-core-durch-make-plan.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-make-ersetzt-core-durch-make-plan.html</guid>
      <pubDate>Wed, 07 Oct 2026 09:00:00 +0000</pubDate>
      <description>Make now lists one paid plan at $9 per month for 5,000 credits. Core, Pro and Teams have disappeared from the public pricing table.</description>
    </item>
    <item>
      <title>Make raises the Core entry price</title>
      <link>https://hourbench.tech/blog-make-core-preis-steigt.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-make-core-preis-steigt.html</guid>
      <pubDate>Fri, 02 Oct 2026 09:00:00 +0000</pubDate>
      <description>Make now lists Core at $12 per month for 10,000 credits on monthly billing, up from $9. Check the amount before renewing or switching plans.</description>
    </item>
    <item>
      <title>Update n8n now: security fixes released for 1.x and 2.x</title>
      <link>https://hourbench.tech/blog-n8n-sicherheitsupdate-september-2026.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-n8n-sicherheitsupdate-september-2026.html</guid>
      <pubDate>Thu, 01 Oct 2026 09:00:00 +0000</pubDate>
      <description>n8n published a batch of new security advisories. Self-hosters should move to a patched release now, especially when instances have several users or public triggers.</description>
    </item>
    <item>
      <title>Zapier cuts the Professional entry price</title>
      <link>https://hourbench.tech/blog-zapier-professional-preis-sinkt.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-zapier-professional-preis-sinkt.html</guid>
      <pubDate>Sat, 26 Sep 2026 09:00:00 +0000</pubDate>
      <description>Zapier now lists Professional at $19 per month on annual billing instead of $19.99. Existing plans should be checked before the next renewal.</description>
    </item>
    <item>
      <title>Lead scoring: which points count and which only look useful</title>
      <link>https://hourbench.tech/blog-lead-bewertung-welche-punkte-zaehlen.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-lead-bewertung-welche-punkte-zaehlen.html</guid>
      <pubDate>Fri, 25 Sep 2026 09:00:00 +0000</pubDate>
      <description>Workflow 02.02 scores an enquiry from four signals. The arithmetic is clear. The difficult part is knowing when a neat score describes the email rather than the opportunity.</description>
    </item>
    <item>
      <title>n8n security update: shared instances should upgrade now</title>
      <link>https://hourbench.tech/blog-n8n-zugangsdaten-sicherheitsupdate.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-n8n-zugangsdaten-sicherheitsupdate.html</guid>
      <pubDate>Tue, 22 Sep 2026 09:00:00 +0000</pubDate>
      <description>A high-severity flaw could let an ordinary member extract credentials from the instance. Patched releases are available.</description>
    </item>
    <item>
      <title>The AI Act&#x27;s transparency rules are live — what they mean for your automations</title>
      <link>https://hourbench.tech/blog-ai-act-artikel-50.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-ai-act-artikel-50.html</guid>
      <pubDate>Tue, 22 Sep 2026 09:00:00 +0000</pubDate>
      <description>Article 50 became applicable on 2 August 2026. Most of it lands on the model vendors, not on you. But three things do land on you, and two of them are one line of text.</description>
    </item>
    <item>
      <title>Who the Vault is for — and who should keep their money</title>
      <link>https://hourbench.tech/blog-wen-wir-bedienen.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-wen-wir-bedienen.html</guid>
      <pubDate>Tue, 22 Sep 2026 09:00:00 +0000</pubDate>
      <description>Most people who buy an automation product don&#x27;t have an automation problem. They have a Tuesday problem. Here is the person these workflows were chosen for, the work they take off the pile, and four honest reasons to walk away.</description>
    </item>
    <item>
      <title>n8n 2 is where everyone is now — five changes that break old workflows</title>
      <link>https://hourbench.tech/blog-n8n-2-umstieg.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-n8n-2-umstieg.html</guid>
      <pubDate>Tue, 22 Sep 2026 09:00:00 +0000</pubDate>
      <description>Version 2 was a hardening release, not a feature release. Which is exactly why it breaks things quietly: your workflow still opens, it just stops doing what it did.</description>
    </item>
    <item>
      <title>MCP quietly became the standard — and n8n speaks it in both directions</title>
      <link>https://hourbench.tech/blog-mcp-standard.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-mcp-standard.html</guid>
      <pubDate>Tue, 22 Sep 2026 09:00:00 +0000</pubDate>
      <description>Two years ago it was an Anthropic protocol. Now it sits under the Linux Foundation, OpenAI and Google ship it, and your n8n instance can be both ends of it.</description>
    </item>
    <item>
      <title>Draft, don&#x27;t send — the one rule that makes AI automations safe to run</title>
      <link>https://hourbench.tech/blog-entwurf-statt-senden.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-entwurf-statt-senden.html</guid>
      <pubDate>Tue, 22 Sep 2026 09:00:00 +0000</pubDate>
      <description>A wrong draft costs you five seconds. A wrong email costs you a client. Almost every automation people abandon was abandoned because it sent something.</description>
    </item>
    <item>
      <title>A map of the automation scene in 2026</title>
      <link>https://hourbench.tech/blog-automatisierungs-szene-2026.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-automatisierungs-szene-2026.html</guid>
      <pubDate>Tue, 22 Sep 2026 09:00:00 +0000</pubDate>
      <description>Four layers, three billing units, and one bottleneck that none of the vendors is selling a fix for. What the landscape actually looks like from a one-person business, with the numbers taken off the vendors&#x27; own pricing pages.</description>
    </item>
    <item>
      <title>Triage the inbox without burying a real enquiry</title>
      <link>https://hourbench.tech/blog-posteingang-sichten-ohne-anfrageverlust.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-posteingang-sichten-ohne-anfrageverlust.html</guid>
      <pubDate>Tue, 22 Sep 2026 09:00:00 +0000</pubDate>
      <description>An inbox classifier is useful only when its mistakes remain recoverable. Here is how workflow 02.01 labels mail, decides when to interrupt you, and leaves a trail when the model gets it wrong.</description>
    </item>
    <item>
      <title>Why the Vault runs on n8n and not on Zapier</title>
      <link>https://hourbench.tech/blog-warum-n8n-und-nicht-zapier.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-warum-n8n-und-nicht-zapier.html</guid>
      <pubDate>Tue, 22 Sep 2026 09:00:00 +0000</pubDate>
      <description>Two reasons, one of which is money and the more important one isn&#x27;t. Plus the four cases where Zapier is the better answer and we will say so.</description>
    </item>
    <item>
      <title>Five ways automation projects die in small businesses</title>
      <link>https://hourbench.tech/blog-fuenf-denkfehler.html</link>
      <guid isPermaLink="true">https://hourbench.tech/blog-fuenf-denkfehler.html</guid>
      <pubDate>Tue, 22 Sep 2026 09:00:00 +0000</pubDate>
      <description>None of them is a technical failure. Four are decisions made in the first hour, and the fifth is a decision nobody makes at all.</description>
    </item>
  </channel>
</rss>
