Building AI agents that write n8n workflows has one specific failure mode: the agent picks a node that looks plausible, invents an operation that does not exist, and produces a workflow that imports cleanly and then breaks at runtime. Hard to catch. Expensive to debug.

Developer Artyom Rabzonov published a structured catalog of every n8n node to HuggingFace to solve exactly that problem. It covers 524 nodes, every operation, every credential type, and a top-level properties schema. Free. CC-BY-4.0.

What Each Row Contains

Every row in the dataset maps to one node and includes:

• node_name: internal ID (e.g. slack, lmChatOpenAi)
• display_name: the label you see in the UI
• categories and subcategories: taxonomy values
• operations_supported: the actual operation values, not inferred ones
• credentials_required: exact credential type names
• properties_schema: JSON describing top-level property descriptors
• source_package: either nodes-base or @n8n/nodes-langchain
• github_permalink: pinned link to the .node.ts source file

Format is JSON and Parquet (Snappy). The dataset updates monthly.

The Agent Pipeline This Enables

The intended usage pattern is RAG over a tool catalog. Embed every row using description, operations, and credentials. At plan time, retrieve the top N nodes relevant to the user request. Hand the agent only those rows. Validate the emitted workflow JSON against the properties schema before deploy.

The developer includes a code example that filters nodes by operation using the HuggingFace datasets library:

from datasets import load_dataset

ds = load_dataset("automatelab/n8n-nodes-catalog")["train"]

messaging = ds.filter(
    lambda r: "message" in (r["operations_supported"] or [])
)
for row in messaging:
    print(row["node_name"], row["credentials_required"])

Numbers Worth Knowing

The catalog split landed at 431 nodes from nodes-base and 93 from @n8n/nodes-langchain. The langchain package is not a small footnote. A non-trivial number of nodes have an empty operations_supported list: those are root nodes like LLMs, vector stores, and output parsers where the operation abstraction does not apply. Useful to know if your planner filters by operation.

Caveats

• The properties schema is a top-level summary. For deep parameter shapes, use the github_permalink.
• Multi-version nodes report only the default version. The source link covers full version history.
• The CC-BY-4.0 license covers the catalog additions. The n8n source itself is governed by n8n’s own license.

A browsable index is also available at automatelab.tech if you want to explore nodes without loading the full dataset.

The post 524 n8n nodes in one free dataset to stop agent hallucinations appeared first on BizStack  —  Entrepreneur’s Business Stack.

Most enterprise approval workflows aren’t systems. They’re email threads with a spreadsheet bolted on. When a decision gets disputed or an auditor comes knocking, the answer lives in someone’s inbox. If that person left the company, the answer may be gone entirely.

Developer Manjunath built an open source platform to fix this using LangGraph, FastAPI, and SQLite. The full source, architecture diagrams, state machine documentation, and 56 passing tests are on GitHub.

The Core Technical Pattern

The workflow engine uses two LangGraph primitives to handle human-in-the-loop pauses without polling loops or background daemons.

• interrupt_before: Tells the graph to halt before a named node, persist the current state to the checkpointer, and return control to the caller. The graph resumes on the next explicit invocation with the same thread ID.
• AsyncSqliteSaver: A persistent checkpoint backend that survives server restarts. Unlike the default MemorySaver, which is process-local, AsyncSqliteSaver writes to SQLite and is readable by any process with the correct connection string.

In production, swapping CHECKPOINT_DB_URL to a Postgres connection string is the only change required. The application code stays identical.

Why Interrupt Beats Polling

The conventional human-in-the-loop approach writes a “pending review” flag to a database and polls until a human updates it. That pattern has two failure modes: the polling process is a single point of failure, and concurrent reviewers can both see “pending” and submit conflicting decisions.

The interrupt approach eliminates both. When the graph reaches the review node, it halts. No polling process. No flags. The checkpoint store holds the state. Resume happens via a single API call that loads the checkpoint, applies the reviewer’s decision, and continues execution from that exact node.

Immutable Audit Logging

