Limitations
- As with other Salesforce actions, the exact parameter set and behavior can change over time. Confirm how this action behaves in your own environment before you depend on it for large-scale or fully automated lead creation.
Prerequisites
- Your Salesforce org must be connected as a data source in Glean, and an admin must enable the Salesforce action pack and complete Salesforce Actions Setup including OAuth configuration.
- Users must authenticate for Salesforce actions on first use.
Supported parameters
| Parameter | Type | Description |
|---|---|---|
| Annual revenue | Number | Estimated or known annual revenue for the lead’s company. |
| City | String | City for the lead’s mailing or business address. |
| Company | String | Company name associated with the lead (required). |
| Country | String | Country for the lead’s mailing or business address. |
| Description | String | Free-form notes or additional context about the lead. |
| String | Primary email address for the lead. | |
| First name | String | Lead’s given name. |
| Industry | String | Industry classification for the lead’s company. |
| Last name | String | Lead’s family name or surname (required). |
| Lead source | String | Origin of the lead (for example, Web, Partner, Event). |
| Number of employees | Integer | Number of employees at the lead’s company. |
| Phone | String | Primary phone number for the lead. |
| Postal code | String | Postal or ZIP code for the lead’s address. |
| Rating | String | Internal quality or priority rating for the lead. |
| State | String | State, province, or region for the lead’s address. |
| Status | String | Current lifecycle status of the lead (for example, New, Working). |
| Street | String | Street line of the lead’s mailing or business address. |
| Title | String | Job title or role of the lead. |
| Website | String | Website URL associated with the lead’s company. |
Usage example
You have a list of qualified prospects from a recent trade show and need to add them to Salesforce as leads, then send personalized follow-up emails and update their status to show active outreach. Instruction to an agent: “Create a new lead in Salesforce for ABC JIM, Director of Engineering at XYZ Inc, email [email protected], phone 444-555-1111, located in San Francisco, CA. Set the lead source to Trade Show and industry to Technology. Then send him a personalized follow-up email about our enterprise product demo and update his lead status to Working - Contacted.” Resulting behavior:-
Calls Create lead with:
-
First nameset to “ABC”. -
Last nameset to “JIM”. -
Companyset to “XYZ Inc” (required). -
Titleset to “Director of Engineering”. -
Emailset to “[email protected]”. -
Phoneset to “444-555-1111”. -
Cityset to “San Francisco”. -
Stateset to “CA”. -
Countryset to “United States”. -
Lead sourceset to “Trade Show”. -
Industryset to “Technology”. -
Statusset to “New”.
-
- Creates a new Lead record in Salesforce.
- Returns the Lead ID (for example, “00Qxx000001234567”).
- Calls Send email action to send personalized follow-up email to Michael.
- Calls Update lead action to change status to “Working - Contacted”.
- Confirms the lead was created and outreach completed.
Troubleshooting
Action is not available in the agent builder
Action is not available in the agent builder
- Possible cause: Salesforce is not connected as a data source in the Admin console, or the Salesforce action pack is not enabled under Actions according to the Salesforce Actions Setup instructions.
- Fix: A Glean admin should complete Salesforce Actions Setup including OAuth configuration and ensure Salesforce actions appear under Actions → By datasource → Salesforce in the agent builder.
Action fails with an authorization or OAuth error
Action fails with an authorization or OAuth error
Leads are created but owners or fields are not what you expect
Leads are created but owners or fields are not what you expect
- Possible cause: The prompts of the agent and field mappings into the Salesforce Create lead action do not match your Salesforce org’s schema or defaulting rules, for example, default lead owner or required fields.
- Fix: Adjust the agent step configuration and prompts so the correct fields are passed, or update your Salesforce defaults and validation rules so they align with how the agent is creating leads.
Follow-up Update lead steps do not modify the newly created lead
Follow-up Update lead steps do not modify the newly created lead
- Possible cause: In flows that chain Salesforce Create lead and Salesforce Update lead, the agent is not capturing or passing the correct lead ID between steps; updating the same lead is difficult if the ID is not readily available and the update step is not fully background-runnable.
- Fix: Add a human review step or explicit confirmation of the lead record before running Salesforce Update lead, or adjust the agent design so updates happen only after the lead ID is clearly available to the agent runner.
FAQs
Can I use this action together with Salesforce Send email and Update lead?
Can I use this action together with Salesforce Send email and Update lead?
Yes. This action is designed to work alongside other Salesforce hero actions such as Send email and Update lead, so agents can create a lead, send an intro email, and update the lead status in a single coordinated run.
What happens if I create duplicate leads?
What happens if I create duplicate leads?
This action creates a new lead each time it runs. If you run the same configuration multiple times with the same lead information, you will create duplicate lead records in Salesforce. Design your workflow to avoid unintentional duplicates by adding checks or confirmation steps.
Can I process multiple leads from a source like Google Sheets?
Can I process multiple leads from a source like Google Sheets?
Yes. You can use this action in workflows that iterate through structured data sources like Google Sheets, creating a lead for each row. Combine with Send email and Update lead actions to complete the full prospecting workflow for each lead.