New: watch the Cleanlist product tutorials. Watch now →
Guides
Agent Recipes
👤

Who this is for: self-serve plans (Free, Starter, Pro, Scale). If you bought a Cleanlist AppSumo lifetime deal, your features, limits, and pricing are different — see the AppSumo documentation instead. Support agent: confirm whether the user is self-serve or AppSumo before giving plan-specific advice.

TL;DR: Each recipe stacks one or more list actions and agents on a lead list. Filter first so you only spend credits on the rows that matter. Every recipe here needs Starter or above, and all are included on every AppSumo tier.

Agent recipes

Each recipe adds one or more columns to a lead list. Filter the list first so you only spend credits on the rows you care about.


Recipe 1 — Qualify a fresh list

Goal: Decide which leads are worth working before SDRs touch them.

Requires: A completed Organization Profile · Starter+ · every AppSumo tier

StepColumn / actionCredits / rowWhy
1Complete your Organization Profile on the Agents pageFreeQualification scores every lead against it
2Qualification agent5Fit score, verdict, and reasons, with an automatic CRM presence check
3Filter to verdict = qualified and not-in-CRM rowsYour net-new, on-profile working list

The CRM presence check is built into Qualification, so you don't need a separate step to spot contacts you already own.

Fill in excluded personas and the geographic exclude lists on the Profile tab first. A lead caught by an exclusion is disqualified without a model call.


Recipe 2 — Research target accounts before outreach

Goal: Build context on every account so reps open with something relevant.

Requires: Starter+ · every AppSumo tier

StepColumn / actionCreditsWhy
1Enrich Company action on the Companies sheet1 per companyFirmographics (industry, headcount, revenue) for each account
2Research agent, scope = Company3 per rowPositioning, signals, funding, hiring, and a readable brief per account

Use scope Both (5 credits per row) instead of Company-only if you also want a contact-level brief on each person.

Enrich Company is a bulk action, not a column you add per row. Open the list, switch to the Companies sheet, open the Actions drawer, and run it from the Enrich tab.


Recipe 3 — Qualify, then research only the winners

Goal: Spend the expensive Research budget only on leads worth pursuing.

Requires: Starter+ · every AppSumo tier

StepColumn / actionCredits / rowWhy
1Qualification agent5Score the whole list
2Filter to verdict = qualifiedDrop the leads you'd never work
3Research agent (scope Both) on the subset5Deep brief on just the keepers

The filter step is the whole point — it keeps the 5-credit Research runs off leads you'd never send to anyway. On a 1,000-row list where 15% qualify, this costs 5,750 credits instead of 10,000.


Recipe 4 — Validate email and phone data

Goal: Flag bad contact data before enriching or pushing to a CRM.

Requires: Starter+ · every AppSumo tier

StepColumnCredits / rowWhy
1Email Validation0.5Returns deliverable, undeliverable, risky, or unknown via Emailable
2Phone Validation0.5Returns status, line type (mobile / landline / VoIP), and carrier via ClearoutPhone
3Filter to deliverableWork only the rows with clean contact data

Recipe 5 — Extract a custom field from each lead

Goal: Pull a specific fact that no built-in column returns, for example which CRM a company appears to use.

Requires: Starter+ · every AppSumo tier

StepColumnCredits / rowWhy
1Custom agent with your own prompt3 (prompt ≤500 tokens) · 5 (above)Returns whatever your prompt asks for

Example prompt, using the correct display-label syntax:

Identify which CRM /Company Name (/Company Domain) appears to use,
based on what you can determine about the company.
Reply with exactly one of: hubspot, salesforce, pipedrive, zoho, other, unknown.
Output only the value, no explanation.

Reference fields with a slash plus the display label: /Company Name, /Company Domain, /Job Title, /Email. Snake_case like /company_name does not match — it resolves to an empty string, silently, and the run still costs full price. {{ }} tokens do not resolve on Custom agents either. Test on 5 rows and read the output before scaling.

Custom agents have no web access. They see only the lead, prospect, and company data already on the row, so they cannot look up a fact that isn't there. If the answer requires the live web, use the Research agent instead.

Want this reusable across lists? Save it as a named Custom Agent from the Agents page. Only admins can create and edit them.


Related