Update lead

The Salesforce Update lead action updates existing lead records in your connected Salesforce org identified by their Salesforce ID. This write action updates only the specified fields and does not change unspecified fields on the lead.

Limitations

• As with other Salesforce actions, the exact parameter set and behavior can change over time. Confirm behavior in your own environment and review the action schema in the agent builder before relying on this action for large-scale or fully automated lead updates.

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 and have permission to update Lead records.

Supported parameters

Parameter	Type	Description
Annual revenue	Number	Estimated or known annual revenue for the lead’s company. Defaults to -1 when not specified.
City	String	City for the lead’s mailing or business address.
Company	String	Company name associated with the lead. Typically required.
Country	String	Country for the lead’s mailing or business address.
Description	String	Free-form notes or additional context about the lead.
Email	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. Typically required.
Lead ID	String	Unique identifier of the lead record (for example, Salesforce lead ID). Required for updates.
Lead source	String	Origin of the lead (for example, Web, Partner, Event).
Number of employees	Integer	Number of employees at the lead’s company. Defaults to -1 when not specified.
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 just sent an introduction email to a lead and need to update their status in Salesforce to reflect active outreach, searching for them first to get their Lead ID.

Instruction to an agent:

"Find the lead for ABC at XYZ Inc in Salesforce and update his status to Working - Contacted with a note that says Sent intro email about enterprise product demo."

Resulting behavior:

• Calls Search Salesforce with SOQL to find leads where the last name is "ABC" and company is "XYZ Inc".

• Retrieves the Lead ID (for example, "00Qxx000001234567").

• Calls Update lead with:

  • Lead ID set to "00Qxx000001234567".

  • Status set to "Working - Contacted".

  • Description set to "Sent intro email about enterprise product demo on Dec 11, 2025".

• Updates the specified fields on the Lead record.

• All other fields (First name, Last name, Company, Email, Phone, Title, etc.) remain unchanged.

• Confirms the lead status was updated successfully.

Workflow tip: Always search for the lead first to get the Lead ID before updating. When chaining Create lead and Update lead, ensure your agent captures and passes the correct lead ID between steps. For prospecting workflows, you can combine this action with Create lead and Send email to create leads from sources like Google Sheets, send intro emails, and update status in one coordinated run.

Troubleshooting

• Possible cause: Salesforce is not connected as a data source, or the Salesforce action pack is not enabled and configured in your Glean deployment.
• Fix: In the Admin console, confirm that Salesforce is connected as a data source and that the Salesforce action pack is enabled under Actions. A Glean admin must complete Salesforce Actions Setup including OAuth configuration and ensure Salesforce actions appear under Actions → By datasource → Salesforce in the agent builder.

• Possible cause: The Salesforce OAuth app is not configured correctly, for example, callback URL, Consumer Key, or Consumer Secret, or the user running the agent has not completed the required Salesforce authorization flow from Glean.
• Fix: Have the user retry the agent and complete the Salesforce authorization prompt. If errors persist, a Glean admin should re-check the OAuth setup on the Salesforce Actions Setup page and re-run the configuration steps.

• Possible cause: In flows that chain Salesforce Create lead and Salesforce Update lead, the agent may not be 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.

• Possible cause: In some environments using the legacy action execution flow, Salesforce actions can fail with an error indicating that no valid base URL is available for custom auth.
• Fix: Retry the action later and, if the issue persists, ask a Glean admin or the actions-oncall team to review the Salesforce action pack configuration and any custom auth settings for Salesforce actions.

FAQs

No. The action updates only the specified fields. Only the fields you pass into the action are modified; all other fields remain unchanged on the record.

Use Salesforce Search or Search Salesforce with SOQL to find the lead by email, name, company, or other criteria first. These search actions will return the Lead ID, which you can then pass to Update lead.

Yes. Salesforce Update lead is designed to work alongside other Salesforce actions such as Create lead and Send email so agents can create a lead, send an intro email, and then update the status and related fields of the lead in one coordinated run.

Make sure your agent reliably captures and passes the correct lead ID from the Create lead step into Salesforce Update lead. Updating the newly created lead is difficult when the ID is not readily available and the update step is not fully background-runnable. It is recommended to add an explicit review or confirmation step before running the update, especially in high-volume or automated flows.