Connectors
A connector gives HexaHQ access to an app or API where your work happens, such as Salesforce, Gmail, Slack, Google Drive, or an internal service.
What a connector provides
A connector describes how HexaHQ reaches a tool and authenticates to it. The actions available through that tool are capabilities.
Some connectors are already available. If a tool has an API but no existing integration, your AI can help create the connector and the capabilities it needs. You do not need to build or host a separate MCP server.
Shared setup, individual access
An organization can set up a connector once, but each person connects with their own account when the tool supports individual access. Actions then use that person's identity and existing permissions.
Sharing a connector never shares your credentials. One teammate cannot borrow another teammate's access.
Some tools are connected once for the whole team instead, through a bot or a service account. That is a credential the organization owns rather than one of yours, and work through it runs as the bot. Your own sign in stays yours either way.
Credentials
HexaHQ collects credentials in a secure browser flow. OAuth connectors ask you to sign in to the source app. Connectors that use an API key provide a secure page where you enter it.
Never paste a password, key, token, or secret into an AI conversation. Credentials are stored outside the conversation and are not included in prompts.
If access expires or is revoked, reconnect the tool. Existing workflows can use it again after access is restored.
HexaHQ and your AI client
There are two connections in a typical setup. Your AI client connects to HexaHQ through MCP. HexaHQ then connects to the apps and APIs used for your work.
In the Hub, Connector refers to the second kind: the connection between HexaHQ and a work tool.