Hex helps marketing teams know which analytics projects, notebooks, and data connections support the decisions they are about to make. With Hex connected, Juno can find relevant projects, inspect project details, review notebook cells, check recent run status, and audit workspace users, groups, collections, and sharing settings. It brings the analysis layer into campaign planning, so teams can ask what exists, what is running, and whether a trusted project is ready to guide spend, content, or lifecycle decisions.
What Juno does with Hex
Hex gives Juno a practical Hex MCP connector for marketers who need the analysis layer close to campaign planning. Once connected, Juno can find relevant analytics projects, inspect project details, review notebook cells, check recent run status, and look across data connections, users, groups, collections, and sharing settings.
That turns "someone has a notebook for that" into searchable context for the decision in front of you. Ask Juno which project supports a spend readout, whether a cohort analysis has run recently, or what notebook cells are driving the chart you want to cite.
Hex's Public API documentation describes workspace operations for projects, runs, access controls, collections, and data connections. Juno keeps the marketer's question in plain language while checking the workspace pieces that make the answer trustworthy.
Where it fits in your workflow
Connect Hex before a QBR, campaign postmortem, content roadmap, lifecycle review, or budget meeting where the team needs the real analysis, not a screenshot with mystery provenance. The practical trigger is simple: a marketing decision depends on a Hex project, and you need to know whether that project is current, relevant, and safe to use.
A useful workflow starts with the decision. Give Juno the campaign, segment, metric, date window, or project name you care about. It can explore analytics projects, review notebook cells, check project runs, and audit data connections before returning a brief, tracker, or roadmap note your team can actually act on.
It also fits governance checks. If a trusted project is shared too narrowly, tied to a data connection nobody recognizes, or sitting in the wrong collection, Juno can flag that context before the marketing team builds next month's plan around it.
What you get
- Hex project maps that show which analytics projects, collections, and sharing settings support a campaign, segment, or reporting question
- Notebook cell summaries that help marketers understand the logic behind charts, tables, and metrics without spelunking through every block
- Recent run status checks for projects that need to be fresh before a readout, roadmap call, or spend decision
- Data connection audits that clarify which sources a project depends on before the team treats it as a source of truth
- Decision-ready briefs and trackers that turn project context into next steps for content, lifecycle, paid media, or customer analysis
Frequently asked questions
Can Juno edit my Hex notebooks?
Use this connector for inspection, reporting, and planning context. Juno can point to the projects, cells, runs, data connections, and sharing details that deserve attention, while your analytics team still owns notebook changes and data decisions.
What should I provide before asking Juno to review Hex?
Bring the decision you are trying to make, the campaign or customer segment, the metric that matters, and any project names or collections you already know. If you are not sure where the analysis lives, start by asking Juno to explore relevant projects.
Can this help with access and governance questions?
Yes. Juno can audit users, groups, collections, sharing settings, and data connections so you can tell whether a trusted project is visible to the right people and grounded in recognizable data sources.
When should I authorize Hex?
Authorize it when your next marketing decision depends on an existing Hex analysis: a campaign performance brief, customer cohort review, content roadmap, lifecycle tracker, or budget recommendation that should be backed by current project context.