Inbound inquiries hit a web form or a shared email and then wait for someone to copy them into ERPNext, tag them, and figure out who owns them. By the time that happens, the prospect has often moved on.
sonnet1 weekERPNextGmailOpenAISlack
Claude
81ROI
83Scale
$4.1k92Saved
ROI for
README.md
Why this subagent
Inbound inquiries hit a web form or a shared email and then wait for someone to copy them into ERPNext, tag them, and figure out who owns them. By the time that happens, the prospect has often moved on.
This agent captures every inquiry, reads it, and creates a routed ERPNext lead with an owner assigned. The prospect gets an immediate acknowledgment and the rep gets a Slack ping, so the first response goes out fast. Leads stop slipping through the gap between the form and the CRM.
How it runs
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
Classify each lead by product interest, region, and rough deal size from the message text.
pending
Route the lead to the right sales territory and assign an owner by your rules.
pending
Send an acknowledgment to the prospect and notify the assigned rep in Slack.
pending
Sample output
json
// Sample output
// (generated when the pipeline finishes)
From an inbound inquiry, create an ERPNext lead with product_interest, territory, and assigned owner, and return the acknowledgment text.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.