Every event is appended to a log with no update or delete operations. The developer made one deliberate structural choice worth copying: document content, raw field values, and personal data are never written to the audit trail. Only structured metadata is logged, such as the risk score, the event type, and the actor. This keeps the audit log outside the data retention requirements that apply to the documents themselves.

Pluggable Workflow Modules

The platform ships with two workflow modules today: compliance review and procurement. Both were added without touching the orchestration engine. Adding a third requires one new folder in workflows/ and implementing a standard interface with three methods: name, build_graph, and get_input_schema.

The compliance review module runs six automated stages before a human sees anything, producing a risk score and a full rule evaluation. The reviewer gets the complete automated output, not a summary, before submitting a decision.

Production Path

The platform is designed local-first with a documented migration to Azure: SQLite to Postgres, local file storage to Blob Storage, API keys to Key Vault, and uvicorn to Container Apps. The developer describes it as one environment variable change per component.

If you’re building any approval, review, or escalation flow where decisions need to be traceable after the fact, this architecture is worth reading before you start wiring up another email chain.

The post Stop storing workflow state in email: LangGraph fixes it appeared first on BizStack  —  Entrepreneur’s Business Stack.

Australian creative agency Paper Moose is turning 15 this year. The agency started as a filmmaker collective in a garage, caught the first digital video production wave, and has grown into a full-service shop. Now it’s staring down what founder and CEO Nick Hunter calls the industrial revolution for knowledge work.

Hunter’s framework for thinking about AI’s limits comes down to one word: geist. German for ghost or spirit, he uses it to describe the X-factor that animates truly original creative work. His argument is that AI can automate tasks that can be tracked via benchmarks and improved through reinforcement learning. It cannot automate geist.

The reinforcement learning problem

Hunter gets specific about why. You could theoretically train a creative model by having a world-renowned creative director evaluate a million pieces of work until the model learns to choose as they would. But even if that worked, you’ve frozen one person’s sensibility. You’ve lost the diversity of creative outlooks that makes a truly resonant idea stand out. He argues that without a fundamental shift away from LLMs to some other underlying technology, there is no path to automating that diversity.

The more immediate threat, in his view, is not AI replacing great creative work. It’s AI flooding the market with low-quality output: what he calls slop creative.

Moose Review: testing creative before you spend

Paper Moose built Moose Review to address the slop problem directly. It’s an AI creative testing tool that evaluates work against a framework drawn from marketing science research on advertising effectiveness. The framework references Byron Sharp, Les Binet and Peter Field, Karen Nelson-Field, Orlando Wood, and Daniel Kahneman.

The tool uses synthetic focus groups, which Paper Moose calls Synths, and runs them through a set of tuned questions. According to Hunter, Synth responses mirror real human subgroups by up to 94%. The library now holds over 20,000 reviews. The reported outcome: results close to traditional focus groups, at a fraction of the cost and time.

“Moose Review gives us what creativity has never had before: a verifiable output with a quick feedback loop. It lets us kill weak ideas cheaply and confirm strong ones confidently, ensuring every dollar spent outperforms.” — Nick Hunter, Founder, CEO and ECD, Paper Moose

The internal platform bet

Beyond Moose Review, the agency has been building an internal software platform called Portal. Hunter describes it as a foundation for automating agency intelligence work, covering scheduling, documentation, financial tracking, research, and media implementation. The goal is to free up human capacity for geist-heavy thinking across client work.

Combined with in-house generative and traditional production capabilities, Paper Moose says this creates a leaner, faster operating model.

The operator angle

Hunter’s closing prediction is worth noting for anyone running a small creative operation: AI won’t replace creative agencies, but it will force them to become leaner, faster, and wilder. The next fifteen years, he says, belong to those willing to dramatically alter their business models to balance the automateable and the ineffable.

For solo operators doing content, branding, or ad creative, the same logic applies. Automate the intelligence layer. Protect the time you spend on the work that can’t be benchmarked.

The post Why this agency says AI will never replace great creative appeared first on BizStack  —  Entrepreneur’s Business Stack.

