Agent recipes

How to use a recipe

1. Go to Agents and click New agent.
2. Paste the recipe’s sentence into Describe the job, changing the details (titles, channel, schedule) to yours. Several recipes are also one-click starters on that screen.
3. Answer Clu’s questions. Clu sizes the audience for free and proposes a play.
4. Click Review on canvas, check the steps, then Accept.
5. Set the agent’s Limits, click Try it and check the results, then click Looks good (or Turn on).

Step settings and prices are in the Play steps reference; triggers are in Plays and triggers. Prices for the Research and Qualification skills come from your workspace’s estimate, shown on each step card.

Prospecting

Weekly ICP leads

Ask Clu: “Every Monday, find new people who match my ICP, get their verified work emails, and send me the list in Slack.” (starter Weekly ICP leads)

Into a sequence instead: “Every week find 30 heads of RevOps at Series B SaaS companies and put them in my RevOps intro sequence.”

Good to know

• The weekly number counts people. The Runs tab shows each week’s progress, for example “30 of 30 people”, and why the week ended.
• Add to sequence skips people with no email or a risky one, people already in the sequence, and anyone active, replied or stopped in another sequence, each with a reason. A draft sequence holds people until you launch it.
• Ask for Validate after Enrich if you want emails verified (0.5 per check), or Skip leads already in CRM to leave out people you already have.
• The Weekly ICP outbound template does a similar job and also qualifies people and round-robins them to your reps.

Lookalikes of best customers

Ask Clu: “Each month find 50 companies like these 10 best customers and add their heads of sales to Salesforce”, followed by the 10 domains. (starter Lookalikes of best customers)

Good to know

• Your seed companies, and every company already an Account in your connected CRM (matched by website domain), are left out.
• With Find People, the monthly number counts people. Keep 1 person per company if you counted companies.
• Set the agent’s Records per run to at least your monthly number, or it lowers the volume.

New leaders at target accounts

Ask Clu: “When a new VP or director of sales or marketing starts at one of our target accounts, research the account, log it in Salesforce and tell the account owner.” (Simpler starter: New hires at target accounts, “Watch my target accounts for new sales and marketing leaders and add them to a list.”)

Good to know

• Clu asks what counts as new in the role (30, 60 or 90 days) and where a message goes when the owner isn’t linked in Slack.
• The play keeps its own copy of your target domains. If they live in a list or CRM field, later changes there don’t update the play.

Funding round at a target account

Ask Clu: “Tell me when any of these 40 accounts raises money and add their VP of Sales to Salesforce”, followed by the domains.

Good to know

• Funding data can trail the announcement by weeks; the 90-day window absorbs that. The first run fires for every account whose round is already inside the window, so expect a burst of emails on day one.
• “Tell me only” variant: drop Find People, Enrich and Sync, and the agent costs nothing.
• For broader account signals (hiring, news, funding and headcount at up to 10,000 named accounts), use the Something happens at an account trigger, which charges per signal.

Website visitors to decision makers

Ask Clu: “When RB2B tells us a company visited our pricing page, find their VP of Sales and head of ops, skip companies already in a deal, and add them to HubSpot for the account owner.”

Good to know

• Create the webhook URL after you accept the play, and keep the play off until a real RB2B submission maps correctly.
• Records are per visit, so a company that visits twice runs twice. Ask Clu to skip leads already in your CRM if that matters.

Inbound and CRM hygiene

Route inbound leads to the right rep

Ask Clu: “When someone fills in our demo form, enrich them, check if they fit, give the good ones to the right rep in Salesforce and ping that rep in Slack.” (Simpler starters: Route inbound to owners and Qualify inbound leads.)

Good to know

• Clu asks who owns each lead (for example “the account owner, else Dana and Eli in turn”) and where a message goes when the rep isn’t linked in Slack.
• You can turn on webhook signing (HMAC) in the play panel. Never paste secrets in chat.
• The Slack channel must be internal to your workspace.

Enrich new CRM contacts in place

Ask Clu: “When a contact is created in my CRM without an email or phone, enrich it and update the record.” (starter Enrich new CRM contacts; template Inbound enrich and route back)

