All templates
FeaturedIntegration#Payments#Stripe#Webhook#Email#Slack#Integration

Payment Webhook Handler

Receive a Stripe-style webhook payload, parse the event, send a receipt email on success, and Slack-alert your team on failure.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Payments#Stripe#Webhook#Email#Slack#Integration

Click a node to select it — same as the Heym editor; the panel shows its settings.

10 nodes · Free & source-available

Payment Webhook Handler

A complete inbound payment event pipeline: parse the webhook JSON, branch on success vs failure, email the customer a receipt, and ping your team on Slack when a charge fails — all without writing a line of server code.

What this workflow does

  1. Input receives the raw Stripe webhook JSON body
  2. Set extracts event type, amount, currency, and customer email from the payload
  3. Condition checks whether event_type equals payment_intent.succeeded
  4. Send Email (success path) sends a payment receipt to the customer
  5. Slack (failure path) alerts your ops channel with the failure reason
  6. Output returns the parsed event for downstream logging

Use cases

  • Stripe, Paddle, or LemonSqueezy webhook processing
  • SaaS subscription lifecycle events (payment succeeded, failed, refunded)
  • E-commerce order confirmation and failed-payment recovery

Setup

Point your payment provider's webhook endpoint at a Heym webhook trigger URL (replace the textInput node with a Webhook trigger node for production). Add an SMTP credential to Send Email and a Slack credential to the alert node.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3Press Cmd+V / Ctrl+V — nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis · production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom · glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner — none of them talk.
symptom · visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym · one runtime
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym