Update Salesforce Connector

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens, Connectors

Changes an existing Salesforce connector. The action finds the connector by its ID and saves a new title and new Salesforce login details.

The update replaces the connector's details. Fields you leave out are cleared, so pass every value you want to keep.

note

This action requires the Salesforce feature to be licensed.

Typical Use Cases

• Save a new password or security token after it changes in Salesforce
• Let users edit their saved Salesforce account from a form
• Rename a connector or change its login domain

Don't use it to

• Create a connector. Use Add Salesforce Connector instead.
• Check that the new details work. The action saves them without contacting Salesforce. Use Test Connector after saving.
• Update a connector of another type. Use Update Connector instead.

Related Actions

Action Name	Description
Add Salesforce Connector	Creates a Salesforce connector and returns its ID.
Get Connector	Reads the details of a connector.
Test Connector	Checks that a connector can sign in.
Delete Connector	Removes a connector.
Update Connector	Changes a connector of any type.

Input Parameter Reference

Parameter	Description	Supports Tokens	Default	Required
Portal	The portal of the connector group. It isn't used when the action runs. When using an expression, the value must be the PortalId.	Yes	empty string	No
Entry Id	The ID (GUID) of the connector to change, for example [SalesforceConnectorId].	Yes	empty string	Yes
User Id	A user ID for the connector. In 1.28 this value isn't saved on the connector.	Yes	empty string	No
Entry title	The new name of the connector. It always replaces the current name, so an empty value clears it.	Yes	empty string	No
Login Url	The Salesforce login domain, for example https://ap1.salesforce.com/. If the value doesn't end with /services/oauth2/token, that path is added. Leave it empty to use https://login.salesforce.com/services/oauth2/token.	Yes	empty string	No
Account Username	The Salesforce username.	Yes	empty string	Yes
Password	The Salesforce password. Saved encrypted. Use ****** to keep the saved password.	Yes	empty string	Yes
Security Token	The Salesforce security token for the user. Saved encrypted. Use ****** to keep the saved token.	Yes	empty string	Yes
Custom Data	Extra name-value pairs to store on the connector, entered as Data Key and Data Value. This list replaces the connector's current custom data.	Yes	empty	No

Considerations

• Everything is replaced. Values you leave out are removed, including Login Url and any custom data you don't list again. An empty Login Url means the default Salesforce login is used.
• Username, password and security token are required. If one is empty, the action fails with Parameter '<field title>' is required. To keep a saved password or token without knowing it, pass ******.
• The Entry Id must exist. An empty value fails with Data was not saved due to an invalid EntryId!. An ID that isn't found fails with Requested connector, with id '...', does not exist. A value that isn't a GUID also fails.
• The connector type isn't checked. The action changes whatever connector the ID points to. Make sure it's a Salesforce connector.
• The login isn't tested. Run Test Connector after the update to check the new details.

Examples

tip

To understand how to use the below examples, please see Running Examples.

1. Save a new security token

This action updates the connector with ID [SalesforceConnectorId] with a new security token from a form. The saved password is kept by passing ******.

{
    "Title": "Update Salesforce Connector",
    "ActionType": "cs.salesforce.update",
    "Description": "Save the new Salesforce security token",
    "Parameters": {
        "EntryId": "[SalesforceConnectorId]",
        "EntryName": "Salesforce - [CompanyName]",
        "LoginUrl": "",
        "UserName": "[SalesforceUsername]",
        "Password": "******",
        "SecurityToken": "[SalesforceSecurityToken]"
    }
}

Revised 09/26/2026