Fill missing emails every night

Ask Clu: “Every night, find Salesforce contacts with no email and fill them in.” (starter Fill missing emails)

Good to know

• To try misses again, ask for “recheck misses again after 30 days” (Run each record again after). Found contacts leave the condition, so only misses come back.
• Enrich and CRM Action retry temporary failures after 1, 6 and 24 hours, at the step that failed, without charging earlier steps again.
• Without a LinkedIn URL field mapped for Contacts, Enrich has only name and company to work with and finds far fewer emails.
• Records a rep owns, or with an open deal, are left alone when your CRM settings protect them. Ask Clu for Allow updates to owned records if you want them filled too.
• Variants: missing phones (10 per phone found), Leads instead of Contacts, or HubSpot.

Quarterly still-employed check

Ask Clu: “Every quarter check all our Salesforce contacts to see who still works at their company and mark the ones who left.”

Good to know

• Budget carefully: at up to 3.5 credits a contact, 10,000 contacts cost up to 35,000 credits a quarter. Narrow the conditions rather than capping the count, because a cap re-checks the same contacts every quarter and never reaches the rest.
• Add “Employment status is not Left” to the conditions so you don’t pay to recheck people already marked.
• A large CRM is swept over several days, not in one run. Quarterly runs start on the first business day of January, April, July and October.
• To check one list instead of the whole CRM, run Employment check on the list.

CRM duplicate cleanup

Find and merge duplicate Salesforce or HubSpot records on a schedule, with your review before anything merges. It costs no credits. See CRM duplicate cleanup.

Research and reporting

Brief before every prospect meeting

Ask Clu: “Before any meeting with a prospect, send me a brief on the person and their company with anything Salesforce has on them.” (Related starter: Account briefs.)

Good to know

• The CRM is only read, never written. The email goes to you, never to the prospect.
• If no Account matches the company’s domain, the CRM lines are empty: that means no match was found, not that there is no history.

Stalled deals before pipeline review

Ask Clu: “Every Monday morning tell each rep in Slack which of their deals haven’t moved in two weeks.” (Related starter: Deal review prep.)

Good to know

• A deal is listed once per quiet stretch: the first Monday after it crosses 14 days. It comes back only after new activity and another quiet stretch, so this is not a full list every week.
• A stage change alone doesn’t count as activity. Reps with no stalled deals get no message.
• Slack shows 25 rows, then “and N more”.

Weekly pipeline summary

Ask Clu: “Every Friday at 4 send #sales a summary of the pipeline: what moved, what closed and what’s at risk.” (starter Weekly pipeline summary)

This is a scheduled brief, not a record play: a Schedule trigger (Friday 16:00), a Brief step that reads your CRM deals, and Notify posting the brief to #sales. What goes into the brief lives in the agent’s Instructions.

Good to know

• It only reads; it never changes your CRM.
• It’s charged like a Clu message, up to the agent’s Brief credits per run (100 unless you change it, at most 1,000).
• There are no records, so Try it runs one real brief and holds its delivery: you read the brief and see where it would go before anything reaches #sales.
• The brief covers the deals it read, so in a very large pipeline it may not list every deal.

Skill recipes on a lead list

These run from a list’s Actions → Skills tab, need Starter or above, and don’t need Agents. Prices below use the default estimates; your exact price is shown before each run. See Skills.

Why qualify first: on a 1,000-row list where 15% qualify, Qualification on every row (about 600 credits) plus Research on the 150 keepers (about 1,830) costs about 2,430 credits, against about 12,200 to research all 1,000 rows.

Example Custom skill prompt (type / in the editor to insert the variable chip):

Classify the seniority of {{lead.job_title}} as exactly one of:
Executive, Director, Manager, Individual contributor, unknown.
Output only the value.

The Custom skill sees only the data on the row. It can’t look anything up on the web; for that, use the Research skill.

Related

• Build your first agent: the full walkthrough
• Agents
• Plays and triggers
• Play steps reference
• Skills
• Sequences
• CRM duplicate cleanup
• Credits and pricing