Hex

Business software

Built when you ask for it

Sync Hex project, run, collection, and user data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Hex connector syncs your collaborative analytics data into analytics-ready tables in your data warehouse. Pull projects, runs, collections, and users from the Hex API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Projects
  • Runs
  • Collections
  • Users

How it gets built

  1. Choose Hex when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Hex's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Hex itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

Personal access token or workspace token (Bearer). In Hex, open your user settings, then API keys under Account, click New Token, give it a description and an expiry, and copy it. A workspace token, which only an admin can create, can be set never to expire; a personal access token, which anyone with the Editor role or above can create, expires after 7 to 120 days. Hex's API needs the Team or Enterprise plan, and Ingest reads app.hex.tech, so a single-tenant, EU or HIPAA workspace with its own Hex address is not supported yet.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Hex connector?
Not as a finished connector yet. Ingest builds it from Hex's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Hex data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Hex API documentation: https://learn.hex.tech/docs/api-integrations/api/overview

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, OpenAI (ChatGPT Enterprise), Clockify, Google Drive, Google Sheets, Jira.

Request Hex