See every built-in connector at a glance: how it connects and whether it can change data. You can connect several accounts of each, and add any other remote MCP server with Add any MCP server.
Select a tool's name for its own page: what you need, how to connect, what you can ask, the tools Henkan uses, limits and troubleshooting.
At a glance#
| Tool | How it connects | What Henkan can do | Changes data? |
|---|---|---|---|
| Google Analytics 4 | Google sign-in, read-only | Reports, comparisons, funnels, pivots, realtime, A/B test readouts, tracking audit | No |
| Google Search Console | Google sign-in, read-only | Clicks, impressions, CTR and position, URL inspection, sitemaps | No |
| BigQuery | Service-account key | Datasets, schemas, read-only SQL with a cost cap, GA4 export summaries | No |
| Google Tag Manager | Google sign-in (through Stape) | Container audit, tags, triggers, variables, versions | Create, edit, remove, publish (with approval) |
| Kameleoon | API credentials, or Kameleoon sign-in (official MCP) | Test results with significance and SRM, breakdowns, program health, audit | Pause, resume, stop, traffic split, drafts (with approval) |
| Wingify | API token | Campaign results with significance, program health, audit, heatmap listing | Campaign status (with approval) |
| AB Tasty | API credentials | Campaigns and variations, results with significance and SRM | Play, pause (with approval) |
| Contentsquare | Contentsquare sign-in (official MCP), or API credentials | Site, page and zone metrics, Web Vitals, page diagnosis, audit | No |
| Microsoft Clarity | API token | Rage and dead clicks, quick backs, scroll, engagement for the last 1–3 days | No |
| Hotjar | API credentials + site IDs | Surveys: NPS with margin, ratings, choices, verbatims by device or country | No |
| Henkan Vision | API key | Sessions, timelines, frustration patterns, replay links | No |
| Qualtrics | API token or OAuth client | NPS, CSAT and CES by segment and period, open-text themes, key drivers, survey audit | No |
| Piano Analytics | API keys + site IDs | Reports by property and metric, period comparisons with significance, trends | No |
| Didomi | API key + secret | Consent notices and live settings, CNIL and Google Consent Mode audit, vendors, compliance scans | No |
| Commanders Act, Tealium, OneTrust | Vendor sign-in (official MCP); OneTrust without sign-in | Tags, server-side, privacy and consent statistics; Tealium server-side profiles; OneTrust API reference | No |
| Slack | Slack sign-in | Post reports and CSV tables, read a channel on request, talk to Henkan in Slack | Post, upload (with approval) |
| Notion | Notion sign-in | Read pages and databases, search, publish reports and test learnings | All writes (with approval) |
| Optimizely, MoEngage, Meta Ads, Amplitude, Fullstory, Klaviyo, Braze, Air360 | Vendor sign-in (official MCP) | The vendor's own tools: experiments, campaigns, ads, product analytics, sessions | Only with approval |
| HubSpot, Salesforce, Adobe Analytics | Official MCP, with an extra set-up step | CRM records and reports, Adobe report suites, segments and reports | Only with approval |
Rules that apply to every tool#
- Your permissions. Henkan sees what the connected account sees in the tool, and nothing more.
- Read tools run without asking by default. An organisation owner can set them to Ask before running.
- Tools that change data always ask. See Approve actions.
- The Can act badge marks tools where Henkan can change what your customers or your live site see: tags, tests, campaigns, ads or CRM records. Their panel says exactly what they can change.
- The Max badge marks premium connectors (BigQuery, Adobe Analytics, Salesforce, Optimizely, and your own MCP servers) when your organisation's plan doesn't include them. Ask Henkan to switch to Max or to try one; connections you already have keep working. See Requests and plans.
- Credentials stay on the server. They are encrypted and never shown again. See Security and privacy.
- Limits. Your organisation's plan and its requests, and each tool's own limits. See Usage and limits.