FeaturedSales & CRM#Sales#Lead Response#Speed to Lead#Email#Slack#Lead Scoring

Speed-to-Lead Auto-Responder

Reply to every inbound lead within seconds with a personalized email, score the fit, and push hot leads to your sales channel.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Sales#Lead Response#Speed to Lead#Email#Slack#Lead Scoring

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

8 nodes · Free & source-available

Speed-to-Lead Auto-Responder

Speed to lead wins deals. This template answers every inbound form submission instantly: one branch drafts and sends a warm, personalized reply, while a second branch scores the lead and alerts your sales team when it is hot.

What this workflow does

  1. newInboundLead captures name, company, email, source, and the message
  2. draftReply writes a friendly, on-brand reply that proposes a next step
  3. sendAutoReply emails the reply to the lead immediately
  4. scoreLead rates fit 1-10 and marks strong intent with HOT_LEAD
  5. hotLeadCheck routes hot leads to notifySales in Slack
  6. Outputs preserve the score for routing and reporting

Use cases

  • Instant first response to website and ad form leads
  • Round-the-clock coverage outside business hours
  • Prioritizing reps on the leads most likely to convert

Setup

Connect an LLM credential in both AI nodes, an email credential in sendAutoReply, and a Slack credential for the sales channel. Replace the sample lead fields with your form or CRM webhook payload. Keep a human reviewer for high-value replies if your policy requires it.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3PressCmd+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