Get User Connector

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens, Connectors

Finds the connector that belongs to a user in a connector group and saves its ID in a token. A connector can be linked to a user. This action looks in the group you name, of the connector type you pick, and returns the first connector linked to that user.

note

This action requires the Advanced Security feature (Enterprise) to be licensed. If it isn't, the action fails with a message that the feature is unlicensed.

Typical Use Cases

• Look up the current user's own connector before running an action that uses it
• Check whether a user already has a connector in a group, and skip creating another one
• Get a user's connector ID so you can read, test or delete it

Don't use it to

• Read the connector's details. This action only returns the ID. Pass it to Get Connector afterward.
• Find a connector by its name. Use Get Connector instead.
• Find a group ID. Use Find Group instead.

Related Actions

Action Name	Description
Get Connector	Reads the details of a connector into tokens.
Find Group	Gets a connector group ID from its title.
Add Group	Creates a connector group.
Delete Connector	Removes a connector.

Input Parameter Reference

Parameter	Description	Supports Tokens	Default	Required
Use current user	Look up the user who runs the action.	No	false	No
User Identifier	The user to look up, by UserId, Username or Email, for example [UserId]. A number is always treated as a UserId. The user must be in the current portal. Shown when Use current user is off.	Yes	empty string	Yes, when Use current user is off
Connector Type	The connector type of the group.	No	empty string	Yes
Group Title	The name of the connector group to search, for example Customer Accounts.	Yes	empty string	Yes
Output Entry Id	The name of a token to save the connector ID in, for example UserConnectorId. Brackets are optional.	No	empty string	Yes

Output Parameters Reference

Parameter	Description
[<Output Entry Id>]	The ID of the user's connector, a GUID. It's empty when the user has no connector in the group.

Considerations

• No connector isn't an error. If the user has no connector in the group, the output token is empty. Check it before you use it, for example with the condition [UserConnectorId] != "".
• The user, type and group must exist. Otherwise the action fails with one of these messages:
  • Could not identify the provided user.
  • No connector type with name '<type>' found.
  • No connector group with name '<group>' found.
• Only the first match is returned. If a user has more than one connector in the group, you get one of them.
• Few connectors are linked to users. In 1.28, connectors created with Add Connector, the type-specific add actions or the Connectors page aren't linked to a user. The action mostly finds connectors that were linked in earlier versions.

Examples

tip

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

1. Get the current user's connector

This action looks in the Customer Accounts group of the Salesforce connector type for the current user's connector. Its ID is saved in [UserConnectorId].

{
    "Title": "Get User Connector",
    "ActionType": "CredStore.GetUserEntry",
    "Description": "Find the current user's Salesforce connector",
    "Parameters": {
        "UseCurrentUser": true,
        "UserId": "",
        "TypeName": "salesforce",
        "GroupName": "Customer Accounts",
        "OutputEntryId": "UserConnectorId"
    }
}

2. Get another user's connector by email

This action looks up the user whose email is in [CustomerEmail].

{
    "Title": "Get User Connector",
    "ActionType": "CredStore.GetUserEntry",
    "Description": "Find the customer's Salesforce connector",
    "Parameters": {
        "UseCurrentUser": false,
        "UserId": "[CustomerEmail]",
        "TypeName": "salesforce",
        "GroupName": "Customer Accounts",
        "OutputEntryId": "UserConnectorId"
    }
}

Revised 09/26/2026