Every automation conversation hits the same wall. Someone asks what to build it in. Make.com, n8n, and custom Python agents all end up on the shortlist. Advocates show up for each one. And the discussion turns into a feature comparison that misses the actual question.

The right question is not which tool does more. It’s which tool your team can actually run at your current stage. Pick too simple a tool and you’ll rebuild in six months. Pick too complex a tool and the project stalls before it ships.

The framework below gives you a three-tier maturity model and a five-question checklist. Most teams land on a clear answer by question three.

Short answer: Use Make.com for non-technical ops teams running standard SaaS workflows. Use n8n when your team has some technical literacy and needs AI-native automation. Use custom Python agents on LangGraph when stateful multi-agent logic or production reliability requirements exceed what either platform can deliver.

️ The Three-Tier Model

Teams that have shipped more than a handful of automations tend to notice the same thing: the tool rarely fails. The mismatch between the tool’s complexity and the team’s capacity does. The maturity model maps teams into three tiers based on technical capacity and workflow complexity.

• Tier 1: Non-technical or visual-first teams running standard SaaS workflows. Make.com is built for this tier.
• Tier 2: Developer-adjacent teams who can read configuration files and understand API logic. n8n fits here.
• Tier 3: Engineering-capable teams building stateful, multi-agent AI systems. This is the custom Python and LangGraph tier.

Most teams start at Tier 1. Most outgrow it. The question is knowing when to move.

️ Tier 1: Make.com

Make.com is a visual, drag-and-drop automation platform with more than 1,500 app integrations. For ops teams running standard SaaS workflows with three to five steps and predictable volumes, it earns its place. You can connect a CRM to Slack, a form to a spreadsheet, or an email trigger to a project management tool in an afternoon without writing code.

The credit billing trap

In November 2025, Make.com switched from a step-count billing model to a credit-based system. The change reshuffled the cost calculus for power users in a way most comparison guides are not clearly explaining.

Under the current model, each individual step in a scenario consumes one operation credit. A 10-step scenario running 1,000 times per month consumes 10,000 operations, not 1,000. Add a conditional branch that fires extra steps on certain runs, and the real operation count climbs higher still.

For simple, linear, low-frequency workflows this is manageable. For complex, high-frequency workflows, or anything approaching AI agent behavior where each reasoning step adds to the count, costs can spike unexpectedly.

Where it breaks: Scenarios with more than eight steps at high frequency; conditional logic that multiplies step counts; any workflow needing stateful AI reasoning.

Tier 2: n8n

n8n is an open-source workflow automation tool. It’s self-hostable, which matters for teams with data residency or compliance requirements. And it counts each entire workflow run as a single execution regardless of how many steps that workflow contains.

That execution model is the key difference from Make.com. A 10-step workflow run 1,000 times in n8n counts as 1,000 executions, not 10,000 operations. At scale, the cost gap is material.

n8n is not a no-code tool. The canvas is visual, but working comfortably with it requires the ability to read JSON, understand HTTP requests, and think in terms of data transformations. A team with one technically-inclined member can get significant value from it.

The AI agent advantage

In 2025, n8n added native AI agent nodes with direct LangChain integration. You can build multi-step AI agent loops inside the visual canvas without writing custom code. A trigger fires an LLM call, the LLM output selects a tool, the tool result returns to the LLM for a decision, and the loop closes, all in n8n’s canvas.

Where it breaks: Stateful multi-agent architectures with shared memory; production-grade reliability requirements with custom retry logic; teams with no technical capacity at all.

Tier 3: Custom Python and LangGraph

LangGraph is a Python library in the LangChain ecosystem for building stateful, graph-based multi-agent AI systems. It’s designed for production deployments where agents must maintain context across multiple reasoning steps, coordinate with other agents, and recover gracefully when a step fails.

Custom Python agents built on LangGraph are not the right answer for every team. They require engineering capacity and carry maintenance overhead that no-code tools don’t. But for certain problems, they’re the only answer that works reliably at production scale.

When custom is the right choice:

