Integrations

Integrations turn Hubi from a capable AI into a teammate that knows your data and can act on it. Connect your business stack and let Hubi read, write, and take action across all of it. Manage everything from Capabilities > Integrations in the dashboard.

Channels - Where You Talk to Hubi

Channels are how your team reaches Hubi day to day.

• Slack - the most common channel. Most new workspaces connect Slack during onboarding, and Hubi becomes available in any channel or DM. To connect later, open Capabilities > Integrations, choose Slack, and complete the OAuth authorization.
• Microsoft Teams - install Hubi from Microsoft Teams, then send Hubi the setup command shown on the Teams card (connect <code>). Teams itself handles install, scope selection, and permissions; a manual package is offered as a fallback, though manual upload depends on your tenant's Teams app policy. Available where it is enabled for your workspace.
• Web and mobile - always available, no setup required.

Once a channel is connected, invite @Hubi and message it like any teammate. Channels are also how Jobs deliver their results.

App Integrations - 1,000+ Tools

Connect third-party apps so Hubi can fetch data and take action:

• Google Workspace - Gmail, Calendar, Drive, Docs
• Google Analytics and Google Search Console - the traffic and search data behind SEO audits
• HubSpot - contacts, deals, pipeline
• Notion - pages, databases, tasks
• WordPress, Webflow, Wix, and other CMSs - where your articles get published. See Publish Your Articles.
• And 1,000+ more

How to connect: open Capabilities > Integrations, browse or search, choose the app, and follow the OAuth flow or paste an API key.

Shopify has a dedicated native app that runs inside the Shopify admin. See Shopify for the recommended setup.

Notion and Klaviyo connect straight to the vendor's own MCP server through OAuth. You authorize in a popup and never paste an API key.

Just for Me or Shared

When you connect an app, Hubi asks how the connection should be used:

• Just for me - only your own conversations use it.
• Share with workspace - everyone in the workspace can have Hubi act through it.

Your first connection for an app is named "

OAuth vs. API Key

Most apps use OAuth - a browser-based login that auto-refreshes tokens. Some require a manual API key from the service's dashboard. API keys are stored encrypted and are never shown again after entry.

For anything that is not in the integrations directory - an API key for your own service, or a login to a site Hubi needs to reach - use Capabilities > Credentials. Credentials are stored encrypted, and admins can share one with specific groups rather than the whole workspace.

Managing Integrations

From Capabilities > Integrations:

• View - connected apps show a Connected badge. Open any integration to see status and actions.
• Disconnect - Hubi loses access, but no data is deleted from the third-party service.
• Reconnect - if an integration shows an error or expired status, reconnect to re-authorize.

Connected accounts are shared across web, mobile, Slack, and Teams.

When Hubi Needs One

Hubi asks for a connection at the point the work needs it, not before. A backlink pitch that needs Gmail, an audit that needs Google Analytics, an article that needs WordPress - each shows a Connect card right in the conversation. Selecting it takes you to the right integration, and the work carries on from where it paused.

Plan Requirement

App integrations are available on every plan. Free connects one channel; paid plans connect all of them. See Settings for details.