La interfaz está localizada; las descripciones y documentos de las Skills se traducen automáticamente con IA a su idioma. El código, los comandos, rutas y términos técnicos se mantienen en el original, y prevalece el documento del autor.
Explorar Skills
Productividad · SKILL.md

hex-install-auth

hex-install-auth

Install and configure Hex SDK/CLI authentication. Use when setting up a new Hex integration, configuring API keys, or initializing Hex in your project. Trigger with phrases like "install hex", "setup hex", "hex auth", "configure hex API key".

Independent GitHub snapshot · Automated classification · Original documentation governs

Documentación de la Skill

GitHub

name: hex-install-auth description: 'Install and configure Hex SDK/CLI authentication.

Use when setting up a new Hex integration, configuring API keys,

or initializing Hex in your project.

Trigger with phrases like "install hex", "setup hex",

"hex auth", "configure hex API key".

' allowed-tools: Read, Write, Edit, Bash(npm:), Bash(curl:), Grep version: 1.6.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:

  • saas
  • hex
  • data
  • analytics compatibility: Designed for Claude Code

Hex Install & Auth

Overview

Configure Hex API authentication using OAuth 2.0 Bearer tokens. The Hex API at app.hex.tech/api/v1/ lets you programmatically trigger project runs, check status, manage users, and configure connections. Tokens are generated per-user in the Hex workspace settings.

Prerequisites

  • Hex account (Team or Enterprise plan)
  • Workspace admin access for API token generation
  • At least one published Hex project

Instructions

Step 1: Generate API Token

  1. Open Hex workspace settings
  2. Navigate to API tokens section
  3. Click New Token
  4. Set description and expiration
  5. Select scopes: "Read projects" and/or "Run projects"

Step 2: Configure Environment

# .env (NEVER commit)
HEX_API_TOKEN=hex_token_abc123...
HEX_WORKSPACE_URL=https://app.hex.tech

# .gitignore
.env
.env.local

Step 3: Verify Connection

// verify-hex.ts
import 'dotenv/config';

const TOKEN = process.env.HEX_API_TOKEN!;

async function verify() {
  const response = await fetch('https://app.hex.tech/api/v1/projects', {
    headers: { 'Authorization': `Bearer ${TOKEN}`, 'Content-Type': 'application/json' },
  });
  if (!response.ok) throw new Error(`Hex API ${response.status}`);
  const projects = await response.json();
  console.log(`Connected! Found ${projects.length} projects`);
  return projects;
}

verify().catch(console.error);
# curl verification
curl -s -H "Authorization: Bearer $HEX_API_TOKEN" \
  https://app.hex.tech/api/v1/projects | python3 -m json.tool

Token Scopes

ScopeEndpointsUse Case
Read projectsListProjects, GetProjectRuns, GetRunStatusMonitoring
Run projectsRunProject, CancelRun (+ all read)Orchestration

Error Handling

ErrorCauseSolution
401 UnauthorizedInvalid or expired tokenRegenerate in workspace settings
403 ForbiddenMissing scopeCreate token with "Run projects" scope
404 Not FoundWrong workspace URLVerify HEX_WORKSPACE_URL

Output

Return an authentication setup receipt with environment, secret reference rather than value, token-scope class, approved project/destination result, synthetic connectivity status, and rotation/cleanup owner. Never print an access token, SQL, or output.

Examples

env=sandbox; secret_ref=hex-client-v4; scope=project-run; destination=approved; synthetic_probe=200; rotation_owner=platform-ops proves setup without exposing a credential.

Resources

Next Steps

After auth, proceed to hex-hello-world.

Skills guardadas