• Multi-agent orchestration where agents share state and pass context between runs
• Conditional logic too complex to represent in a visual canvas
• Production deployments needing monitoring, retry logic, and observability layers
• Data-sensitive environments where processing must remain on-premise

Where it breaks: Engineering time is the primary cost. For teams without internal Python capacity, the investment is real. The honest trade-off is control and reliability versus time and resource.

The Decision Framework

Tier comparison

Five-question checklist

Run through these in order. Stop at the first answer that maps to a tier.

1. Does anyone on your team read JSON or YAML comfortably? No: Tier 1 (Make.com). Yes: continue.
2. Do your automations typically involve more than 8 steps? No: Tier 1 or Tier 2. Yes: Tier 2 minimum; revisit Make.com’s credit model carefully at your volume.
3. Do you need the agent to remember context between sessions or coordinate with other agents? No: Tier 1 or Tier 2. Yes: Tier 3.
4. Do compliance or data-residency requirements prevent sending data to a cloud SaaS platform? No: Tier 1 or Tier 2. Yes: n8n self-hosted (Tier 2) or Tier 3.
5. Is your budget model a fixed monthly ceiling or outcome-based? Fixed ceiling: review Make.com’s operation count at your target volume before committing; n8n is more predictable at scale. Outcome-based: custom-tier unit economics may be more favorable at volume.

FAQ

Can I start on Make.com and migrate to n8n later?

Yes. Workflow logic transfers conceptually but not by direct import. Plan for a one to two week rebuild for a multi-step scenario. The migration case is strongest when Make.com’s monthly credit costs begin to exceed what an n8n self-hosted server would cost.

When does a custom Python agent become worth the investment?

When you need agents that hold state across sessions, coordinate between each other, or require observability and retry logic that no-code canvases can’t provide. Most teams hit this ceiling at three to five deployed agents running in parallel on business-critical workflows.

Is n8n difficult to learn for a non-developer?

The visual canvas is approachable. The AI agent nodes require comfort with API concepts: HTTP requests, JSON payloads, and authentication patterns. A team with one technically-inclined member and two to three weeks of hands-on time typically reaches independent productivity.

The post Make.com vs. n8n vs. LangGraph: pick by maturity, not features appeared first on BizStack  —  Entrepreneur’s Business Stack.

If your brand’s SEO strategy was built around Google rankings alone, the ground is shifting under you. London-based startup Searchable just raised £10.3m to help businesses track and improve how they show up across AI-driven search, and the round signals where performance marketing budgets are heading next.

What Searchable Does

Searchable positions itself as a growth command centre for the AI search era. The platform monitors brand visibility across ten AI engines, surfaces insights through interactive agents, and connects analytics from Google Search and Google Analytics into a single view.

Clients include Goop, Farfetch, and Sonos. The pitch is straightforward: as more queries get answered by ChatGPT and similar tools rather than a traditional results page, brands need a different measurement layer to know whether they’re appearing at all.

The Operator Angle

For solopreneurs and small teams running content or SEO programs, this funding round is a signal worth noting. The tools your larger competitors will be using in 12 months are being built right now. Visibility in AI-generated answers is a distribution channel that existing analytics stacks don’t measure cleanly, and that gap is exactly what Searchable is raising money to close.

The £10.3m raise is earmarked to accelerate the platform. No breakdown of investors or deployment plans was disclosed in the announcement.

The post Searchable raises £10.3m to track brands across 10 AI search engines appeared first on BizStack  —  Entrepreneur’s Business Stack.

Most data analysts spend a chunk of every week pulling the same numbers, cleaning the same CRM fields, and writing summaries that were outdated before they hit Slack. Friday Studio is a free, open source agentic workspace that handles that layer so analysts can spend time on work that actually needs their judgment.

Here are the six workflows the Friday AI team documents as working today.

1. Competitive monitoring on a daily schedule

Friday monitors competitor websites, review platforms, news feeds, and LinkedIn pages on a schedule. Pricing changes, feature announcements, and positioning shifts get flagged the same day with a plain-English summary. Because Friday stores findings across sessions, you can ask “what changed with Competitor X this month?” and get a synthesized answer from everything it has tracked, rather than re-running searches manually.

