Integrations — HoxCore Documentation

Integration Model

HoxCore's philosophy is reference, don't replicate. Rather than syncing data from external tools into the registry, HoxCore stores authoritative links to where data lives in your existing tools.

This means:

Your GitHub issues stay in GitHub
Your Notion pages stay in Notion
Your Trello boards stay in Trello
HoxCore is the single place to find which tools and URLs belong to a given project

No OAuth, no sync, no webhooks

Integration references are just URLs and metadata in YAML. HoxCore requires no API keys, no OAuth flows, and no background sync processes for its reference model. Future releases may add optional live data fetch features.

The `tools` Field

Any entity can include a tools list. Each entry specifies a name, provider, and URL:

tools:
  - name: project-board
    provider: github
    url: https://github.com/sdescobedo/hoxcore/projects/1

  - name: design-doc
    provider: notion
    url: https://notion.so/team/design-abc123

  - name: backlog
    provider: trello
    url: https://trello.com/b/xyz123/backlog

  - name: ci-pipeline
    provider: github-actions
    url: https://github.com/sdescobedo/hoxcore/actions

Field	Required	Description
`name`	Yes	Descriptive label for this tool reference
`provider`	No	Tool provider identifier (used for display/filtering)
`url`	Yes	Direct URL to the relevant resource
`description`	No	Optional human-readable note

The `repositories` Field

Source code repositories get a dedicated field (separate from tools) to make them easily identifiable at a glance:

repositories:
  - name: main
    url: https://github.com/sdescobedo/hoxcore
    provider: github

  - name: frontend
    url: https://github.com/sdescobedo/hoxcore-web
    provider: github

  - name: infra
    url: https://gitlab.com/team/infrastructure
    provider: gitlab

To find entities associated with a particular provider, use hxc list with full-text search:

# Search for entities mentioning github in title or description
hxc list project --query github

# Or inspect an entity's raw YAML to see its repositories
hxc show P-001 --raw

GitHub

HoxCore integrates deeply with GitHub as a reference provider:

repositories:
  - name: main
    url: https://github.com/sdescobedo/hoxcore
    provider: github

tools:
  - name: project-board
    provider: github
    url: https://github.com/sdescobedo/hoxcore/projects/1
    description: "Main project planning board"

  - name: ci-cd
    provider: github-actions
    url: https://github.com/sdescobedo/hoxcore/actions
    description: "CI/CD pipeline"

  - name: issues
    provider: github
    url: https://github.com/sdescobedo/hoxcore/issues
    description: "Issue tracker"

  - name: discussions
    provider: github
    url: https://github.com/sdescobedo/hoxcore/discussions

Azure DevOps

repositories:
  - name: main
    url: https://dev.azure.com/myorg/myproject/_git/myrepo
    provider: azure-devops

tools:
  - name: work-items
    provider: azure-devops
    url: https://dev.azure.com/myorg/myproject/_workitems
    description: "Sprint backlog and work items"

  - name: pipelines
    provider: azure-devops
    url: https://dev.azure.com/myorg/myproject/_build
    description: "Build and release pipelines"

  - name: wiki
    provider: azure-devops
    url: https://dev.azure.com/myorg/myproject/_wiki

Notion

tools:
  - name: design-doc
    provider: notion
    url: https://notion.so/workspace/Design-Document-abc123
    description: "Architecture and design decisions"

  - name: meeting-notes
    provider: notion
    url: https://notion.so/workspace/Meeting-Notes-def456
    description: "Recurring meeting notes database"

  - name: roadmap
    provider: notion
    url: https://notion.so/workspace/Roadmap-ghi789
    description: "Product roadmap page"

Overleaf

Particularly useful for academic research projects and papers:

tools:
  - name: paper
    provider: overleaf
    url: https://www.overleaf.com/project/abc123def456
    description: "Main paper draft (LaTeX)"

  - name: supplementary
    provider: overleaf
    url: https://www.overleaf.com/project/xyz789ghi012
    description: "Supplementary materials"

Trello

tools:
  - name: sprint-board
    provider: trello
    url: https://trello.com/b/abc123/sprint-board
    description: "Current sprint kanban board"

  - name: backlog
    provider: trello
    url: https://trello.com/b/xyz456/product-backlog
    description: "Product backlog"

Google Workspace

tools:
  - name: spec-doc
    provider: google-docs
    url: https://docs.google.com/document/d/abc123/edit
    description: "Product specification document"

  - name: roadmap-sheet
    provider: google-sheets
    url: https://docs.google.com/spreadsheets/d/xyz456/edit
    description: "Roadmap and OKR tracker"

  - name: team-drive
    provider: google-drive
    url: https://drive.google.com/drive/folders/abc789
    description: "Project assets and files"

  - name: team-meeting
    provider: google-meet
    url: https://meet.google.com/xyz-abc-def
    description: "Weekly standup link"

Custom Integrations

The tools field is fully open-ended. Any URL-addressable resource can be referenced:

tools:
  - name: monitoring
    provider: datadog
    url: https://app.datadoghq.com/dashboard/abc123
    description: "Production monitoring dashboard"

  - name: support
    provider: zendesk
    url: https://company.zendesk.com/agent/queues
    description: "Customer support queue"

  - name: analytics
    provider: mixpanel
    url: https://mixpanel.com/project/123456
    description: "Product analytics"

  - name: internal-wiki
    provider: confluence
    url: https://company.atlassian.net/wiki/spaces/ENG/pages/123
    description: "Engineering runbook"

  # Any arbitrary tool
  - name: custom-dashboard
    provider: custom
    url: https://internal.company.com/projects/P-001
    description: "Internal project dashboard"

Provider naming convention

Provider names are arbitrary strings. Use lowercase with hyphens for consistency: github, azure-devops, google-docs. Consistent naming makes it easier to grep or search your raw YAML files by provider name.