Form · Webhook → Slack · CRM
Enrich, score and route inbound leads in minutes.
A form needs only name and email. ListPlus adds the company from the domain, computes the fit score and hands A-leads to Slack and your CRM. The rest stays in the list – visible, not deleted.
Runs in ListPlus – no agent needed
Score and rules run for every new lead – no agent needed
Example · fictional contacts, real prices
Watch it
Setup
Build this workflow.
A way into the list – a form, a webhook or an app event (Typeform, Calendly, a HubSpot form). Your ICP criteria and a pipeline to Slack or the CRM.
What does a run cost?
The company from the email domain costs 0.25 credits per lead ($0.01 on Pro); personal domains trigger no lookup. Checks, rules and a rule-based score cost nothing, an AI criterion in the score 0.02 credits per AI answer. A pipeline handoff is charged per record.
- ListPlus runs automatically
A lead arrives
By form, webhook or app event the record lands in the list – with its origin.
- ListPlus runs automatically
Add the company from the domain
The email domain yields company, industry and size. Personal domains trigger no company lookup; disposable addresses are caught by the checks.
- ListPlus runs automatically
Compute the fit score
A score column: industry +40, size +30, role +30 – plus an AI criterion where a rule is not enough. The score recalculates whenever data changes.
- Slack · CRM runs automatically
Hand off A-leads, existing accounts to the owner
Rule: score ≥ 80 and not in the CRM → status “A”, Slack and CRM pipeline. Already in the CRM → status “Existing” for the owner. Below 50 → tag “Nurture”.
- Your team manual in ListPlus
Review the unclear ones
Rows with an open finding (name and email do not match, company unclear) stay on “Review”.
With your agent
Give your agent this brief.
A form or webhook on the list, a Slack or CRM pipeline. An agent with the “Set up” right can create score and rules – paused until you switch them on.
The same call from Claude Code, ChatGPT, Cursor or an n8n HTTP node – MCP and REST offer the same tools.
Agent guide (.md) ↗Set up the list “Inbound”: add the company from the email domain, a fit score (software industry +40, 51–500 employees +30, marketing or sales role +30), a match against the list “Customers”. Rules: score ≥ 80 and not a customer → status “A” and the pipelines “Slack #inbound” and “CRM”; customer → status “Existing”; score < 50 → tag “Nurture”. Create the rules paused and show me the cost per lead.
Tools and sample call
describe_setup · add_column · create_trigger · query_records · send_to_pipeline
create_trigger({
"list_id": "<shared_list_id>",
"name": "A-leads to Slack",
"on": "match",
"conditions": {
"groups": [
[
{
"field": {
"kind": "column",
"name": "Fit score"
},
"op": "greaterThanOrEqual",
"values": [
"80"
]
},
{
"field": {
"kind": "reference",
"listId": "<customers_list_id>"
},
"op": "isNotIn"
}
]
]
},
"actions": [
{
"kind": "status",
"status": "A"
},
{
"kind": "pipeline",
"pipeline": "Slack #inbound"
}
],
"activate": false
})Try it with your data
Routing runs only after normalisation and deduplication – otherwise “US” and “United States” land with two reps. A score is a rule, not a judgement; “Review” cases are seen by a person.