Hex support

Last updated date:

Connect, reconnect, and troubleshoot Hex without sharing credentials or customer content through support channels.

1. Before you start

  • Prefer a Hex workspace token created by an administrator; otherwise use a deliberately owned personal token.
  • Grant read access for projects, users, groups, collections, and data connections.
  • Decide separately whether Enterprise queried-table observability is approved and available.
  • Do not send Hex credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Hex API overviewHex's API token and endpoint overview.

2. Connect Hex

  1. In Seedling, open Connections and choose Hex.
  2. Choose personal or workspace scope deliberately; Seedling never promotes an actor-owned connection into workspace access.
  3. Enter the API token, optional workspace label, and the workspace's hex.tech API base URL.
  4. Seedling verifies the workspace and token identity before enumerating released assets.
  5. Allow the first Hex synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Hex API token rejected
Confirm the hex api token is active, was entered without surrounding whitespace, and belongs to the intended Hex account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Hex population as empty.
Wrong account or scope
Disconnect before retrying with the intended Hex identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the project or collection remains visible to the token and is not archived or deleted.
  2. Check user/group/project sharing and data-connection access changes.
  3. Treat queried-table data as optional Enterprise enrichment, not a completeness requirement for ordinary project sync.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement hex api token for the same Hex account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old hex api token in Hex.