Agentforce Connector Release Notes

You can now use the new Send Message (Sync) operation instead of Continue agent conversation to return a structured JSON response that separates business data from metadata. The Continue agent conversation operation was deprecated because it supported a limited set of response types and returned only the text from the Message field.

The Start agent conversation and Send Message (Sync) operations now support the Agent Variables field. Use this field to pass agent variables that provide additional context to the agent during a request.

The connector now includes the MS-AGENTFORCE:AGENT_API_ERROR and MS-AGENTFORCE:INVALID_CONNECTION error types for all operations.

The Start agent conversation and Continue agent conversation operations now return the new collect additional attribute in the response, providing access to more elements from the agent’s full payload.

The new Bypass User field in the Start agent conversation operation now provides a mechanism to override the logged-in user’s permissions, allowing agents linked to Data Cloud content to use their own assigned user to access these assets.

Transport Layer Security (TLS) configuration support is added.

You can now configure an HTTP proxy for this connector.

The Read Timeout and Read Timeout Unit parameters are supported at both the configuration and operation levels.

Enhanced connector filtering mechanism is added to filter out Agentforce (Default) as these agents aren’t accessible via the API.

Agentforce Connector User Guide

Agentforce Connector Reference

Salesforce Help

MuleSoft Services

Known Issues