Skip to main content
Version: 1.28 (Current)

Add Fedex Connector

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens, Connectors

Creates a new Fedex connector in a connector group. The connector stores the Fedex Web Services keys and passwords that the Get Fedex Tracking Info action uses to track shipments. The action can save the ID of the new connector in a token, so later actions can use or update it.

The two passwords are saved encrypted. The two keys are saved as plain values.

caution

In 1.28, this action fails in apps with the error Could not get Type handler for Feature of 'cs.fedextracking.credentials.add'. Plant an App can't find the license feature for the Fedex connector type, so the license check stops the action. Use Add Connector with a Fedex group instead, or create the connector on the Connectors page.

Typical Use Cases​

  • Save Fedex Web Services credentials from a setup form
  • Create Fedex connectors from a setup workflow instead of by hand
  • Save the new connector's ID so you can update or delete it later

Don't use it to​

  • Change an existing Fedex connector. Use Update Fedex Connector instead.
  • Check that the credentials work. The action saves them without contacting Fedex.
  • Add a connector of another type. Use Add Connector instead.
Action NameDescription
Add ConnectorCreates a connector of any type, including Fedex.
Update Fedex ConnectorChanges the details of an existing Fedex connector.
Get ConnectorReads the details of a connector.
Delete ConnectorRemoves a connector.

Input Parameter Reference​

The four credential fields map to the WebAuthenticationDetail values of the Fedex Web Services API. See the Fedex documentation for how to get them.

ParameterDescriptionSupports TokensDefaultRequired
Group TitleThe Fedex connector group to add the connector to. The list shows Fedex groups only. The saved value is the group's ID.Noempty stringYes
Entry titleThe name of the connector, for example Fedex - Warehouse.Yesempty stringNo
Account KeyThe value sent as WebAuthenticationDetail.ParentCredential.Key.Yesempty stringNo
Account PasswordThe value sent as WebAuthenticationDetail.ParentCredential.Password. Saved encrypted.Yesempty stringNo
Application KeyThe value sent as WebAuthenticationDetail.UserCredential.Key.Yesempty stringNo
Application PasswordThe value sent as WebAuthenticationDetail.UserCredential.Password. Saved encrypted.Yesempty stringNo
EntryId Token NameThe name of a token to save the new connector's ID in, for example FedexConnectorId. Brackets are optional.Noempty stringNo

Output Parameters Reference​

ParameterDescription
[<EntryId Token Name>]The ID of the new connector, a GUID. It's only set when EntryId Token Name has a value.

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.
  • The group decides the connector type. If Group Title is empty, the action fails with Invalid GroupId. If no group has that ID, it fails with Connector group (id: ...) not found.
  • Nothing is required by the connector. Empty fields are saved as empty.
  • The credentials aren't tested. Test Connector doesn't support Fedex connectors.
  • Names aren't unique. Running the action twice with the same title creates two connectors.
  • Keep secrets out of the action. Pass the keys and passwords through tokens instead of typing them into the action.

Examples​

tip

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

1. Save Fedex credentials​

This action adds a connector to the Fedex group with ID 3, using values from a form. The new connector's ID is saved in [FedexConnectorId]. Replace 3 with the ID of your Fedex group. Because of the 1.28 issue described above, use Add Connector for this in an app.

{
"Title": "Add Fedex Connector",
"ActionType": "cs.fedextracking.credentials.add",
"Description": "Save the Fedex Web Services credentials",
"Parameters": {
"Group": "3",
"EntryName": "Fedex - Warehouse",
"AccountKey": "[FedexAccountKey]",
"AccountPassword": "[FedexAccountPassword]",
"ApplicationKey": "[FedexApplicationKey]",
"ApplicationPassword": "[FedexApplicationPassword]",
"EntryIdTokenName": "FedexConnectorId"
}
}

Revised 09/26/2026