2. Scheduled data reporting without a dashboard

Friday connects to Snowflake, Postgres, SQLite, and HubSpot. You configure the query once. Friday runs it on schedule, compares against the prior period, and writes a plain-English summary with the numbers that moved. If a metric crosses a threshold you define, such as MRR down 5% week-over-week or conversion rate below a set floor, Friday alerts the right person the day it happens. Setup takes about 20 minutes.

3. Research synthesis before big decisions

Give Friday a question, and it runs multi-source web research, pulls the most relevant findings, and produces a structured briefing with citations. Paste in customer interview transcripts or survey responses and it clusters themes, surfaces the strongest quotes, and produces a one-page summary. The output lands in Google Docs or Notion.

4. CRM and data quality audits

Friday runs a weekly HubSpot audit: contacts missing required fields, companies with no associated contacts, deals with no activity in the past 30 days. Results arrive as a prioritized Slack message with enough context for a sales ops person to act within an hour. You can extend it to auto-enrich flagged contacts using web research before queuing them for review. According to the Friday team, one analyst runs this every Sunday night so the team has a clean working list by Monday morning. Before this setup, that cleanup happened quarterly, if at all.

5. Multi-agent content and analysis pipelines

An analyst tired of running the same five-step research process manually built this workflow in Friday: a research agent pulls source material, a summarization agent distills key findings, and a scoring agent evaluates output against explicit criteria including depth, coverage of counterarguments, and source freshness. Each criterion gets a specific note on what is pulling it down. The loop runs without a human until the finished briefing appears in Notion. The Friday team reports this takes about 45 minutes to wire up the first time.

6. Anomaly alerting for production data

Friday monitors key data sources on a schedule. You define what normal looks like: acceptable ranges, expected row counts, join rates that should not drop below a threshold. When something falls outside those bounds, Friday posts a Slack alert with context, including which table, which metric, how far off, and a plain-English note on where to look first. The Friday team reports one data team caught a broken ETL pipeline 40 minutes after it failed because Friday flagged the row count drop before anyone opened a dashboard.

Getting started

Friday Studio is free to download at hellofriday.ai and open source on GitHub. Each workflow above is configured in plain English via chat. The Friday team says most setups take under 30 minutes to run the first time.

The post 6 ways data teams are automating the boring parts with AI appeared first on BizStack  —  Entrepreneur’s Business Stack.

The AI automation hype is loud. The demos look good. But when a database administrator running HIPAA-regulated infrastructure actually put three tools to the test, the results were not what the demos suggested.

This is that test. Real workflow. Real compliance requirements. Real verdict.

️ The Workflow That Defined the Test

The DBA in question supports hundreds of databases across dev, staging, non-prod, and production environments. Every database access request requires a sequential approval chain before an account gets provisioned. No exceptions.

The chain looks like this:

1. Developer, analyst, or product manager submits a request via Webex
2. Direct manager approves
3. Database manager approves
4. Security team gives final sign-off
5. An API call provisions the account at the correct access level
6. Credentials are delivered back to the requester via Webex
7. A Jira ticket is created for the network team to open the firewall port

Access levels are structured, not free text: read only, read/write, dev owner, application owner, DBA. Each maps to a specific API endpoint. The central database inventory is populated automatically via Terraform when infrastructure is created. If security does not approve, no account gets created. The audit trail is not optional. It is a HIPAA requirement.

Before the AI tools entered the picture, this process was entirely manual. The DBA would create a Jira ticket and a Word document, chase approvals from three separate people, manually provision the account, and email credentials back. Days would pass. Follow-ups stacked up.

Candidate 1: Claude Dispatch

Claude Dispatch is Anthropic’s feature inside Claude Cowork that creates a persistent connection between your mobile app and Claude Desktop running on your computer. Send a message from your phone, Claude acts on your desktop: reads files, calls APIs, returns results.

