How to get things done with Hexa.

Hexa lets your AI actually do things in the apps your work lives in: your CRM, email, calendar, meeting tools, and issue trackers. It runs multi-step jobs from start to finish, always asking before it sends or changes anything, and keeping a record of what it did. What your AI figures out once, Hexa saves so your whole team can run it with a sentence.

There are two surfaces: the AI, where work happens, and the Hub, where you review workflows and knowledge and administer the org. See the product overview.

Hexa speaks the Model Context Protocol (MCP). Claude (Desktop, Cowork, and Code) is our preferred client and the one we fully support today; other MCP-capable clients can point at the endpoint, and more are coming soon.

The easiest path: create an account and Hexa hands you a one-click connect link. To add it by hand, point your client at the endpoint https://mcp.hexahq.ai/mcp/. It uses OAuth, so you approve access in the browser the first time your client connects.

Full walkthrough on How it works.

Start free — connect an app and get your first task done, no credit card. Already have an account? Sign in. See what's in Free vs Enterprise on pricing.

For tools with a standard integration, connecting is one click: ask your AI to connect the tool (for example, "connect Salesforce"), and Hexa gives you a secure browser link where you sign in and grant access. The credential is stored server-side — nothing is pasted into the chat.

See the tools Hexa connects on Connect anything.

Some tools authenticate with an API key instead of OAuth. Hexa hands you a secure browser link where you enter the key — it is stored server-side and never travels through the chat.

Never paste a key, token, or secret into the conversation. By design there is no way to hand a raw key to your AI; credentials are always entered out-of-band in the browser. More on Security & governance.

Most tools don't ship an MCP server — that's Hexa's edge. Describe the tool's API and your AI authors the capability to call it. You build and host no server, and write no code. Tools that already ship an MCP server connect directly.

How this works: Connect anything.

Credentials are entered in the browser and held server-side. No key transits the chat, and there's nothing to commit to git. Access is keyed per person: a connector is shared once, but each teammate connects with their own credential and acts as themselves.

Details on Security & governance.

Just ask in plain language — "prep me for today's customer meetings," "draft follow-ups for yesterday's calls." Hexa figures out which tools and steps the task needs, runs the ones that are auto-approved, and pauses for your approval on anything that writes, sends, or deletes.

For 400 real examples by team, see use cases.

Do it once in a conversation. Hexa captures the multi-step work as a workflow — in your voice and format — so next time it's a single sentence, for you and anyone you share it with. The workflow lives in your organization, not one person's chat history, so it doesn't evaporate when someone leaves.

Share the workflow and your teammate runs it on their own credential — they never see yours. One technical person can connect the tools and author the capabilities once; everyone else clicks a link, signs in with their own account, and runs the workflows. No JSON, no setup.

More on the team story: Hexa for teams.

• Capability — a single action Hexa can take in a tool (look up a record, send a message). Your AI authors these from a tool's API.
• Workflow — a saved, multi-step process built from capabilities and run with one sentence.
• Knowledge — the facts and preferences Hexa remembers about how your org works, so results come back in your voice and format.

Every capability runs under an org-wide policy. Allow runs automatically (typically read-only lookups). Ask pauses for your approval first (anything that writes, sends, or deletes). Deny blocks it outright. The gate carries each person's own identity, so approvals and actions are always attributable.

More on Security & governance.

When a task hits an "ask" step, your AI shows you exactly what it's about to do and waits. Approve it and Hexa runs the step; decline and it stops there — nothing is sent or changed without your say-so.

Every action Hexa takes is recorded on a run timeline — what ran, who approved it, and when — so there's always an answer to "who did what." Review it in the Hub. See Hexa for teams.

The Hub is Hexa's admin web app. It's where you review and approve proposed workflows and connectors, manage knowledge, set the approval policy, and read the audit timeline — the place to review and govern the work, alongside the AI where it happens. See Hexa for teams.

As people use Hexa, it proposes new workflows and connectors. Admins review them in the Hub and approve the ones the org should share, so good process spreads deliberately rather than by accident.

A connector is shared once but keyed per person: each teammate connects with their own credential, so actions carry their own identity and permissions. Nobody borrows anyone else's access. This is what Claude Teams can't do today — see Hexa vs Claude Teams.

Free is for individuals — connect your tools and run workflows. Enterprise adds org-wide governance and the Hub. See pricing; Enterprise is a conversation with our team (no self-serve flow).

Your data is processed only to run the tasks you invoke, and is never used to train models. For exactly what's stored, how long, and which third parties are involved, see the Privacy Policy and the subprocessors list. More Q&A on the FAQ.

Can't find what you need? Contact us or email sales@hexahq.ai and we'll help.

First check the tool is connected — ask your AI to connect it, or connect it from the Hub. If the tool is connected but the specific action doesn't exist yet, ask your AI to do it anyway: it can author the capability from the tool's API. If a step is blocked, it's likely a deny policy — an admin can adjust it in the Hub.

That's the approval policy doing its job. "Ask" actions wait for your approval; "deny" actions are blocked org-wide. An admin sets and adjusts the policy in the Hub — see how approvals work.

Credentials can expire or be revoked at the source. Reconnect the tool the same way you first connected it — ask your AI to connect it, or use the connect link from the Hub — and re-authorize in the browser. Your workflows keep working once the credential is refreshed.