Skip to content
Log in Start now →
Product
PlatformPricingDimensionsIntegrationsSecurityCompare
Solutions · by use case
Customer, guest and fan experienceProduct feedback and prioritizationRevenue, churn and retentionAgenciesContact center performanceAI agent and chatbot analyticsMulti-location performanceReviews and competitive benchmarking
Solutions · by industry
Hotels and hospitalityRestaurants and food serviceFitness and leisureRetail and e-commerceSports and live entertainmentInsuranceBanking and financial servicesSoftware and SaaSAutomotiveConsumer products and CPGContact centers and BPOsPublic sector and nonprofitReal estateGaming and betting
Learn
Artifacts GalleryCustomer storiesResearchBlogThought leadershipLessons Log in Start now

GitHub integration for Dimension Labs

This brings in each issue in a GitHub repository as one conversation: the issue's title and body, then its comments, from your community and from your maintainers. It's built for a public or customer-facing repository where people file bugs and requests. You run it on your side: a small script pulls from the GitHub REST API and posts each message to the universal API. Discussions are only in GitHub's GraphQL API: see Discussions below.

Read the setup guide › Start now ›
Platform
GitHub Issues and Discussions
Type
Product feedback and community
Connects by
Universal API
Setup
5 steps
Guide checked
2026-10-26, against GitHub's documentation
[01] What comes acrossFrom GitHub into one format

Every GitHub message, in the same shape as everything else.

Each record lands in the Dimension Labs conversation format, so Dimensions, reports and the agent work the same way as for every other source.

GitHubDimension Labs
issue title and body_text; comment body_text text

Falls back to body (Markdown) if body_text is missing. Skip empty bodies.

user.id userId

GitHub's numeric user id, never the login. On your maintainers' replies, use the issue author's id.

author_association, user.type incoming

OWNER, MEMBER and COLLABORATOR are your side, and so is any author whose user.type is Bot. Everyone else (CONTRIBUTOR, FIRST_TIME_CONTRIBUTOR, NONE and so on) is incoming: true.

issue id sessionId

Prefix it, for example github-1296269. Comments find their issue through issue_url.

issue id conversationId

Same value as sessionId.

created_at dimensionlabs_timestamp

ISO 8601. Convert with toMillis.

repository, issue number, state, labels, author_association; comment id platformJson

Labels are the quickest way to filter bugs from feature requests.

[02] How to connect GitHubUniversal API

5 steps. Then it runs on its own.

A small job on your side reads GitHub through its API and posts each message to the Dimension Labs universal API. The guide gives the steps, the field mapping and the code. Run the job once for history, then every 15 minutes. A live source is enriched automatically every day; history is enriched with a backfill.

Rate limits, per GitHub: 5,000 requests per hour with a personal access token, 60 without one. Going over returns 403 or 429. Wait for retry-after seconds if it's there, or until x-ratelimit-reset (UTC epoch seconds) when x-ratelimit-remaining is 0 (rate limits).

Open the full GitHub guide ›
  1. 01Get API access in GitHub
  2. 02Pull new issues and comments
  3. 03Map the fields
  4. 04Send it
  5. 05Run it

What you need

  • A GitHub account that can read the repository's issues.
  • A fine-grained personal access token with the Issues repository permission set to read. For a public repository the API works without a token, but with much lower limits.
  • A Dimension Labs API key for a new Universal API source.

[03] What you can ask

Questions teams answer with GitHub data.

  • Which requests come from the accounts worth the most?
  • Which bugs do customers mention before they leave?
  • What should go on the roadmap next quarter?
[04] More product feedback and communityAll integrations ›
ProductboardCannyJiraFeaturebaseZendeskGongQualtricsTrustpilot
Not just these Any platform with an API connects the same way.

GitHub integration questions

Does Dimension Labs integrate with GitHub?

Yes. A small job on your side reads GitHub through its API and posts each message to the Dimension Labs universal API. The guide gives the steps, the field mapping and the code. The setup guide was checked against GitHub's documentation on 2026-10-26.

What GitHub data does Dimension Labs bring in?

This brings in each issue in a GitHub repository as one conversation: the issue's title and body, then its comments, from your community and from your maintainers. It's built for a public or customer-facing repository where people file bugs and requests. You run it on your side: a small script pulls from the GitHub REST API and posts each message to the universal API. Discussions are only in GitHub's GraphQL API: see Discussions below.

What do I need to connect GitHub?

A GitHub account that can read the repository's issues. A fine-grained personal access token with the Issues repository permission set to read. For a public repository the API works without a token, but with much lower limits. A Dimension Labs API key for a new Universal API source.

How often does GitHub data update?

Run the job once for history, then every 15 minutes. A live source is enriched automatically every day; history is enriched with a backfill.

Can I connect a platform that is not GitHub?

Yes. Any platform with an API connects through the same universal API, and any tool with an export button works as a file upload. The integrations page lists the platforms with a written guide.

Dimension Labs/Start with one file From $299 a month

Stop reporting. Start understanding.

Start with one file. Ask why a number moved. Plans from $299 a month, no demo and no contract on monthly plans.

Start now › See pricing ›