App Connections
In everyday work such as customer research, opportunity follow-up, and visit planning, sales representatives can use WinNexo to look up company information, review customer activity in a CRM, and create follow-up tasks in DingTalk. These tasks often require connections to the relevant business systems to retrieve data or perform actions.
App Connections let sales representatives use these systems directly in WinNexo. They can use a company account for services purchased centrally, or their own accounts and permissions when working with their customers or follow-up tasks.
Before You Configure: Identify the Authentication Method in 30 Seconds
- If the MCP service supports automatic discovery of authentication endpoints through the MCP 2025 specification, administrators only need to enter the service URL and save it. The system automatically identifies the authentication method as OAuth authorization. Users then sign in to their third-party accounts and authorize access. See Scenario 4: OAuth Authorization.
- If the service requires a Bearer Token, API Key/Secret, or Basic Auth through Headers, determine which of the following applies:
| Who Provides the Credentials | How to Configure Them | Detailed Instructions |
|---|---|---|
| The organization provides credentials that the team may share | The administrator enters complete, fixed values as required by the service. Users do not need to enter credentials individually. | See the Headers configuration in Scenario 2: Enterprise Credentials. |
| Each user has their own credentials | The administrator configures a fixed Header Name and defines the Header Value using credential parameter syntax: ${参数名}. Before use, users enter their own credential values on the App Connections page. | See the personal Header configuration and user steps in Scenario 3: User Credentials. |
Note: Basic Auth requires an already encoded credential value. Automatically encoding a username and password entered separately is currently not supported.
- If the service provides a personal URL, or personal credentials must be included in the URL, the administrator replaces the personal credential portion of the service URL with
${参数名}, for example,…?authCode=${authCode}. See the Connector URL configuration and user steps in Scenario 3. If the organization provides credentials that may be shared, enter the fixed values directly without defining parameters, as described in Scenario 2. - If the service explicitly requires no authentication, see Scenario 1: No Authentication.
TIP
Tip: Read the service provider's MCP integration instructions first, then find the appropriate guide below. WinNexo automatically identifies the authentication type from your configuration; you do not need to select it manually.
Configuration Methods
To create a custom MCP connection, administrators go to Capability Center > App Connections, click New Connection, and choose either method:
- Configure MCP Manually: Enter the connection URL, transport type, credentials, and other settings according to the provider's integration instructions.
- Configure MCP with JSON: Paste the JSON configuration provided by the service provider to quickly add a connector.
Both methods follow the same authentication rules. Choose either one. Follow the service provider's configuration instructions for the actual connection URL, credential placement, and format.