Build a full Agentforce inbound lead agent with Lusha

This agent runs autonomously inside Salesforce Agentforce. It triggers on every new inbound lead, executes a complete intelligence pass via the Lusha API, makes routing decisions based on ICP fit, and delivers a fully contextualized lead to the right rep — all without human intervention.

What you’ll get back

Within 60 seconds of a form submission, the rep receives this in Slack:

And the Lead record in Salesforce looks like this:

Build it

Step 1 — Complete Workflows 1 and 2 first

This agent builds on the foundations established in the first two workflows in the series. Before building the full agent, confirm that the custom fields from Workflow 1 and Workflow 2 are in place on your Lead and Contact objects. The agent uses those fields as its output targets.

Step 2 — Add pre-call brief field to the Lead object

In Salesforce Setup, go to Object Manager → Lead → Fields & Relationships. Add one additional custom field:

Step 3 — Create the Agentforce agent in Salesforce

In Salesforce Setup, go to Agentforce → Agents → New Agent. Configure as follows:

• Agent name: Lusha Inbound Lead Agent
• Agent type: Autonomous
• Primary object: Lead
• Trigger: Record created
• Entry condition: LeadSource is not null (or remove condition to run on all new leads)

Step 4 — Add Agent Actions

In the Agent Builder, add the following actions in sequence:

Step 5 — Configure the ICP scoring Prompt Template

In Salesforce Setup, go to Prompt Builder → New Prompt Template. Create a template that takes the enriched lead fields as inputs and returns an ICP score and reason. A starting template:

You are an ICP scoring agent. Score the following lead against
the ICP criteria below and return a JSON object with score
(High/Medium/Low), criteria_met (array), criteria_failed
(array), and reason (one sentence).

ICP criteria:
- Industry must be: {ICP_INDUSTRIES}
- Employee count must be between: {ICP_MIN_EMPLOYEES} and
  {ICP_MAX_EMPLOYEES}
- Funding stage must be: {ICP_FUNDING_STAGES}
- Seniority must be: {ICP_SENIORITY_LEVELS}
- Geography must be: {ICP_GEOGRAPHIES}

Lead data:
- Industry: {Lead.Industry}
- Employees: {Lead.Lusha_Employee_Count__c}
- Funding stage: {Lead.Lusha_Funding_Stage__c}
- Seniority: {Lead.Lusha_Seniority__c}
- Country: {Lead.Country}

Return only valid JSON. No preamble.

Step 6 — Configure the pre-call brief Prompt Template

Create a second Prompt Template that generates the pre-call brief:

Write a pre-call brief for a sales rep in under 60 words.
Use only the data provided. Be specific. No generic phrases.

Contact: {Lead.FirstName} {Lead.LastName},
  {Lead.Lusha_Seniority__c} at {Lead.Company}
Company: {Lead.Industry}, {Lead.Lusha_Employee_Count__c}
  employees, {Lead.Lusha_Funding_Stage__c}
ICP score: {Lead.Lusha_ICP_Score__c}
Top signal: {Lead.Lusha_Top_Signal__c}
Score reason: {Lead.Lusha_Score_Reason__c}

Return the brief as plain text only.

Step 7 — Configure the Slack notification

In the Agent Builder, add a Slack Notification action as the final step. Configure the message template to include the lead name, company, ICP score, top signal, direct dial, verified email, pre-call brief, and a deep link to the Salesforce Lead record. Send to the assigned rep’s Slack user ID, retrieved from the Lead.Owner field.

Step 8 — Test end to end

Create a test lead with a known email address. Monitor the agent run in Agentforce → Agent Runs to confirm each action completes successfully. Verify the Lead record is fully enriched, the ICP score is correct, the pre-call brief reads naturally, and the Slack notification arrives with all fields populated. Target run time under 60 seconds. Full troubleshooting guidance at docs.lusha.com/guides.

What this agent replaces

The full Lusha for Salesforce series

This agent is the seventh and final workflow in the series. Each workflow stands alone — build one or build all seven.

Together they give you a fully autonomous Lusha-powered Salesforce stack:

1. Auto-enrich new leads with Lusha inside Salesforce Agentforce →
2. Score and route leads by ICP fit →
3. Alert reps when a key contact changes roles →
4. Surface buying signals on open deals →
5. Enrich and score accounts on a scheduled cadence →
6. Enrich contacts before a Salesforce campaign goes out →

Example outputs in this workflow are illustrative — they reflect the structure, fields, and format of real Lusha API output, but were not pulled from a live session. Build this workflow with your own Lusha API key and Salesforce org to see live results.