3 production-ready workflow templates — Lead CRM, Stripe fulfillment, Form→Sheets+Slack

Built with n8n
1

Sharing three workflows I built for real production use. Each one is documented and handles the edge cases that the basic tutorials skip (duplicate detection, error logging, null-safe field parsing).

**What’s in the Starter Pack ($29 one-time):**

  1. **Lead Capture → CRM → Welcome Email** — webhook → Google Sheets CRM → Gmail personalised welcome. Zero paid nodes.

  2. **Stripe Payment → Fulfillment → Receipt** — Stripe webhook → order record → fulfillment trigger → branded receipt email via Resend. Works for digital products.

  3. **Form Submission → Google Sheets + Slack Alert** — any form webhook → validated Sheets append → Slack DM to owner. Good for internal ops / waitlists.

Each comes with:

  • Clean, commented JSON (import-ready)
  • Setup guide: which credentials to configure and in what order
  • Test checklist so you know it’s working before you go live

**$29 one-time. No subscription, no upsell.**

→ n8n Workflow Starter Pack (3 Workflows)

First workflow is free to try — reply and I’ll share the JSON so you can validate the quality before buying.

1 Like
2

Dropping the free one here instead of making you ask — here’s the Lead Capture → CRM → Welcome Email workflow JSON.

This covers the full pattern: webhook in → validate → Sheets write → Gmail out → error alert. Once you have the credentials wired, the other two in the pack slot in the same way.

3 n8n variables to set before activating:

  • CRM_SHEET_ID — the long ID from your Google Sheet URL
  • REPLY_TO_EMAIL — your support address (shown as reply-to on the welcome email)
  • OPERATOR_EMAIL — your own inbox for silent error alerts

Import: Workflows → Import from File, or paste via the </> button in the editor.

The other two (Stripe fulfillment and Form→Sheets+Slack) are in the full pack: n8n Workflow Starter Pack (3 Workflows) — $29 one-time, no subscription.

3

The Stripe fulfillment pattern is solid - one edge case worth guarding is idempotency. Stripe webhooks can fire more than once for the same event (replay, network retry), so if your template doesn’t already check the Stripe event ID before triggering fulfillment, adding a lookup against a “processed_events” sheet or a simple static data store before the fulfillment step prevents duplicate sends. The Lead Capture flow has the same risk if the webhook fires twice before the Sheets write completes.

4

Nice pack. For production templates like CRM, Stripe, and Slack, I’d include a small go-live receipt in the README: credential aliases, dedupe key, record id written, email or message id sent, and where errors alert.

That makes it easier for someone to trust the JSON before wiring it to live accounts. Do you include that in the checklist?