Happy New Year! Here at Hex we took a few days to rest and recharge, and are feeling re-energized to take on the new year!
And boy oh boy are we taking it on — we’re ushering in 2023 with one of our most exciting features yet: Components.
We have also snuck in a few oft-requested enhancements for some of our existing features - including a big upgrade to Single Value cells. Read on for more...
🧱 Components
Ever find yourself rewriting the same logic time and again? Or copy-pasting a query from a doc? Or finding out your colleague wrote the same thing just a little differently?
Us too, and it isn’t fun. So today, we’re introducing a new way for teams to collaborate consistently within Hex: Components. These are reusable groups of cells that can be written once, and used anywhere.
You can easily create a component from an existing project: just select a few cells, click "New Component" and share it with your team:
You can then share your component with other users on your team or with your workspace, and they can easily reuse the logic across their projects.
Over time, your team can build up a centralized repository of consistent, reusable logic, and empower others to do great things.
Components are available now for everyone (and Teams and Enterprise accounts can share unlimited components with their workspace).
🔢 Single value cells now support dataframes
You can now move seamlessly from a SQL result to a Single Value cell, without taking a detour into Python to extract a specific value!
Yes, that means you can go ahead and delete the Python cells that just have value_to_display = dataframe_name['column_name'][0]
in them. Comparisons work seamlessly too.
⏱ Scheduled runs manager
Hex Admins can now manage all scheduled runs in their workspace from a single view. No need to @here the data team and ask who’s using up all those kernels. Scheduled runs manager is available in the Admin panel for Teams and Enterprise accounts.

Other improvements
- Previously when a dataframe had two columns with the same name, we sometimes renamed the second column for you, but often didn’t, leading to errors in downstream cells that required unique column names. Going forward, dataframes will always have unique column names, making the dataframe easier to use downstream.
- If your Athena data connection has access to multiple data catalogs, we now make sure to show all of them in the schema browser.
- We’ve improved how our API handles invalid or extraneous parameters. Rather than ignoring, we will now return a 422 response, with a payload detailing the invalid or unfound parameters.