Automation workflows for n8n

Templates that ship with proof they run.

Everyone sells "500 free n8n workflows." Almost none of them prove the thing actually works. Every FlowProof workflow comes with a run log, screenshots, and a real cost-per-run — so you import it and it just works.

See the vault → What "proof" means Instant download · MIT-style reuse · money-back
proof-log · sample · daily-ai-news-digest.json
# sample of the log format · imported into n8n 2.29 · run manual
input → 2 RSS feeds, 37 items in last 24h
step 1 → read feeds step 2 → filter 24h
step 3 → Claude summarize model haiku · ~$0.002/run
output → 1 digest email · 5 themes · 37 links preserved
time → 11.4s  PASS

Every workflow ships with one of these, captured from a real run before it goes on sale. Not a promise — a receipt.

The vault · v1

Ten workflows. API and RSS only — no scrapers that break next week.

Each one is a single job done properly, with the credentials it needs listed up front and a cost estimate before you run it. We release in demand order: two workflows go on sale first, and the rest ship as buyers ask for them.

04 · launch workflow

Open Gmail to finished reply drafts

Every unread email arrives classified and summarized, with a reply draft already in the thread when one makes sense. Nothing sends itself.

GmailClaude
on sale first · proof before listing
08 · launch workflow

Your newsletter draft, waiting at 8am

Your feeds merged and curated into one HTML newsletter, saved to Gmail drafts with every source link preserved. You edit and send.

RSSClaudeGmail
on sale first · proof before listing
01

Daily AI News Digest

Pull any set of RSS feeds, summarize with Claude into themed sections, deliver to email or Slack.

RSSClaudeGmail/Slack
proof captured · releases next
02

Stripe Revenue Digest

Every morning, total yesterday's charges and refunds and post a clean summary to Slack.

StripeSlack
proof captured · releases next
03

Invoice & Receipt → Sheet

Inbound attachments read by an OCR model, parsed to line items, appended to a spreadsheet.

OCRSheets
built · releases on demand
05

YouTube → X / LinkedIn

New upload becomes a summary and platform-native post drafts, ready for review.

YouTubeClaude
built · releases on demand
06

Meeting Notes → CRM

POST a transcript in, get a structured CRM note back: TL;DR, decisions, action items with owners.

WebhookClaudeNotion
built · releases on demand
07

Form → CRM + Slack

Form submissions become scored CRM leads plus a sales-channel ping. Deterministic rules, zero model spend.

WebhookNotionSlack
built · releases on demand
09

Competitor News Watch

Watch official feeds and APIs — not scraped pages — and get one daily roll-up.

RSS/APISlack
built · releases on demand
10

Blog Draft Pipeline

A keyword queue in a sheet comes back as outlines and full drafts, written to the same row for review.

SheetsClaude
built · releases on demand
Pricing

Buy one, or take the whole vault.

Sold through Gumroad — they're the merchant of record, so your invoice is clean and no personal seller details are exposed.

Single
$29 / workflow
  • One workflow + its proof log
  • Setup README & cost table
  • Free fixes for spec changes
Get single
Launch pair
$49 / both launch workflows
  • Inbox drafts + newsletter drafts
  • Both proof logs + test fixtures
  • Your vote sets the release queue
Get the pair
Full vault
$149 / all + updates
  • All ten as they release, plus new drops
  • Six months of updates
  • Priority on requested workflows
Get the vault
FAQ

The questions a careful buyer asks.

What exactly is the "proof"?

A short log per workflow: the n8n version it ran on, the test input, the result, run time, and the real API cost — plus three screenshots (canvas, output, execution). You can see it worked before you spend a cent.

Why are only two on sale?

A workflow goes on sale only after its proof log is captured, and we release in the order buyers ask. The launch pair covers the two most repeated daily jobs: answering email and drafting a newsletter.

Will these break in a week?

Every v1 workflow uses official APIs and RSS — no page scraping that breaks on the next site redesign. When a service ships a breaking change, buyers get the fix.

What do I need to run them?

A self-hosted or cloud n8n instance and the credentials each workflow lists (e.g. an Anthropic key, a Gmail connection). Cost estimates are on every product page.

Refunds?

If a workflow doesn't run as its proof log shows, you get your money back. The proof is the promise.