Connectors
Understand Winglo connectors, connection types, access controls, health states, activity, and safe disconnection.
Connectors let Winglo use information or capabilities from services your business already relies on. Connecting a service establishes access; it does not give every AI department unrestricted permission to use everything in that service.
Data connectors and MCP servers#
The Connectors page can contain two kinds of integration:
- Data connectors connect a supported service so Winglo can read, sync, publish, or communicate through the capabilities shown for that service.
- MCP servers advertise individual tools that can be enabled and controlled for each AI department.
Use the All, Data sources, and MCP servers filters to focus the catalog. The summary cards show the number of available data sources, connected MCP servers, discovered tools, and connections that need attention.
Read Connector concepts and connection types and MCP servers and tools for the differences.
Find and open a connector#
Choose Connectors in the main navigation. Search by service name or browse the categories. A department may also have an Integrations or Connectors page that shows connections relevant to that department.
Opening a card shows what the service covers, its authentication method, current status, compatible departments, and any available setup or management controls. A service marked Coming soon is visible for discovery but cannot be connected yet. Availability may also depend on your workspace and plan.
Connect a service#
- Open the connector and read what it can access.
- Choose Connect.
- Complete the provider sign-in, enter the requested API key, or supply the service URL shown by the form.
- Return to Winglo and confirm that the status is Connected.
- Review which compatible departments may use the connection.
Use credentials owned and controlled by your organization. Never paste an API key, access token, recovery code, or private service URL into department chat.
Understand connection states#
| Status | What it means | What to do |
|---|---|---|
| Connected | The connection is available | Review access and recent activity |
| Finishing setup | Authorization has started but is not complete | Finish the provider flow or reopen the connector |
| Needs attention | Winglo cannot currently use the connection as expected | Read the displayed error and reconnect if requested |
| Expires soon | Authorization is still working but may soon need renewal | Reconnect before important scheduled work |
| Disconnected | New work cannot use the connection | Reconnect only if the service is still needed |
| Coming soon | Setup is not currently available | Choose another supported service or check again later |
A failed sync does not always mean the credential is invalid. Read the Last sync failed message before reconnecting. If Sync now is available, use it once after correcting the cause and then check the result.
Control department access#
For a connected data service, Agent access shows the compatible AI departments. Turn access on only for departments that need the connection. A department that is not listed is not compatible with that connector.
MCP servers provide more detailed controls because a single server may advertise many tools. You can disable a tool, allow it to run automatically, or require approval before it runs. See Manage MCP tool access.
Connection access and action approval solve different problems. Access decides whether a department can reach a connector or tool. Approval decides whether a proposed action can run without a person confirming it.
Review activity#
Open a connected service to view its Activity log. It can show connection changes, access changes, sync attempts, health checks, token refreshes, and errors. Use this history when you need to understand when a connection changed or why a department stopped using it.
The activity log describes Winglo's interaction with the connector. Check the provider itself when you need to confirm the final state of an external record, message, or publication.
Disconnect safely#
Open the connector and choose Disconnect or the removal control shown for that connection. Confirm only after checking workflows, scheduled publications, triggers, and departments that depend on it.
Disconnecting prevents new use through that connection. It does not undo actions already completed, delete records at the provider, or necessarily revoke the provider-side authorization. Revoke access in the provider's security settings as well when your policy requires it.
For an MCP server, prefer disconnecting when you may need the configuration again. Permanent removal can also remove its discovered tools, grants, cached resources, and call history; the confirmation shown in Winglo explains the affected data.
If a connection fails#
Check the visible error, provider account access, credential status, compatible department access, and any workflow waiting on the service. Avoid repeatedly approving or retrying an external action when its outcome is unclear, because the provider may already have completed it.
For more help, use Troubleshooting Winglo.