For personal productivity and ad-hoc delegation, the pitch is genuinely compelling. For a regulated approval chain, the architecture falls apart immediately.

• No server. Dispatch requires Claude Desktop to be running on your computer. The moment the laptop sleeps, it stops.
• No deterministic logic. The workflow is driven by an LLM reasoning about what to do. The same input could produce a different output on a different run.
• No sequential approval gates. Claude does not wait for a human to respond before deciding the next step.
• No audit trail. No timestamps, no record of who approved what and when.

Pricing: Dispatch is bundled with Claude Pro at $20/mo or Max at $100/mo. Accessible pricing. But the architecture disqualifies it before the price is relevant.

A workflow that depends on a laptop staying awake is not an enterprise workflow. It is a personal convenience.

Candidate 2: OpenClaw

OpenClaw is open-source, self-hostable, and designed as a personal AI assistant that runs on your own infrastructure. It connects to Webex, Telegram, Slack, and WhatsApp, listens on those channels, and uses an LLM to decide what action to take in response to a message.

The self-hosted angle made it more interesting for regulated environments. Running it on a VPS rather than a laptop means it can operate 24/7. The software itself costs nothing under an MIT license. Real costs are the VPS (roughly $5 to $15/mo) plus LLM API tokens from whichever provider you connect.

OpenClaw passes the first disqualification that knocked out Dispatch. It can stay on. But the deeper requirements exposed the same category of problem.

• No deterministic approval chain. It reasons about what to do. Handling every edge case the same way every time is not guaranteed.
• No structured error handling or retry logic. If an API call fails, the agent may or may not handle it gracefully.
• No auditable execution logs. LLM reasoning is not a HIPAA audit trail.
• No native Jira integration. You can make API calls, but you are building that logic yourself with no visual workflow editor.
• Real DevOps overhead. Docker, VPS configuration, model routing. Not a weekend project for someone who just needs the automation to run.

OpenClaw lets an AI decide what to do. In a regulated environment, you need a system that does exactly what it is configured to do — every single time.

️ The Tool Already Running: n8n

n8n is a visual, node-based workflow automation platform. It is not the newest tool in this comparison. It did not go viral. It does not use an LLM to decide what to do next.

The DBA had already built the database access workflow in n8n before starting this investigation. The investigation forced a clear articulation of why it works where the others do not.

• Always on. n8n runs on a server. No desktop dependency.
• Full execution logs. Every workflow step is logged with timestamps. If something fails, you know exactly where and why.
• Explicit approval gates. The manager node fires, waits for a webhook response, and branches on yes or no. The database manager node fires next. Then security. The LLM is not deciding the order. The configuration is.
• Native integrations. Jira, Webex, and REST API connections are built in. No custom code required to connect them.
• Dual audit trail. When security approves, a Jira ticket is created automatically with each approver documented: name, role, timestamp. A second ticket fires for the network team. Credentials are delivered to the requester via Webex.

The entire chain, from Webex message to provisioned account, is deterministic, auditable, and server-side. It does not matter whether the laptop is on. It does not matter whether the LLM is reasoning well that day. The workflow does what it is built to do.

The self-hosted Community Edition of n8n is free. Server costs can run as low as $4/mo. What n8n asks for is clarity of thought: you need to understand your process before you can automate it.

Side by Side

What Running It on Real People Revealed

One thing no tool comparison surfaces: some users have managers on paper who are not actually the decision-makers for the systems being requested. Org charts say one thing. Real accountability sits somewhere else.

When the approval request went to the wrong person, the workflow stalled. Not because the automation failed, but because the data it depended on was wrong.

A well-designed workflow makes your organizational data gaps visible. The automation did not hide the problem. It exposed it. And that forced the fix.

The Verdict

Claude Dispatch is a remote control for your desktop. It is well-designed and genuinely useful for personal task delegation. It has no server, no audit trail, and no deterministic logic. Those three gaps make it a non-starter for regulated workflows.

OpenClaw is a powerful personal AI assistant for technical users who want flexible, self-hosted automation. It can call APIs and respond to messages. It has no structured approval chain, no execution logging, and no enterprise governance features.

