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.
- The authenticated Salesforce user must have permission to edit Task records based on your organization’s sharing rules.
Supported parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| Task ID | String | Yes | Salesforce ID of the task to mark as completed (e.g., “00T5g00007ABCDEFUA2”). |
| Completion notes | String | No | Optional notes about the task completion; appended to the existing task description. |
Usage examples
- “Mark task 00T5g00007ABCDEFUA2 as completed with notes ‘Spoke with prospect, confirmed needs, scheduled demo for next Tuesday’.”
- “Complete the follow-up call task and add the summary ‘Customer satisfied with resolution’.”
- “Close out my sales outreach task with completion notes ‘Left voicemail, will try again tomorrow’.”
Troubleshooting
Action does not appear in the agent builder
Action does not appear in the agent builder
- Possible cause: The Salesforce action pack is not added, not linked to your Salesforce data source, or not fully configured.
- Fix: In the Glean admin console, go to Platform → Actions, add or open the Salesforce action pack, link it to your Salesforce datasource, configure authentication, update publish settings, and save. After that, Salesforce actions should appear under Actions → By datasource → Salesforce.
Action fails with OAuth or connected account error
Action fails with OAuth or connected account error
- Possible cause: The user’s connected Salesforce account is missing, inactive, or misconfigured, or the Salesforce connected app is not set up correctly.
- Fix: Ask the user to re-authenticate Salesforce when prompted by Glean. If errors persist, verify the Salesforce connected app configuration (callback URL and scopes) and confirm that Salesforce Actions setup is complete.
Action fails with invalid task ID error
Action fails with invalid task ID error
- Possible cause: The provided task ID does not exist in Salesforce, is not a valid 18-character Salesforce ID, or the user does not have access to view the task.
- Fix: Verify the task ID is correct by checking the task directly in Salesforce. Task IDs typically start with “00T” and are 15 or 18 characters long. Ensure the user has permission to view and edit the task.
Action fails with insufficient permissions error
Action fails with insufficient permissions error
- Possible cause: The authenticated Salesforce user does not have permission to edit Task records or the specific task is assigned to someone else with restricted access.
- Fix: Verify the user’s Salesforce profile or permission set includes edit permissions for Tasks. Check that the task owner allows others to edit the task based on your organization’s sharing settings.
FAQs
What happens to the existing task description?
What happens to the existing task description?
If you provide completion notes, they are appended to the existing task description. The original description is preserved, and your notes are added at the end. If you do not provide completion notes, only the status is updated to “Completed”.
What task status does this action set?
What task status does this action set?
This action sets the task status to “Completed”. If your Salesforce org has custom task statuses, the action uses the standard “Completed” status value. You cannot specify a different completion status with this action.
Can I complete multiple tasks at once?
Can I complete multiple tasks at once?
No. This action completes one task at a time. To complete multiple tasks, you need to call this action multiple times with different task IDs, or use a loop in your agent workflow.