Hex integration
Hex data and BI automation
Hex is a collaborative analytics platform where teams build data notebooks, run SQL and Python projects, and ship shareable data apps. The NoClick Hex node works against the Hex API, so a single workflow can look up a project, check run status, pull run history, cancel a run that has stalled, grab the rendered image of a run's cell, and create embed URLs for results. It also covers the housekeeping around all of that: organizing projects into collections, editing data connections, ingesting semantic projects, and managing groups and user access. Point it at your workspace to keep runs monitored and results moving without opening Hex.
What you can automate with Hex
Hex operations
Triggers1
Runs5
Projects3
Sharing4
Embedding1
Admin3
Groups5
Collections4
Data Connections2
Semantic Models1
Questions
Yes. The Hex node includes an On Project Run Completed trigger, so a workflow starts the moment a project finishes running. From there it can check the run's status, pull the run's cell image, or create an embed URL and send the result on.
It can. Use Get Project Runs and Get Run Status to see how a run is going, and Cancel Run to stop one that has hung or is no longer needed. That keeps long-running projects from piling up unattended.
Hex authenticates with an API token you generate in your workspace settings. Paste that token into the node's credentials once and every Hex operation in your workflows uses it. Get Current User is a quick way to confirm the connection is live.
Yes. The node creates, edits, and reads collections to organize projects, and it manages groups with create, edit, get, list, and delete. It can also deactivate a user, which is handy for offboarding when someone leaves the team.
It can fetch the rendered image of a run's cell with Get Run Cell Image, and it can create an embed URL so a live project view can be dropped into a dashboard, email, or doc. Both give you a way to surface results outside of Hex without rebuilding the visuals.