n8n is not the flashiest answer. But it runs reliably, logs everything, integrates natively with Jira and Webex, and does exactly what you configure it to do, every single run.

The better question is not which tool is newest. It is what kind of automation you are building. If the answer involves regulated data, sequential human approvals, and a legal requirement to prove who did what and when, the answer is still n8n. If the answer involves personal productivity and flexible task handling, Dispatch and OpenClaw are worth a serious look. Both things can be true at the same time.

The post n8n vs. Claude Dispatch vs. OpenClaw: which wins for regulated workflows? appeared first on BizStack  —  Entrepreneur’s Business Stack.

Manual expense reimbursement is a tax on your team’s time. Someone photographs a receipt, emails it, someone else opens it, types numbers into a spreadsheet, then pings a manager. Every step is a handoff that can break.

This tutorial walks through an n8n workflow that eliminates most of those handoffs. It parses receipt images via API, routes expenses by amount, logs approvals to Google Sheets, and notifies submitters via Slack or Gmail. No code required.

What You’ll Build

The workflow does five things in sequence:

1. Triggers when a receipt image is submitted via webhook, Gmail, or Google Drive
2. Calls the Receipt Parser API and gets back structured JSON
3. Routes based on amount: auto-approves expenses under $50, flags anything over for manager review
4. Logs every expense to a Google Sheet
5. Notifies the submitter via Slack or email with the parsed details

Prerequisites

• An n8n instance, cloud or self-hosted (n8n.io)
• A Receipt Parser API key from ilovesreceipt.com (free tier: 500 calls/month, no credit card required)
• A Google account for Sheets logging
• Optional: a Slack workspace for notifications

Step 1: Set Up the Trigger

Pick your entry point based on how receipts arrive. Three options:

• Webhook (recommended): Add a Webhook node, set method to POST. Any tool that can send a webhook, including forms, mobile apps, and Zapier, can trigger this workflow.
• Gmail: Add a Gmail Trigger node. Filter by subject containing “receipt” or “reimbursement”. Fires on each matching email with an attachment.
• Google Drive: Add a Google Drive Trigger node. Watch a specific folder such as /Receipts/Pending. Fires when any new file is uploaded.

The rest of this tutorial uses the webhook option since it’s the most reusable across intake methods.

Step 2: Read the File

No conversion step needed. The Receipt Parser API accepts the raw file as multipart/form-data, so base64 encoding is not required.

If your trigger provides a URL (for example, a Google Drive file URL), add an HTTP Request node set to GET to download the binary first. If your trigger delivers a binary attachment directly, such as a Gmail attachment, pipe it straight to Step 3.

Step 3: Call the Receipt Parser API

Add an HTTP Request node with these settings:

Store your API key in n8n Credentials as a Generic Credential with Authorization → Bearer YOUR_KEY. This keeps it out of the workflow JSON and reusable across other flows. Get a free key at ilovesreceipt.com.

After this node runs, structured data is available in subsequent nodes as $json.data.merchant.name, $json.data.total, and so on.

Step 4: Route by Amount (IF Node)

Add an IF node with this condition:

{{ $json.data.total }} > 50

• True branch: flag for manager review
• False branch: auto-approve and log

You can layer additional conditions if needed: category-based routing (meals vs. travel vs. supplies), a merchant allowlist or blocklist, or employee-specific thresholds.

Step 5: Log to Google Sheets

On the False (auto-approved) branch, add a Google Sheets node. Set Operation to Append Row, point it at your expense log spreadsheet, and map these columns:

Step 6: Flag Large Expenses in Slack

On the True (high expense) branch, add a Slack node. Set Operation to Send Message, target the #expense-approvals channel, and use this message template:

  *Expense Approval Required*

*Merchant:* {{ $json.data.merchant.name }}
*Amount:* ${{ $json.data.total }}
*Date:* {{ $json.data.date }}
*Payment:* {{ $json.data.payment_method }}

React ✅ to approve or ❌ to reject.

Step 7: Notify the Submitter

