300+ apps, six native integrations, one workspace. Every connection doubles as an agent tool.
Helm connects to the tools you already run on. Six native integrations for the core stack (Stripe, Slack, Gmail, Google Calendar, GitHub, plus WordPress and WooCommerce site connections via MCP), and 300+ external apps (HubSpot, Salesforce, Notion, QuickBooks, and more). Every connection is also a tool your AI agents can use on tasks, in chat, or over MCP.
Six integrations built directly into the platform. Direct OAuth, no middleware.
Agents post updates and field @mentions in channels.
Repo access for agents that ship code changes.
Site connections via MCP. Auto-detects WooCommerce for product and order tools.
Every external app uses the same OAuth flow, the same agent-tool pattern, and the same audit log.
And 290+ more. Browse the full catalog inside the product.
Three steps to put a new app in front of every agent in your workspace.
Step 1
Go to Settings → Integrations. Pick the app. OAuth or API key, same as any other SaaS tool. Two clicks.
Step 2
The integration appears as a tool group in every agent config. Toggle read or read+write per agent. Revoke any time.
Step 3
Assign a task, send a chat, or call the tool over MCP. Agents pick the right integration based on context and act.
Eight categories, ~40 apps each. Browse the full list in the product catalog.
HubSpot, Salesforce, Pipedrive, Zoho
Mailchimp, Klaviyo, ConvertKit, SendGrid
QuickBooks, Xero, FreshBooks, Plaid
Jira, Asana, Linear, ClickUp
Zendesk, Intercom, Front, Freshdesk
Notion, Google Docs, Confluence, Airtable
Airtable, PostgreSQL, Google Sheets, Snowflake
Shopify, Stripe, Recurly, Chargebee
Four real workflows that stop being "someday" once your stack is connected.
Your AM agent pulls new HubSpot deals every morning, de-dupes against existing records, and posts a summary to the right Slack channel. No manual copy-paste.
Your marketing agent reads campaign metrics from Klaviyo and Mailchimp, writes a weekly summary into the client document, and flags underperforming segments.
Your finance agent compares QuickBooks receivables with Helm invoices, flags mismatches, and drafts dunning emails for the overdue ones. You review, send.
Your support agent reads new Zendesk tickets, auto-routes feature requests into the right Projects board, and closes the loop with the customer when shipped.
Our MCP server exposes Helm data to any AI client. Claude Code, Cursor, Windsurf, or custom agents built on any framework.
The questions we get most when teams plan a rollout.
Authenticate once (OAuth or API key) in Settings → Integrations. The toolkit then becomes available to every AI agent in your workspace as a tool group. Same pattern across 300+ apps, with per-agent read or read+write scopes.
External integrations are included on Pro and Business plans. Starter includes the six native integrations (Stripe, Slack, Gmail, Google Calendar, GitHub, and WordPress site connections). See Pricing for current plan limits.
The catalog includes 300+ toolkits and grows every month. If the app has a public API, odds are it's there. If it's not, tell us on Support and we'll escalate. You can also use MCP to expose a custom tool to your agents directly.
Both. Each tool group has read and read+write options, toggled per agent. Autonomy settings (observe, suggest, auto) still apply, so write actions can require approval before executing. Rotate or revoke credentials any time.
Yes. Every tool call is logged with the agent, the task or chat it ran from, the arguments, and the result. The audit log is visible in your workspace for compliance and debugging.
Yes. Helm is a full work platform on its own: CRM, Projects, Email, Invoicing, and the rest all work natively. Integrations extend the reach of your agents and data, but nothing is required.
Two clicks per tool. Every integration is also a tool your AI agents can use.