- Category: crm
- Auth: OAUTH2
- Composio-managed OAuth available? No
- Tools: 24
- Triggers: 0
- Slug:
SALESFORCE_SERVICE_CLOUD - Version: 20261101_00
Tools
Agent Sensitive Data Rule Triggered
Agent Sensitive Data Rule Triggered
SALESFORCE_SERVICE_CLOUD_AGENT_SENSITIVE_DATA_RULE_TRIGGEREDNotifies Salesforce Live Agent that sensitive data rules were triggered in agent messages. Purpose: When an agent’s outgoing message contains sensitive data (SSN, credit card, email, etc.), call this action to apply configured masking or handling rules to protect customer privacy. Prerequisites: - Active Live Agent chat session with valid chat_id - Sensitive data rules configured in Salesforce Setup - Live Agent feature must be enabled in your Salesforce org Note: Salesforce Live Agent Chat is deprecated and retiring February 14, 2026. Migrate to Messaging for In-App and Web for continued support. Typical Flow: 1. Agent sends message containing sensitive data 2. System detects sensitive content matches a rule 3. Call this action with the chat_id and triggered rules 4. Salesforce applies masking/filtering per rule configurationInput Parameters
Output
Chasitor Sneak Peek
Chasitor Sneak Peek
SALESFORCE_SERVICE_CLOUD_CHASITOR_SNEAK_PEEKSend real-time typing indicator (sneak peek) to Live Agent during active chat session. Allows agents to see what visitors are typing before the message is sent. Requires an active Live Agent chat session with valid session_key and affinity token. The sequence number must increment with each request.Input Parameters
Output
Composite Batch
Composite Batch
SALESFORCE_SERVICE_CLOUD_COMPOSITE_BATCHTool to execute multiple independent REST subrequests in one batch call. Use when bundling up to 25 independent operations to minimize round trips. Subrequests cannot reference each other.Input Parameters
Output
Composite Request
Composite Request
SALESFORCE_SERVICE_CLOUD_COMPOSITE_REQUESTExecute up to 25 dependent Salesforce REST subrequests in a single API call. Subrequests execute sequentially and can reference results from earlier requests using ’@{referenceId.field}’ syntax. Use this when operations depend on each other (e.g., create Account then create related Contact). For independent operations, use Composite Batch instead.Input Parameters
Output
Composite SObject Tree
Composite SObject Tree
SALESFORCE_SERVICE_CLOUD_COMPOSITE_SOBJECT_TREECreate one or more nested sObject record trees in a single API call. Supports parent-child relationships up to 5 levels deep, with a maximum of 200 total records across all trees. Use this for bulk insertion of related records (e.g., Account with Contacts, or Orders with Line Items). Relationships must be Master-Detail or Lookup. Only supports INSERT operations, not upserts.Input Parameters
Output
Create Case Record
Create Case Record
Delete Case Record
Delete Case Record
Describe SObject
Describe SObject
End Chat Session
End Chat Session
SALESFORCE_SERVICE_CLOUD_END_CHAT_SESSIONEnd a Salesforce Live Agent chat session using its session key, API version, and affinity token. A success response does not necessarily confirm the session ended. DEPRECATED: Salesforce scheduled legacy Chat for retirement on February 14, 2026 and recommends migrating to Messaging for In-App and Web.Input Parameters
Output
Generate Request ID
Generate Request ID
SALESFORCE_SERVICE_CLOUD_GENERATE_REQUEST_IDGenerate a UUIDv4 string to use as an Idempotency-Key header in Salesforce User Interface API requests. This prevents duplicate record creation when POST, PATCH, or DELETE requests are retried due to network failures or timeouts. The same key returns cached responses for 30 days, avoiding duplicate operations and saving server resources. Use this tool whenever you need to ensure idempotent behavior for Salesforce UI API operations.Output
Generate Signed JWT Assertion
Generate Signed JWT Assertion
SALESFORCE_SERVICE_CLOUD_GENERATE_SIGNED_JWT_ASSERTIONTool to generate a signed JWT assertion for Salesforce JWT bearer OAuth flow. Use when you need to perform server-to-server authentication using a connected app’s certificate. Use before exchanging the assertion for an access token.Input Parameters
Output
Get Case Record
Get Case Record
SALESFORCE_SERVICE_CLOUD_GET_CASE_RECORDRetrieve a Salesforce Case record by its ID. Returns Case details including status, priority, subject, description, owner, and timestamps. Useful for: - Looking up Case details by ID - Checking Case status and priority - Getting customer issue information - Retrieving Case metadata and relationships Requires a valid 15 or 18-character Salesforce Case ID. Optionally specify which fields to retrieve using the fields parameter; otherwise all accessible fields are returned.Input Parameters
Output
Get Chat Messages
Get Chat Messages
Get Live Agent API Version
Get Live Agent API Version
List Einstein Bots
List Einstein Bots
Query All SOQL
Query All SOQL
SALESFORCE_SERVICE_CLOUD_QUERY_ALL_SOQLTool to execute a SOQL query including deleted and archived records. Use when you need to fetch all rows including soft-deleted data in Salesforce.Input Parameters
Output
Query SOQL
Query SOQL
Reconnect Chat Session
Reconnect Chat Session
SALESFORCE_SERVICE_CLOUD_RECONNECT_CHAT_SESSIONReconnect a Live Agent chat session after its affinity token changes, using the session key and affinity token. After reconnecting, call ResyncChasitorState to restore the visitor’s chat context; a success response does not necessarily confirm reconnection. DEPRECATED: Salesforce scheduled legacy Chat for retirement on February 14, 2026 and recommends migrating to Messaging for In-App and Web.Input Parameters
Output
Resync Chasitor State
Resync Chasitor State
SALESFORCE_SERVICE_CLOUD_RESYNC_CHASITOR_STATEResynchronizes the chat visitor’s state after a session reconnection. This action is part of the Salesforce Live Agent chat session recovery workflow: 1. First, call ReconnectChatSession with the session_key and affinity_token 2. Then, call this action to restore the visitor’s chat state 3. Finally, resume normal chat operations (sending messages, getting messages, etc.) Prerequisites: - An active or recently disconnected Live Agent chat session - Valid session_key and affinity_token from the original session - Live Agent must be properly configured in the Salesforce org Note: The legacy Live Agent product is being phased out in favor of Messaging for In-App and Web. This action sends a POST request to /chat/rest/Chasitor/ChasitorResyncState with required Live Agent headers but no request body.Input Parameters
Output
Retrieve Salesforce Username
Retrieve Salesforce Username
Send Custom Event
Send Custom Event
SALESFORCE_SERVICE_CLOUD_SEND_CUSTOM_EVENTSend a custom event from a chat visitor to a Live Agent during an active chat session. Use this tool to trigger custom event handlers on the agent’s side, enabling custom interactions beyond standard chat messages. Custom events can be used for actions like form submissions, button clicks, page navigation, or any application-specific events that need to be communicated to the agent. Prerequisites: - An active Live Agent chat session must be established - Live Agent REST API must be configured and enabled in your Salesforce org - Valid session_key and affinity_token from session initialization Note: This endpoint requires Live Agent to be properly configured. The API typically returns 204 No Content on success.Input Parameters
Output
Upload File to S3
Upload File to S3
Visitor Sensitive Data Rule Triggered
Visitor Sensitive Data Rule Triggered
SALESFORCE_SERVICE_CLOUD_VISITOR_SENSITIVE_DATA_RULETrigger sensitive data rules for a Live Agent chat visitor after sensitive content is detected, to support masking or handling. An empty success response does not confirm that the rules were applied. DEPRECATED: Salesforce scheduled legacy Chat for retirement on February 14, 2026 and recommends migrating to Messaging for In-App and Web.