Connector concepts and connection types

Winglo uses connector as the general name for an integration with an external service. The catalog includes traditional data connectors and MCP servers, but they expose access in different ways.

Connector, connection, and access#

A connector is the supported integration shown in the catalog. A connection is your workspace's authorized link to that service. Department access determines which compatible AI departments may use the connection.

These states are independent. A connector can exist without being connected. A service can be connected while a particular department has no access. A department can have access while a specific action still waits for approval.

Data connectors#

A data connector provides the capabilities Winglo shows for a supported service. Depending on the service, those capabilities may include reading data, syncing information, publishing, or communication.

Data connectors usually expose a connection-level access control for compatible departments. Always read the connector detail before authorizing it; similar services can request different permissions.

MCP servers#

An MCP server advertises individual tools. After connection, Winglo discovers the tools offered by that server and lets you decide what each department may do with them.

Because one server can expose both low-risk and state-changing tools, MCP access is managed at the tool level. Read MCP servers and tools before enabling a server.

Authentication methods#

The setup screen shows the method required by each connector:

• Provider sign-in redirects you to the service to authorize access and returns you to Winglo.
• API key asks for a credential created at the provider.
• URL connects an endpoint such as a supported feed or server address.

Use an organization-controlled account where possible. Give the provider only the scopes required for the intended work. Winglo will never need a credential pasted into ordinary department chat.

Syncing and direct actions#

Some connectors periodically import information and may provide Sync now. Others are used only when a department performs a specific action or check. If the detail says there is no scheduled sync, a health-check error should not be interpreted as a missed import schedule.

The connector's activity log can show sync and access events. The provider remains the final place to confirm whether an external record, message, or publication exists.

Access and approval#

Access answers “may this department reach the service or tool?” Approval answers “may this proposed action run now?” A department may have access and still need your approval for a guarded tool.

For MCP tools, the available modes are explained in Manage MCP tool access. For actions waiting on a person, see Inbox and approvals.

Choose the minimum useful connection#

Connect a service only when a defined task needs it. Grant access only to the departments involved. Review activity after setup, and remove access when the task, employee, vendor, or service relationship ends.

For setup and status guidance, return to Connectors.