On both branches, add a Gmail or Slack node to confirm receipt. Use this message body:

Hi there — your expense was received and parsed successfully.

Merchant: {{ $json.data.merchant.name }}
Date: {{ $json.data.date }}
Total: ${{ $json.data.total }}

{{ $json.data.total > 50 ? "Your expense has been flagged for manager review." : "Your expense has been auto-approved and logged." }}

Testing the Workflow

Open the workflow in n8n and click Execute Workflow with test mode on. Then send a POST request to your webhook URL with a receipt image:

curl -X POST https://your-n8n-instance.com/webhook/receipt-parse 
  -F "data=@receipt.jpg"

Check your Google Sheet for the logged row and your Slack channel for any approval notifications.

Going Further

Once the core workflow is running, a few extensions are worth considering:

• Multi-currency support: The API detects currency. Add a conversion step using an exchange rate API to normalize totals.
• PDF invoices: The API handles PDFs too, useful for contractor invoices submitted via email attachment.
• Airtable instead of Sheets: Swap the Google Sheets node for an Airtable node for richer filtering and views.
• Approval loop: Use n8n’s Wait node to pause the workflow until a Slack reaction is received before marking the expense as approved.

Common Pitfalls

• Binary data not passing through: Make sure the node connecting to the HTTP Request node is set to pass binary data, not just JSON. Check the node’s output panel to confirm a binary item is present.
• API key exposed in workflow JSON: Always use n8n Credentials for the API key. Pasting it directly into the node makes it visible to anyone who exports the workflow.
• IF node evaluating strings instead of numbers: If $json.data.total comes back as a string, wrap it in Number() or use n8n’s expression editor to cast it before the comparison.

The post Automate expense reimbursement with n8n and a receipt API appeared first on BizStack  —  Entrepreneur’s Business Stack.

Nectar Social has closed a $30 million Series A to expand its AI marketing platform. The round was reported on May 17, 2025.

What Nectar Social Does

Nectar Social operates in the AI marketing space, building platform tooling aimed at social and marketing workflows. Beyond the funding announcement itself, specific product details from the announcement were not available at time of writing.

Why This Round Matters

A $30M Series A is a meaningful signal in the AI marketing tools category. It means institutional capital is moving into AI native marketing infrastructure, not just AI features bolted onto legacy platforms.

For solo operators and small marketing teams, that is worth tracking. Companies raising at this stage tend to ship fast and price aggressively to capture market share before the round is spent. Early pricing windows on well funded AI marketing tools often close once the growth team hits its targets.

The Operator Takeaway

If Nectar Social is on your radar as a potential tool for your marketing stack, now is the time to evaluate it. Funded startups at the Series A stage are usually still hungry for case studies, willing to negotiate on pricing, and responsive to feedback in ways that change once they hit scale.

Watch for product announcements tied to this funding. A $30M raise at the Series A stage typically comes with a hiring push and a shipping sprint in the 90 days that follow.

The post Nectar Social closes $30M Series A for its AI marketing platform appeared first on BizStack  —  Entrepreneur’s Business Stack.

Nectar Social closed a $30 million Series A led by Menlo Ventures and Anthropic’s Anthology Fund. The company describes its product as an AI-powered marketing operating system.

What Nectar Social Automates

The platform targets the full operational marketing stack. According to the company, that includes ad copy and blog post generation, social media updates, campaign management, audience segmentation, real-time analytics, and SEO optimization.

That scope explains the “operating system” framing. It’s not positioning itself as a point tool for one task. It’s positioning itself as the layer that runs the whole workflow.

The Operator Implication

Junior content, social media management, and SEO execution roles are the obvious pressure points. The platform is built to handle the repeatable task layer those roles currently own.

For operators running lean teams or outsourcing that work today, this funding signals the category is scaling fast. The question worth asking now: are you a buyer of this kind of system, or are you someone whose current workflow looks a lot like what it replaces?

The post Nectar Social raises $30M Series A to automate marketing ops appeared first on BizStack  —  Entrepreneur’s Business Stack.