Step 4 - Create config.yml

config.yml has one top-level block per system: hivel: (always required), then one block per source you're syncing, jira:, github:, gitlab:, bitbucket:, azure:, and claudeotel: if you're tracking Claude Code usage. Source blocks are lists, so you can combine multiple instances of the same tool. The examples below show each block on its own, then a combined example at the end. See Configuration Reference for the full key-by-key reference.

Minimal - Jira only

hivel:
  api_token: ${HIVEL_API_TOKEN}
 
jira:
  - instance_slug: jira
    url: https://your-org.atlassian.net
    email: ${JIRA_EMAIL}
    token: ${JIRA_TOKEN}
    earliest_issue_date: "2025-01-01"

How to create a jira token?

Minimal - GitHub only

hivel:
  api_token: ${HIVEL_API_TOKEN}
 
github:
  - instance_slug: github-main
    token: ${GITHUB_TOKEN}
    earliest_data_date: "2025-01-01"
    include_orgs:
      - your-github-org

How to create a github token?

Minimal - GitLab only

hivel:
  api_token: ${HIVEL_API_TOKEN}
 
gitlab:
  - instance_slug: gitlab-main
    token: ${GITLAB_TOKEN}
    earliest_data_date: "2025-01-01"
    include_groups:
      - your-gitlab-group

How to create a gitlab token?

Minimal - Bitbucket only

hivel:
  api_token: ${HIVEL_API_TOKEN}
 
bitbucket:
  - instance_slug: bitbucket-main
    email: ${BITBUCKET_EMAIL}
    token: ${BITBUCKET_TOKEN}
    earliest_data_date: "2025-01-01"
    include_workspaces:
      - your-workspace

How to create a bitbucket token?

Minimal - Azure DevOps only

hivel:
  api_token: ${HIVEL_API_TOKEN}
 
azure:
  - instance_slug: azure-main
    token: ${AZURE_TOKEN}
    earliest_data_date: "2025-01-01"
    organization: your-org

How to create an azure devops token?

Azure DevOps Server (on-prem/TFS) instead of Azure DevOps Services (cloud):

azure:
  - instance_slug: azure-onprem
    token: ${AZURE_TOKEN}
    is_server: true
    url: https://host/tfs/CollectionName
    earliest_data_date: "2025-01-01"

Minimal - Claudeotel

hivel:
  api_token: ${HIVEL_API_TOKEN}

claudeotel:
  - instance_slug: acme-claude
    base_url: https://otel-collector.hivel.ai/api  
    api_key: dummy-value                            
    org_id: "1132"                                    

How to create a claude enterprise API key?

Combined - Jira + GitHub

hivel:
  api_token: ${HIVEL_API_TOKEN}
 
jira:
  - instance_slug: jira
    url: https://your-org.atlassian.net
    email: ${JIRA_EMAIL}
    token: ${JIRA_TOKEN}
    earliest_issue_date: "2025-01-01"
 
github:
  - instance_slug: github-main
    token: ${GITHUB_TOKEN}
    earliest_data_date: "2025-01-01"
    include_orgs:
      - your-github-org

Multiple providers in one config are supported - the agent syncs all configured providers in parallel.

Note: When configuring multiple instances of the same tool (for example, two separate Jira deployments, or GitHub Cloud alongside GitHub Enterprise Server), give each one a distinct instance_slug so the agent and Hivel platform can tell them apart. A simple numbered suffix works well - e.g. jira-1 and jira-2 - though any unique, descriptive name is fine too (e.g. github-cloud and github-onprem).

Step 3

Step 5