Linking BugHerd as a source

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Learn more
PostHog Wizard hedgehog

Contents

Alpha release

This source is currently in alpha. The interface and available tables may change.

The BugHerd connector syncs your bug tracking and QA data – organization details, projects, tasks, and users – into the PostHog data warehouse.

Adding a data source

  1. Go to the sources tab of the data pipeline section in PostHog.
  2. Click + New source and then click Link next to BugHerd.
  3. You need an API key from BugHerd. Find it in BugHerd under Settings > General Settings (organization owner/admin access is required).
  4. Back in PostHog, enter the API key and click Next.
  5. Select the tables you want to sync, set the sync method and frequency, then click Import.

Once the syncs are complete, you can start using BugHerd data in PostHog.

Available tables

TableDescriptionSync method
OrganizationYour BugHerd organization detailsFull refresh
UsersUsers in your BugHerd organizationFull refresh
ProjectsProjects in your BugHerd accountFull refresh
TasksTasks (bugs) across all projectsIncremental

Incremental tables sync only new or updated records on each run. Full refresh tables reload all data on each sync.

Sync limitations

Only the Tasks table supports incremental syncing, using BugHerd's updated_at timestamp filter. The API does not expose reliable timestamp filters for other endpoints, so they sync in full each run.

Configuration

OptionTypeRequired
API keypasswordYes

Supported tables

TableDescriptionSync methodIncremental fieldPrimary key
Organization

Top-level details about your BugHerd organization.

Full refresh——
Users

Team members and guests who belong to your BugHerd organization.

Full refresh——
Projects

Websites/projects tracked for visual feedback and bug reporting in BugHerd.

Full refresh——
Tasks

Bug reports and feedback items ('tasks') logged against a project's kanban board.

Incremental, Full refreshupdated_at, created_at—
ArchivedTasks

Tasks that have been closed or archived in a project, and so no longer appear on the active taskboard.

Full refresh——
FeedbackTasks

Tasks sitting in a project's backlog (feedback) column, not yet triaged onto the board.

Full refresh——
Columns

Kanban columns on a project's board, including the built-in backlog, todo, doing and done columns and any custom ones.

Full refresh——
TaskComments

Comments posted on a task, forming its discussion thread.

Full refresh——

Still have questions?

Was this page useful?