Update Fedex Connector

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens, Connectors

Changes an existing Fedex connector. The action finds the connector by its ID and saves a new title and new Fedex Web Services keys and passwords.

The update replaces the connector's details. An empty field clears the saved value, so pass every value you want to keep.

caution

In 1.28, this action fails in apps with the error Could not get GroupTypeName for Feature of 'cs.fedextracking.credentials.update'. The action is missing a setting the license check needs. Use Update Connector instead, or edit the connector on the Connectors page.

Typical Use Cases

• Save new Fedex passwords after they change
• Rename a Fedex connector

Don't use it to

• Create a connector. Use Add Fedex Connector or Add Connector instead.
• Check that the new credentials work. The action saves them without contacting Fedex.
• Update a connector of another type. Use Update Connector instead.

Related Actions

Action Name	Description
Update Connector	Changes a connector of any type, including Fedex.
Add Fedex Connector	Creates a Fedex connector and returns its ID.
Get Connector	Reads the details of a connector.
Delete Connector	Removes a connector.

Input Parameter Reference

Parameter	Description	Supports Tokens	Default	Required
Entry Id	The ID (GUID) of the connector to change, for example [FedexConnectorId].	Yes	empty string	Yes
Entry title	The new name of the connector. It always replaces the current name, so an empty value clears it.	Yes	empty string	No
Account Key	The value sent as WebAuthenticationDetail.ParentCredential.Key. An empty value clears it.	Yes	empty string	No
Account Password	The value sent as WebAuthenticationDetail.ParentCredential.Password. Saved encrypted. Use ****** to keep the saved password.	Yes	empty string	No
Application Key	The value sent as WebAuthenticationDetail.UserCredential.Key. An empty value clears it.	Yes	empty string	No
Application Password	The value sent as WebAuthenticationDetail.UserCredential.Password. Saved encrypted. Use ****** to keep the saved password.	Yes	empty string	No

Considerations

• See the caution above. In 1.28, the license check makes this action fail in apps. It only runs where the license check is skipped, such as Plant an App's own system pages.
• Everything is replaced. The title, keys and passwords are saved as entered. Pass the keys again even if they haven't changed. To keep a saved password 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. If the ID belongs to another type of connector, that connector's fields are cleared. Make sure it's a Fedex connector.

Examples

tip

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

1. Save new Fedex passwords

This action updates the connector with ID [FedexConnectorId] with new passwords from a form and passes the keys again. Because of the 1.28 issue described above, use Update Connector for this in an app.

{
    "Title": "Update Fedex Connector",
    "ActionType": "cs.fedextracking.credentials.update",
    "Description": "Save the new Fedex passwords",
    "Parameters": {
        "EntryId": "[FedexConnectorId]",
        "EntryName": "Fedex - Warehouse",
        "AccountKey": "[FedexAccountKey]",
        "AccountPassword": "[FedexAccountPassword]",
        "ApplicationKey": "[FedexApplicationKey]",
        "ApplicationPassword": "[FedexApplicationPassword]"
    }
}

Revised 09/26/2026